Purpose
This guide is for buyers, platform teams, and security stakeholders who need deployment clarity before onboarding. Varydn supports both cloud-hosted and private deployment models, and the correct choice depends on regulatory requirements, operating constraints, and internal ownership expectations.
Cloud-Hosted
- Managed by Varydn
- Lower operational overhead
- Fastest path to onboarding
- Best where SaaS delivery meets internal controls
Private Deployment
- Greater environmental control
- Better fit for restricted or regulated environments
- Requires more planning around access and operations
- Typically paired with enterprise support and onboarding
Planning Checklist
Network, access, and environment boundaries
Repository, CI, and deployment integrations
Evidence retention and reporting expectations
Support boundaries, escalation, and change ownership
Onboarding Sequence
- Confirm the deployment model and the target integrations.
- Define repository, CI, and environment scope.
- Establish access patterns, reporting expectations, and security contacts.
- Validate policy behavior, outputs, and support procedures.
- Transition to steady-state operation with named owners on both sides.
Operational Considerations
- Private deployments require more upfront coordination.
- Reporting and evidence requirements should be agreed early.
- Onboarding should cover both integrations and operating responsibilities.
- Support expectations matter as much as technical fit.
Best Fit
This guide is most relevant for customers evaluating SaaS versus private deployment, especially when compliance, environmental control, or shared operational ownership affect procurement decisions.