Yes. Add your domain in Settings and publish the two DNS records shown. It goes live with its own certificate, usually within minutes, and clients see your logo and favicon instead of ours.

Every row carries the workspace it belongs to, and row-level security in Postgres filters each query against the signed-in session. The rule lives in the database, so a page that asks for the wrong data gets nothing back rather than relying on the interface to hide it.

Their own orders, invoices, subscriptions and tickets — nothing belonging to another client, and none of your internal views. The client role is the narrowest of the five access levels.

Yes. A checkout form can offer several services, each with its own packages, and a client can add any combination with quantities before paying once. Each line becomes its own order so delivery stays trackable per item.

No. Most teams start by publishing one checkout link and letting new orders land in ServeDeck while old work finishes where it is. Clients and services can be added as you go rather than in a migration weekend.

No. Every order has a client thread and a team-only thread. Mentions and internal notes in the team thread never reach the client’s portal.

Replies come back into the ticket they belong to, so the thread stays on the client’s account instead of in one person’s inbox. Your team answers from the console and the client receives it as ordinary email.