On this page0
Unfamiliar word? See Glossary: words used in these docs. Looking for the tasks in order? Begin at Start Here.
Reference
How We Provision Your Instance
There is nothing for you to install. Zonitix provisions a dedicated, single-tenant server for your company. We host and monitor your server. Zonitix releases are installed automatically in a weekly maintenance window when that is switched on and email is set up, which is the choice pre-selected in the first-run setup wizard; an administrator can apply them by hand instead. Operating-system security patches follow the same window or are applied by hand. Backups and restores are your administrator’s to set up and run. You sign in and start configuring.
We Stand Up Your Instance
After your order is confirmed, we provision a server that runs the application and its database for you alone. It is not shared with any other customer.
We Configure & Secure It
We generate the encryption keys for your instance, set up its web address, and register it with the Zonitix licensing server before handing over access.
We Host & Monitor It
We host the server and monitor it. Each Zonitix release is published to your instance. It is installed automatically in a weekly maintenance window when that is switched on, or an administrator applies it from System → Updates; server security patches follow the same schedule or are applied by hand there. You are never asked to run a deploy or log in to a server.
You Sign In
You receive the “Your Zonitix instance is live” email with the address of your instance and a one-time setup key. You enter the key and the setup wizard takes three steps: Admin Identity, where you create the primary administrator; Updates, where you choose between “Update automatically, once a week” (already selected) and “I’ll install updates myself”; and Review & Launch. After signing in, the first job is backup setup, because a new instance is locked until it is done. Then you add admin accounts, check mandatory MFA, and connect your identity provider.
Good To Know
Your instance is provisioned with its own encryption key, generated at build time and unique to you. It encrypts your MFA secrets and integration credentials, and is never shared with another customer's instance.
What This Means For Your Company
Your instance runs on a server that hosts only your company. Employee records, résumés, stored credentials and financial records are kept in a database on that server, not in a database shared with another customer. The Zonitix licensing server (the store) receives licence check-ins and holds your billing details; what a check-in contains is listed on Heartbeat (License Check-In).
Operation & Compliance
Module Management
How We Size Your Instance
You do not buy or manage this hardware — we provision it. We choose the server size from your scale (team size and activity), not from your feature plan: a Core customer running a large team gets a larger server, and we resize it for you as you grow. No plan limits headcount.
No capacity figure is published: there is no tested number of users, devices or requests that a server size supports. The figures the product itself works with are in the technical part below.
If something here is not working as you expect, start with When something goes wrong.
The plain explanation is above. This part is for IT and developers: the exact settings, permission names, API addresses and data fields behind it. Closed: select the heading above to open it. While it is closed, your browser’s find-on-page (Ctrl+F or Cmd+F) does not search this part.
Services And Internal Ports
Your instance is a set of containers, one per service. The gateway is the only service that takes requests from outside; the rest listen on the instance’s internal network. Alongside them run PostgreSQL, Redis and a local model runtime for the private AI features; the versions are listed under Components And Versions, and who hosts each part under Who hosts what.
| Service Name | Internal Port | Responsibility |
|---|---|---|
| API Gateway | 8000 | Dynamic routing, rate limiting, and trusted user headers insertion. |
| User Management | 8001 | RBAC policies, permission records, user setup, and license sync scheduler. |
| Identity & Auth | 8002 | JWT generation, MFA (WebAuthn/TOTP) validation, and session cleanup middleware. |
| Workflow | 8003 | Workflow definitions, runs, task queues and the automation worker. |
| Integration | 8004 | Identity hooks, directory sync and provisioning calls to connected providers. |
| Security Lab | 8005 | Automated port-scanning runner, vulnerability testing, and AWS mapper backend. Runs when licensed. |
| Compliance | 8006 | Compliance Hub, reporting, backups, updates and key escrow. |
| Logging | 8007 | The audit log and log forwarding. |
| Device | 8008 | Device inventory, enrollment and the device agent. |
| AI | 8009 | Private AI assistants and scoring against the local model runtime. |
| Document Parser | 8010 | Document text extraction for recruiting, finance and Security Lab. Runs when one of them is licensed. |
| Recruitment | 8011 | Jobs, candidates, interviews and offers. |
| Signature | 8013 | Zonitix Sign: sends, seals and stores signed documents. |
Server size. We size the server for you; server size follows your scale, not your plan. Your instance reports its software version and user count to us on each heartbeat, and the Overview tab of your customer dashboard shows both. Host size is not among them: the instance measures its own CPU cores and memory, but the Zonitix licensing server does not read those figures.
Memory ceilings. Each of those containers has a fixed memory ceiling, and the ceilings are the same on every server size. With every plan-dependent service started, the ceilings of all containers other than the local model runtime add up to about 7.6 GB (7,776 MB). The model runtime has its own ceiling, 8 GB by default, which is a deployment setting and not something the app changes.
A ceiling is the most a container may use; it is not memory set aside for it. The stack definition sets aside memory for one container only, 2 GB for the model runtime. So these figures are arithmetic on upper bounds, not a measurement of what an instance uses.
The per-container figures are listed under Container Hardening That Is Configured. None of this is a statement of how many people or devices a size supports; no such figure is published.
The Sizing Figure The Product Computes
On each license check-in the instance reads its own CPU core count and memory and computes what its code calls recommended seats: by default 12 for each GB of memory or 25 for each CPU core, whichever gives the smaller number, and never less than 10. After a check-in that succeeds, the instance keeps the result and returns it as seats.recommended, next to the number of active accounts, from GET /api/v1/user-management/license. It is a rule of thumb written into the code, not a measured capacity and not a limit: nothing in the product stops you adding accounts past it, no plan has a headcount limit, and the Zonitix licensing server does not read it. No tested figure for users, devices or requests per second is published.