Deployment patterns
Pick the operating model that matches your team, not a generic SaaS funnel.
ZNYX has three real operating models: runtime only, runtime plus hosted console, and full private deployment. This page makes the boundary explicit so procurement and architecture reviews do not have to infer it from scattered copy.
Starter
Open-source runtime only.
- Runtime runs in your infrastructure
- No console dependency
- Local policy files and docs-based onboarding
- Best for developer evaluation and small single-team rollouts
Growth
Self-hosted runtime with hosted console.
- Runtime still runs in your infrastructure
- Hosted console for policy workflow and operations
- Metadata-first hosted visibility by default
- Best for teams that need shared rollout and trace operations
Enterprise
Optional self-hosting for both runtime and console.
- Private deployment for both runtime and console when required
- Custom packaging, procurement, and deployment planning
- Suitable for air-gap or security review constraints
- Custom pricing and support model
| Capability | Starter | Growth | Enterprise |
|---|---|---|---|
| Runtime location | Customer infrastructure | Customer infrastructure | Customer infrastructure |
| Console location | Not applicable | Hosted by ZNYX | Hosted by ZNYX or customer infrastructure |
| Default hosted visibility | Not applicable | Operational metadata | Deployment-dependent |
| Who manages rollout workflow | Local team | Shared team in hosted console | Shared team in hosted or private console |
| Typical buying trigger | Initial evaluation | Operational coordination | Private deployment requirement |
Selection rule of thumb
Start on Starter if the question is still "does the runtime fit our app?" Move to Growth when the question becomes "how do multiple people manage rollout and operations?" Move to Enterprise when the question becomes "where is the console allowed to run?"