Self-hosted

Run Norbix on your own servers with a self-hosted licence — what you need before you start.

Self-hosted means the Norbix backend runs on your own server or in your own cloud account. You look after the machine, the updates and the backups; Norbix gives you the software and a licence. Check every item below before you start, so you never begin an install that cannot finish.

How Norbix models it

An installation is the same software as the managed service, in the community edition:

Part	What it is
Hub, Api	The two backend services (hub.<domain>, api.<domain>)
Cloud	The web app (cloud.<domain>)
MongoDB, Redis, EventStore, MJML	The data tier: data, cache, the event store, email rendering

Prerequisites

• A self-hosted licence. Get it in Cloud → Account → Licensing — the only place to get one. See Licensing and Licences. The installation reads it from NORBIX_LICENSE.

• A domain with the DNS records from Licensing → DNS records, and a TLS certificate for it. The licence is bound to this domain.

• A Linux server with a public IP address, reachable from the internet on cloud.<domain> (the licence proof), and with outgoing internet access (the licence check every 6 hours).

• Secrets you keep safe: the key that encrypts every stored secret (NORBIX_SECRETS_AES_KEY_BASE64) and the key that signs sign-in tokens (the JWT key). Losing the secrets key makes every stored secret (integration keys, the licence) unreadable — back it up.

Install methods

A method gets its own page here only after its maintained script was run end to end. No method has passed that check yet, so no install page is published. Until then, use the managed service, or ask us about an Enterprise setup.

Where you use it

• Licensing · Keys and environments · Enterprise

• After the install, Cloud, the SDKs and the CLI work the same way as on the managed service — only the addresses change (Base URLs).