Deployment
Choose the Atlas deployment model that fits your operating environment.
Atlas commercial terms are scoped around deployment responsibility, operational boundaries, data migration, and rollout complexity. Public seat pricing is intentionally omitted so the deployment conversation can stay accurate.
SaaS Platform
Atlas-operated deployment for teams that want the product live quickly.
- Atlas-managed application hosting and operational ownership
- Structured onboarding around your data sources and workflow scope
- Access to core Atlas surfaces: planning, documents, monitoring, and governance
- Fastest path to evaluation and rollout
Customer-Managed Deployment
Licensed Atlas deployment in your environment or private cloud.
- Licensed Atlas software deployed in your infrastructure boundary
- Customer control over environment ownership and operational perimeter
- Infrastructure automation and deployment planning aligned during scoping
- Best fit for firms with internal platform, security, or hosting requirements
Enterprise Services
Implementation, migration, and rollout support around either deployment model.
- Data intake, migration, and workflow scoping
- Environment planning for Atlas-operated or customer-managed deployment
- Rollout sequencing across advisory, operations, and principal-safe surfaces
- Integration and operating-model alignment for complex teams
What changes across deployment tracks
| Dimension | SaaS Platform | Customer-Managed | Enterprise Services |
|---|---|---|---|
| Environment Operator | Atlas operates the live environment. | Your team operates the environment running licensed Atlas software. | Support program around either environment model. |
| Control Boundary | Atlas-managed operational perimeter. | Customer-controlled hosting and infrastructure boundary. | Shared implementation planning and program governance. |
| Best Fit | Teams prioritizing speed to evaluation and rollout. | Firms requiring customer-managed or private-cloud deployment. | Programs with migration, integration, or rollout complexity. |
| Implementation Motion | Structured onboarding around current workflows and data inputs. | Deployment planning, environment alignment, and licensed rollout scope. | Scoped migration, integration, and operating-model support. |
| Product Direction | Atlas operating surfaces stay unified across planning, documents, monitoring, and governance. | Atlas operating surfaces stay unified across planning, documents, monitoring, and governance. | Services align delivery around the same Atlas operating system. |
Common Questions
Why is there no public rate card?
Atlas commercial scope depends on who operates the environment, which surfaces are being rolled out, and how much migration or implementation work is required.
Can Atlas run in our environment?
Yes. Atlas supports customer-managed licensed deployment for teams that need infrastructure control or private-cloud boundaries.
Do you still offer Atlas-operated SaaS?
Yes. Atlas can also be deployed as an Atlas-operated SaaS platform for teams that want the fastest route to evaluation and rollout.
What does a deployment review cover?
Deployment reviews focus on operating boundaries, household workflows, data intake, reporting surfaces, and which delivery model best fits your environment.
Does the deployment model change the product story?
No. Atlas remains one proprietary operating system. The deployment model changes operational ownership and implementation shape, not the need to split the product into disconnected stacks.
Ready to see Atlas as an operating system for your firm?
Request a deployment review covering Atlas-operated SaaS, customer-managed deployment, and the workflows you want under one operating layer.