Service OS Pro
Choose how you want to carry the operating system.
Every Service OS Pro engagement starts with the same paid working session. The decision after that is whether CSS operates the system with you or you pay to own your deployment.
Engagement Workshop
Map the workflows, SOPs, KPIs, selected capabilities, and ownership plan. You leave with the Build Document whether or not you continue.
Start the workshopFully Managed
CSS carries the operating layer while you use it: hosting, patching, backups, support, ongoing tuning, and future improvements as shipped.
Choose managedPay to Own
Pay toward an owned software asset over 12 payments. The workshop is separate, so the all-in cash outlay is clear.
Explore ownershipSelf-Hosted after payoff
Run the owned deployment yourself. You pay CSS $0/month; you still own hosting, monitoring, security, backups, maintenance, and other operating costs.
Review ownershipSupported Ownership
Keep ownership while CSS covers platform costs and provides three development hours each month.
Discuss supportThe workshop is not a credit toward a path. Fully Managed has no published cancellation or minimum term — the written agreement states the terms, and nothing here should be read as one. Ownership is a commercial choice, not a promise that software runs without cost. A configured launch typically follows in 2–3 weeks after the workshop and required inputs — typical, not a delivery guarantee.
Is the workshop credited?
No. It is the required first step and produces your Build Document.
Can I self-host immediately?
The self-host option follows the ownership path described in the agreement.
Does $0 mean no costs?
No. It means $0 paid to CSS — hosting, monitoring, security, backups, and maintenance are yours to carry.