Whether you need a fully managed SaaS platform, a simple self-hosted setup, or a distributed architecture across separate SecureOne and agent nodes, SecureOne gives you the flexibility to deploy based on team size, operational maturity, and compliance needs.
Start here: this visual shows how control plane and scan execution can be separated when needed.
Compare the three most common ways teams deploy SecureOne.
Ideal for teams that want fast time-to-value and minimal infrastructure management.
Best for evaluation environments, internal labs, and teams that want everything on a single host.
Best for enterprises that want SecureOne and scanning infrastructure on separate machines or domains.
| Requirement | Recommended Model | Why |
|---|---|---|
| Fastest rollout | SaaS | No infrastructure management and fastest onboarding |
| Single server deployment | All-in-One | Keeps application, database, agent, and CI together |
| Separate app and agent nodes | Distributed | Supports separate domains, scaling, and operational isolation |
| Enterprise CI/CD segmentation | Distributed | Lets scan workloads live independently from SecureOne app services |
Start with the model that matches your current requirements, then evolve into distributed deployment as your scale, compliance, or CI/CD isolation needs grow.
