Every client on their own hostname
Tickets, users, and branding resolve from the address your client visits. One deployment serves all of them, and none of them can see each other.
Simple, Fast, Reliable
The Help Desk Software that just feels Simple.
Help Desk Horizon gives every client you support their own hostname, their own branding, and their own strictly isolated data — from one console your technicians actually want to work in.
Already a client of an MSP that uses Help Desk Horizon? Use the address they gave you — your service desk lives on their hostname, not this one.
What it does
Ticket numbers that mean something
RIVDEN-00001 belongs to Riverside Dental and NGLAW-00001 to Northgate Law. Numbering runs per client, not per system, so a ticket key tells you whose it is.
Your brand, not ours
Product name, accent colour, and login copy are yours, down to the individual client if you want. Colours are contrast-checked on the way in, so a brand palette can never render the interface unreadable.
Internal notes that stay internal
A note marked internal is filtered out server-side for client users. It is absent from the response, not hidden with CSS — the difference matters the first time someone opens developer tools.
A portal without a learning curve
Your client's staff raise a ticket, see their own history, and reply. Requesters see only their own tickets; their admins see the whole company's.
An audit log you cannot rewrite
Every consequential action is recorded, and the application's own database role holds no permission to update or delete those rows. Including when platform support views a tenant — which the tenant sees in their own log.
Isolation in three layers
Client data separation is the whole job. One layer is a single bug away from a cross-tenant leak, so Help Desk Horizon enforces it three times independently.
Each layer is covered by tests that run against a real database, including tests that deliberately attempt cross-tenant reads and writes.
- The request knows its tenant. Resolved from the hostname before authentication, and never from anything a caller can set — no query string, no header, no form field.
- The data layer enforces it. Every query is scoped by convention rather than by remembering, and a write aimed at another tenant throws instead of succeeding quietly.
- The database enforces it again. Postgres row-level security on every tenant table, with the application connecting as a restricted role. A missed filter or a hand-written query still returns nothing. Policies fail closed: no tenant, no rows.
Request a demo
Tell us what you run today and we'll show you the parts that matter to you.
What you send is stored so we can reply to it, and used for nothing else.