Identity and coordination
- Identity and tenancy
- Entitlements
- Audit metadata
- Opaque storage pointers
No schedules, risk registers or model outputs persisted at rest.
Client launch
Start with a secure request.
Tell us who you are and we'll come back within two working days. No schedules, risk registers, passwords or commercially sensitive scheme detail.
- You receive an SRS reference immediately.
- SOMA reviews fit, security and setup needs.
- Detailed intake follows through a private, expiring link.
Four fields · about two minutes
Request a client launch
Request received
Your launch reference
SOMA will review your request and contact you within two working days.
Keep this reference for any follow-up. It does not grant access to the Studio.
Start to go-live
A controlled launch, with a clear owner at every step.
You always know what is happening, what we need and what must be proven before access opens.
- 01
Request
Send the four-field request and receive your traceable SRS reference.
Owner · Client sponsor - 02
Qualify and invite
We confirm fit, commercials and security needs, then issue a private intake link.
Owner · SOMA launch lead - 03
Set up securely
Identity, tenant, entitlements and client-controlled storage are configured.
Owner · SOMA + client admin - 04
Prove and go live
Isolation, storage, access and user acceptance evidence must pass before handover.
Owner · Joint readiness review
No live client data until identity, storage and isolation checks pass.
Client materials
Everything needed to brief the room.
Current, concise and ready to circulate to sponsors, analysts, procurement and security teams.
01PDF · 6 pages
Risk Studio overview
A concise product briefing for sponsors, buyers and delivery leaders.
Download PDF 02PDF · 8 pagesClient launch guide
The complete request-to-go-live journey, responsibilities and readiness checks.
Download PDF 03PDF · 6 pagesSecurity & data residency
The deployment boundary, access controls and client-controlled storage model.
Download PDFThe boundary
Control plane here. Client content there.
The hosted service coordinates access and auditability. Sensitive scheme inputs and outputs remain in storage controlled by the client.
Scheme content and evidence
- Schedules and XER files
- Risk registers and mappings
- Model inputs
- Reports and outputs
Client-selected location, access policy and retention.
Clients who require no hosted processing can use the separately governed self-host deployment.
Ready when you are
Start small. Prove the boundary. Then go live.
Four fields now. The right people and evidence at every step after that.