Choose where the control layer lives.
The control model is the same either way. What differs is the boundary: a managed cloud workspace, operated for you, or a private deployment inside an environment you designate. This page lays the two options side by side so the trade-offs are explicit.
The right deployment depends on your boundaries, not our preference.
Some organisations want to start without owning infrastructure decisions. Others have obligations or policies that require the platform to sit inside an environment they control. Both are reasonable starting points, and both deserve a straight comparison.
What should not differ is the governance: roles, approvals, records and review work the same way in either option. Deployment changes where the platform runs and who operates it — not how authority works inside it.
- Uncertainty about where data physically and contractually sits
- Unclear responsibility when something needs operating or fixing
- Policies or counterparties that require a dedicated environment
- A first phase that should start managed, with room to change later
Deployment is a scoping decision, not a sales default.
We decide it together, from your constraints outward.
Two options, one control model.
Short, honest phrases — the detailed answers are confirmed during scoping, not asserted here.
| Consideration | Cloud workspace | Private deployment |
|---|---|---|
Straight about options. Silent about guarantees.
Within its role
- Offer a managed cloud workspace and a private deployment path
- Keep the same control model — roles, approvals, records, review — in both
- Write down responsibility boundaries before work starts
- Revisit the deployment choice as requirements change
Always with people
- Claim certifications, compliance or availability levels that are not evidenced
- Assert security properties in marketing copy — specifics belong in diligence, via Trust
- Treat deployment as permanent — the option stays open deliberately
- Hide shared responsibilities behind the word “managed”
See deployment on one real workflow.
Bring us one operational pressure. We will show how this capability would apply, where authority would sit, and what the record would look like.