Pay for the walls, not the pixels.

Exactly what it says. Solo is self-serve: you get the setup notes that come with your build, and that is the whole of it. There is no support queue, no ticket address, no response-time promise, and nobody to escalate to. If you write to us about a Solo account we may not answer, and we would rather tell you that now than have you discover it on a bad day.

That isn't us being difficult — it's the actual reason the plan is $7 instead of $19. Support is the expensive part of this business, so the plan without it is the cheap one.

Solo suits someone who is comfortable reading notes and fixing their own server. If you'd rather have a person to write to, that's Team, and you can move up whenever you like.

Yes, whenever you want. Tell us and we'll move the account across — the same devices, the same audit history, nothing deleted and nothing to reinstall.

The usual trigger is a second person needing their own login, or a second client whose machines shouldn't be visible alongside the first one's. Both of those are Team, because tenant separation and named technician accounts are what Team is.

It works in the other direction too. If you scale back down, say so and we'll move you to Solo rather than quietly keep billing you for technicians you no longer have.

The software. There isn't a difference — it's the same three services either way: the console, the rendezvous server that introduces two machines, and the relay that carries traffic when they can't reach each other directly.

Self-hosted means you run that stack from one compose file on your own box. It's AGPL-3.0, so it costs nothing and you can read every line of what you're running. You also own the backups, the certificates and the 3 a.m. restart.

Hosted means we run it, patch it and keep it up, and you get a console account. That is the whole of what you're paying for. If you want to self-host and have us on call, that's the Enterprise / self-hosted plan.

Today our hosted server runs from Europe. Sessions go directly between the two machines wherever the network allows it — the relay only carries the picture when a direct path can't be made, and it can't read what it carries.

If the answer has to be a specific country, that's what Enterprise is for. We measured it before offering it: from Jeddah, a Jeddah region answered in 29 ms against 95 ms to Europe, on 3 September 2026. Region is a real engineering decision here, not a dropdown, so tell us the requirement and we'll quote the deployment.

Self-hosting is always available, on every plan, if the only acceptable answer is “on our own hardware”. What the hosted console stores is set out on the privacy page.

A named console account that can start a session — the owner, admin and technician roles. You're billed for the people who connect to machines, not for the machines: devices are unlimited on Solo, Team and Enterprise alike.

Viewer accounts don't count. A viewer's token is refused by the server before pairing, so read-only is enforced rather than promised, and you can hand one to an auditor or an account manager without paying for it.

Named means named. Sharing one login between four technicians defeats the audit log, which is most of what you're buying. Solo is deliberately a single account — the moment there are two of you, it's Team.

Personal is one account and up to five devices. If you just need more machines and you're still the only person using it, that's Solo — same single account, no device limit, $7 a month.

If a second person needs their own login, or you need one client's machines walled off from another's, that's Team. Those are the things Team is.

We won't cut a session off mid-call to make the point. Tell us and we'll move the account across. And if you'd rather not pay at all, self-hosting has no device limit and no seat count — that option stays open on every tier.

Yes. The server, the console and the client are AGPL-3.0. There is no licence key, no seat check and no licence server to call in the build you run yourself — if we disappeared tomorrow, your deployment would carry on working.

This project builds on other people's open-source work, and the licences and upstream credits are set out in full on the open source page.

Not yet, and we'd rather say so than waste your afternoon. Our builds aren't code-signed, which means Windows SmartScreen will warn about them and macOS Gatekeeper will block them outright until the certificates are in place.

So we're onboarding by hand: you tell us what you're trying to do, we get you a build that works and walk you through the first device. It's slower than a download button and it's the reason every button on this page opens a form instead.

Check the alternatives' own price pages — list prices change, and we'd rather not print a number that goes stale. Two things to look for when you do: whether the price is per technician or per seat, and whether keeping one client's machines away from another's costs extra.

Price isn't really the argument anyway. If it were the only thing that mattered, self-hosting is free and you should do that. The reason to pay is the wall between your clients, the log that proves what happened, and — above Solo — someone to write to.