Deployment & Licensing
Run it where your data
has to stay.
Regulated data does not move for a software vendor's convenience. Quadrazene installs where the data already is, runs without calling home if it must, and gives the people operating it one tool for the whole lifecycle.
Four ways to run it
Same product, your choice of boundary.
The license carries the environment, so the platform behaves correctly in each without configuration drift.
On-prem
self-hostedYour servers, your network. License from an environment variable or a file; call-home optional, for instance only when a VPN is available.
Your VPC
self-hostedIn your cloud account, with call-home enabled so heartbeat and usage reach us.
Air-gapped
offlineNo outbound connection at all. Licenses verify offline, and usage is exported as an encrypted file you hand over yourself.
Managed
SaaSWe run it. Tenants and licenses live in the platform's own database, with no key files to manage.
One operator CLI
The lifecycle is a command, not a runbook.
Installs are scripted and portable, so the tenth box is the same as the first.
Built for the people on call
Upgrades that tell you what they will do.
Release manifest
Every release carries a manifest of the database migrations since the last one, each flagged if it drops a table or column. The tool reads it; nobody types flags from memory.
Safe upgrades
An upgrade enforces the minimum version you may upgrade from and refuses a migrating release unless you take a backup or explicitly confirm.
State outside the app folder
Uploaded files live in a directory that an upgrade does not replace, and an older layout is relocated automatically.
TLS as a command
Install an internal-CA certificate with validation of the key match, SAN and validity, or use certbot. Renewal follows the mode you chose.
Doctor
A single diagnostic pass over the database, services and config, so the first support question is already answered.
Health endpoints
Liveness and readiness endpoints for your load balancer and orchestrator.
One install, many tenants
Isolation you can hand to separate business units.
Single or multi
Install single-tenant with the setup wizard, or multi-tenant with a platform admin and a reserved system tenant. A single-tenant box can be upgraded to multi later.
Per-tenant everything
Users, roles, connections, content, the audit chain and settings are all scoped to the tenant.
Tenant settings
Runtime tunables, such as refresh defaults, timeouts and confirmations, are tenant settings with sensible defaults, not values baked into code.
Limits in the license
Maximum tenants, users per tenant and monthly usage are entitlements the license carries and the platform enforces.
Default sign-in
A tenant can choose the default sign-in method its users land on.
Branding
Per-tenant logo and branding for a workspace that looks like theirs.
Licensing
Buy the parts you use.
Products are independently licensable. Enforcement rejects a request to an unlicensed product before it reaches the handler, and the UI hides what you don't have.
Signed and offline-verifiable
Licenses are cryptographically signed and checked without a network call, so an air-gapped box validates them the same way.
Four pillars, sold separately
Insights, Advisory, Actions and Governance are independently licensable, and a Chain can only use the pillars you own.
Usage you can audit
Call-home is optional. Where it is off, usage exports as an encrypted file you review before sending.
Tell us where it has to run.
On-prem, VPC, air-gapped or managed: we'll walk through the install and the license that fit your boundary.