Help desk
A shared inbox on your own instance
Deploy FreeScout with managed Postgres and a public HTTPS URL. You own the instance. You pay for compute — not per agent.
TemplatesFreeScout
What you get
A private FreeScout, packaged to ship
Customer mail in one inbox — Postgres, a data volume, and the public URL are wired at deploy.
Shared conversations
The team works the same customer threads. Assign, reply, and keep the history on this instance.
Admin on first boot
First run installs the app and seeds the admin from ADMIN_EMAIL and ADMIN_PASS. Change that password after login.
Public HTTPS URL
APP_URL is your https://…stackblaze.app hostname so agents and customers open the same desk.
Dedicated instance
Mailboxes, customers, and attachments stay on this instance — not in a shared vendor account.
Mail after install
Connect SMTP and IMAP in FreeScout settings once the desk is up. The template does not guess your mailbox.
Managed Postgres
Conversations live in CloudNativePG. Uploads, modules, and config persist on the /data volume.
See FreeScout in action
Deploy in seconds
One click. Postgres pre-wired.
Pick the FreeScout template. StackBlaze creates the app and Postgres, sets the public URL, and gives you a hostname.
This stack
Web
FreeScout server
PostgreSQL
managed database · TCP:5432
platform SMTP when the pipeline has mail
- Stack
- FreeScout + PostgreSQL
- First login
- ADMIN_EMAIL and ADMIN_PASS on the app
- Add SMTP and IMAP in settings after login
After you deploy
- 1
Open the public URL
The hostname is on the app page after deploy. First boot installs the schema and the admin user.
- 2
Sign in as the admin
Use ADMIN_EMAIL and ADMIN_PASS from the app env. The template default email is admin@example.com. Change the password immediately.
- 3
Connect the mailbox
In FreeScout settings, add the SMTP and IMAP accounts the team should answer. Order mail and support mail stay in this inbox.
Running FreeScout on StackBlaze
How the instance is wired
FreeScout and Postgres ship together. The public hostname is the agent desk. Mailboxes are configured inside the app.
Postgres holds the conversations
Threads, customers, and users live in the attached database. Restart the app and the inbox is still there.
Files sit on /data
Uploads, installed modules, cache, and config persist on the volume. The database is not an attachment store.
Mail is yours to connect
Point FreeScout at the mailbox you already use. The template does not send through a vendor relay unless you add one.
Add CPU when the queue grows
Raise RAM and CPU on the app from the dashboard. Postgres scales on its own.
Compare
FreeScout on StackBlaze vs a hosted help desk
| Feature | FreeScout on StackBlaze | Hosted help desk |
|---|---|---|
| Data location | Conversations and attachments live on your StackBlaze instance. | Customer mail lives in vendor-operated infrastructure. |
| Install model | One-click template. Admin is created at deploy. | Create a vendor account and use their shared platform. |
| Mailboxes | Connect the IMAP and SMTP accounts you already have. | Often limited to the host’s mail routing and plan. |
| Operations | You control updates, scale, backups, and the instance lifecycle. | The vendor operates the platform and the limits. |
| Billing | Compute, storage, and bandwidth. No per-agent fee. | Usually priced per agent or per plan. |
This template is FreeScout plus Postgres. The admin is seeded at first boot.
FAQ
Common questions
Open the public URL. Sign in with ADMIN_EMAIL and ADMIN_PASS from the app environment. Change ADMIN_PASS before you share the desk. The seeded email is admin@example.com unless you changed it.
Ready to deploy FreeScout?
One click. Dependencies pre-wired. No infrastructure to manage.