Self-hosted deployment
Run the whole application on your own infrastructure, licensed flat rather than metered.
What changes, and what doesn't
This is the exact same application — same backend, same frontend, same docker-compose stack — running on infrastructure you operate instead of ours. There is no separate self-hosted edition or installer to learn.
Set DEPLOYMENT_MODE=self_hosted in your .env before the first start. This does two things: it enforces a single organisation at the API layer (a second organisation is rejected outright, not just discouraged), and it switches /login and /register to a plain email-and-password form by default, since a self-hosted deployment has no access to Noviqent's own Keycloak realm.
What you need to bring
Your own Postgres and Redis (docker-compose.yml provisions these for you if you don't already run them elsewhere), and your own key for whichever AI provider you want the reasoning stage to use — Claude, GPT, Gemini, Grok, or a private-hosted endpoint you already run, exactly the same choice the hosted product offers.
Keycloak SSO, Noviqent Vault, and the usage-based billing platform are all optional integrations, not requirements — every one of them degrades gracefully to "not configured" when its settings are left blank, the same way they already do for local development.
How it's licensed
Self-hosted is licensed as a flat fee, not through the metered usage billing the hosted product uses — a self-hosted instance never reports usage back to Noviqent at all, since we don't operate the infrastructure to observe it. Contact hello@noviqent.co.uk to arrange a licence.
There is no technical licence-key enforcement built into the application itself. This is a deliberate, documented simplification, not an oversight — the same approach the rest of the Noviqent fleet's self-hosted options already take.