Cloud vs. self-hosted
Orbit ships in two deployment forms. Both run the exact same application — there is no “lite” self-hosted edition and no cloud-only feature held back from self-hosters.
| Orbit Cloud | Orbit Self-Hosted | |
|---|---|---|
| Where it runs | Kuzium’s infrastructure | Your own server |
| Your data | Lives on Kuzium’s infrastructure | Never leaves your server |
| Setup | Create an account, log in | Run the installer against your own domain |
| Updates | Automatic | One click in Settings → Updates, with rollback |
| Licensing | Included in your plan | A license file caps seat count and expiry |
| What Kuzium sees | Normal SaaS operation | Only a periodic license check-in — seat count and |
| version, nothing else |
Choosing cloud
Section titled “Choosing cloud”Cloud is the fastest way to start — create an account and you’re in. It’s the right choice if you don’t want to manage servers, TLS certificates, or updates yourself.
Choosing self-hosted
Section titled “Choosing self-hosted”Self-hosted is the right choice when your data has to stay on infrastructure you control — compliance requirements, internal policy, or simple preference. A license file caps your seat count and expiry, checked in over the internet, but losing connectivity or letting a license lapse never breaks the running app — it only pauses adding new seats and pulling updates. See the self-hosted guide to get started.
Moving between them
Section titled “Moving between them”Because it’s the same product and data model either way, moving from one deployment to the other is a data migration, not a rebuild — nothing in your setup has to change shape to move.