Pricing
A dashboard either shows you all your work or it isn't one. Splitting that across a Solo and a Pro tier would mean selling a version of Dispatch that can't see half your terminals, so there is one price and it comes with everything.
Can't reach the licence server. Nothing has changed — try again in a moment.
That didn't go through. Nothing has changed.
This deploy has no licence server configured, so the account area cannot do anything yet.
$6/ month
or $60 a year2 months free
Per person, for 3 machines. Billed monthly or annually, cancel any time.
IntroductoryGoing to $9 / $90 once there are enough subscribers to justify it. Subscribe before then and you keep this rate for as long as you stay subscribed — it is the price your subscription was created at, not a discount we have to remember to reapply.
Several people?Studio is the same build at the same price per person, on one invoice, from 3 seats up. Not self-serve yet — a subscription still maps to one key.
Charging isn't switched on yet. The licence gate, seat binding and trial machinery are all built and tested — the price is what it will be, and the button below is a list rather than a checkout.
Get early accessDownload v0.1.16 →When it does switch on, the trial comes first: 14 days, no card. And nothing here becomes a checkout until something is watching /v1/health — the build refuses to produce one before then, which is the only kind of promise worth putting on a pricing page.
Nothing, for three days. Every launch asks, but an answer that cannot be reached falls back to the last signed token for 72 hours. A 5xx is treated as unreachable rather than as a refusal, and the check races a six-second timeout instead of blocking. An answer that says no — revoked, expired, cancelled — takes effect immediately, and no cached token overrides it.
Yes, within that same 72-hour window. Dispatch verifies an Ed25519-signed token against a public key baked into the build, so the check is local; it is the refresh that needs the network.
DSP-XXXXX-XXXXX-XXXXX-XXXXX. One key, up to 3 machines, entered once per machine in the activation window.
Not today. Dispatch is a Windows build — the terminal backend is ConPTY and the Studio and Rojo integrations are Windows window-level work. The licence and seat machinery already has the equivalents for the other two platforms, but the app does not ship there yet.
It stops opening at the end of the period you paid for. Cancellation is self-service through the billing portal, linked from the activation screen rather than hidden behind an email to support.
Nothing is deleted while you are gone — the key and the machines on it stay on the row, expired. But subscribing again mints a new key and emails it, with a fresh 3 machines, rather than waking the old one up: only a trial is ever upgraded in place. So a return costs you pasting one key into each machine again, and it never costs you a seat.
Yes, and Stripe does most of it. Checkout is hosted by Stripe — card details never touch this site — with automatic tax on, so VAT or sales tax is worked out for where you are and shown before you pay. Invoices and receipts live in Stripe’s billing portal, which the activation screen opens for you, and they download as PDFs. The one part not switched on yet is tax-ID collection, which is what puts a company name and a VAT number on the invoice; it is a Checkout setting rather than a rebuild, and it happens before the first charge.
Not as one purchase yet, and the reason is worth stating: a subscription maps to one key with 3 machines, so four people is four licences and there is no group invoice to raise. Studio is the plan — the same build at the same price per person, from 3 seats up, on one invoice, with a seat you reassign when somebody leaves. Nothing is withheld from it because there is nothing to withhold: this grows on people and machines, never on features.
A hard gate means our outage is your outage. That is the honest cost of licensing a desktop tool this way, and it is why the grace window, the timeout and the treat-5xx-as-unreachable rule exist at all rather than being nice-to-haves. What does not exist yet is a check that watches /v1/health and pages a human: the endpoint answers, nothing is looking at it, and that gets fixed before the first charge rather than after — which is why this paragraph says so instead of claiming otherwise. If it ever does go dark for longer than the window, the fastest lever is a build with the gate blanked — one value in one file, and a normal release.
Leave an address and you'll get one email when the 14-day trial opens — nothing before it, nothing after.
No endpoint configured. Set WAITLIST_ENDPOINT in src/lib/site.ts to any provider that accepts a POST — then this bar goes live.