SupportHub on your own server

Enterprise Dedicated is the same product as the cloud one, installed on your machine. Conversations with your customers stay in your infrastructure; the product runs under a license bound to that server.

There is no self-service purchase and no price on this page: first we look at how many operators you have and what load to expect, then we quote terms.

Request itRequirements and install

The button opens an email to sales, not a checkout.

How it differs from Enterprise Cloud

Both forms of Enterprise have the same features. Everything else differs: whose server it is, who maintains it, where the data sits and what happens when the license runs out.

Where it runs
Enterprise Cloud
A dedicated instance on our servers
Enterprise Dedicated
On your own server, as a closed build
Who maintains the machine
Enterprise Cloud
We do: updates, backups, monitoring
Enterprise Dedicated
You do. Updates install from a button; backups are yours
Where the data sits
Enterprise Cloud
With us
Enterprise Dedicated
With you; conversations and attachments never leave
Updates
Enterprise Cloud
They arrive by themselves; nothing is asked of you
Enterprise Dedicated
When you decide: a button in the cabinet or the same install command
License
Enterprise Cloud
Not needed: everything is on our side
Enterprise Dedicated
A token bound to the server, checked every six hours
How it is arranged
Enterprise Cloud
Agreed with us, with a monthly price
Enterprise Dedicated
Only by agreement, with no self-service purchase

Server requirements

Nothing is built on your machine: we ship ready-made images. That is what keeps the requirements low — building the frontend alone asks for about 8 GB of memory.

System
Minimum Debian 13, amd64Recommended Debian 13, amd64
Dedicated cores
Minimum 2Recommended 4
Shared (burstable) cores instead
Minimum 4Recommended 6–8
Memory
Minimum 4 GBRecommended 8 GB
Swap
Minimum 2 GB, requiredRecommended 2 GB
Disk
Minimum 40 GB SSDRecommended 100 GB SSD
Operators
Minimum up to 5Recommended up to 25

Debian 13 or newer only, amd64. Ubuntu and other distributions are not supported: one tested system instead of a zoo, so our updates don't drift away from what you run. An arm build is a separate request.

The numbers come from a server with dedicated cores. On an ordinary VPS they are shared and oversubscribed, so take about twice the nominal count. Check steal time separately: consistently above 5 per cent and we can't promise responsiveness. The installer measures it as its first step.

Disk is sized by attachments, not by the database: the database takes about 1.6 KB per message. Attachment retention and offloading to S3 are the two levers inside the product.

How delivery works

Ready-made images

We do the build and hand you a single file with the images. Nothing is compiled on your server and nothing is pulled from public registries. Checksums and the signature are verified before anything is unpacked.

A one-command install

One line in the terminal: the installer checks the server, installs Docker, fetches the bundle, fills in the settings, sets up nginx and issues the certificate. Then the first-run wizard creates the owner and the first project.

Updates from a button

The License section shows which version is out for you and whether it changes the database schema. On a press, the service on your server takes a database backup, fetches the update, verifies it and switches the version — and if that doesn't work out, it puts the previous one back by itself. There is no automatic updating.

Support access behind a checkbox

Until the checkbox is ticked there is no account for us on the server, no key and no sudo rule. Tick it and we come in for the length of the session and only with our own key; untick it and the key is removed and open sessions are cut. The engineer who comes in will have root, and we say so plainly.

What the install looks like

curl -fsSL https://get.supporthub.cc/install | bash -s -- \
    --key SHLIC1.… \
    --domain support.example.com \
    --api-domain api.support.example.com \
    --email admin@example.com

The license token in the command is required: the address the bundle is fetched from comes out of it. Running it again with a newer bundle is an upgrade — settings, database and setup code stay where they are.

Air-gapped networks

If the server has no way out to the internet, the bundle arrives as a file and the license is activated offline: you send the server fingerprint, we issue a receipt. Tell us up front — it changes the order of the install and what we send you.

What to read next

How to get a licenseWhat to send us, what comes back and what to do with the token you get.Installing on your own serverRequirements, the one-command install, the step-by-step install and what to do when something doesn't come up.Updates and support accessWhat the Update button does, what you see while it runs and where the limits of support access are.

Request a delivery

Write to us with how many operators will work in it, what load to expect and whether you have data-residency requirements. We'll say what of that fits on one server and quote the terms.

Request itsupport@forestsnet.com