Service Plans
Zero Trust Access is billed per user onboarded to the platform. Costs scale naturally with your actual usage — you only pay for the users who need access.
Pricing Model
Zero Trust Access is charged on a per-user, per-month basis. The unit price is confirmed at onboarding and reflects the number of users registered on the platform.
Per-User Billing
Each user registered on the Zero Trust platform counts as one billable seat. Pricing is agreed at the start of the service and reviewed at each renewal or user-count change.
Cost Scales with Usage
If Zero Trust is used only for infrastructure administration (SSH, RDP, Kubernetes), user counts tend to be small — typically a handful of platform operators. Costs rise only if the service is extended to end users consuming internal applications.
Estimating Your User Count
The number of users required depends on the use cases you enable:
| Use Case | Typical User Count |
|---|---|
| SSH / RDP to infrastructure | Low — server administrators only |
| Cloud management portal access | Low — platform operators only |
| Kubernetes control plane access | Low — developers and cluster admins |
| Internal web application access | Variable — can include a large number of end users |
Start by mapping each application or resource you plan to protect, then count the distinct users who will need access to any of them. That total is your billable seat count.
Getting Started
To onboard, provide UNICC with:
- Your chosen identity provider (Entra ID, Google Workspace, SAML, or OIDC).
- The list of applications or resources to be protected.
- The estimated number of users who will require access.
A UNICC engineer will configure the policies, set up secure tunnels to your private resources, and validate access before Go Live.