Deployment options aligned to how regulated teams actually buy.
For many buyers, deployment model determines whether evaluation can proceed at all. Cyblox supports different operating patterns so teams can review the product within the constraints they already manage.
Deployment is not an implementation detail. It is a control boundary.
Security, data handling, support model, and review scope all change depending on where the product runs and which components remain under customer control.
Customer-controlled / on-premises
Deploy within infrastructure you control when sovereignty, internal review policy, or network boundaries require local ownership.
- Runs within customer-managed environment
- Aligned to stricter review boundaries
- Suitable where external dependency is constrained
Hybrid
Use a mixed model when local execution or data boundaries need to coexist with more centralized coordination and support.
- Balances control with operational flexibility
- Can reduce review friction versus full SaaS adoption
- Useful for phased enterprise rollouts
Air-gapped
Support disconnected environments where the core operating model does not permit external connectivity.
- Designed for isolated environments
- Supports stricter network assumptions
- Reviewed differently from connected deployments
The right model depends on review scope and operating ownership.
Teams usually compare deployment options based on who runs the platform, where sensitive data resides, how support works, and what external connectivity is required.
Control expectations
Understand who owns infrastructure, upgrades, access administration, and operating procedures.
Connectivity assumptions
Review whether external access is required, optional, or disallowed for the environment in scope.
Support model
Different models change how support, upgrades, and troubleshooting are coordinated.
Rollout path
Many teams start with one model and expand only after technical, legal, and security review are complete.
Choose the model that matches your review constraints first.
The fastest path is usually the one that fits existing governance, not the one with the fewest deployment steps on paper.
Best when customer control is mandatory
On-premises or customer-controlled models are often preferred where data sovereignty or internal hosting policy is non-negotiable.
Best when flexibility matters
Hybrid can fit teams balancing local control, central oversight, and phased adoption.
Best when connectivity is unacceptable
Air-gapped deployments align to environments with stricter isolation and offline operating assumptions.
Need a deployment discussion grounded in your operating model?
We can walk through which deployment pattern best fits your review requirements, support model, and control boundaries.