Identity and coordination
- Identity and tenancy
- Entitlements
- Audit metadata
- Opaque storage pointers
No schedules, risk registers or model outputs persisted at rest.
Request access
Start with four safe fields.
V2.12.1 is in controlled availability — a small number of schemes, each provisioned individually with an agreed reliance boundary. This request starts a conversation; it does not create an account, authorise release or start client onboarding. No schedules, risk registers, passwords or commercially sensitive scheme detail.
- Online submissions receive an SRS reference in the confirmation response when the secure service is available; email requests receive a reference in our reply within two working days.
- SOMA reviews fit, security and setup needs.
- Detailed intake can follow only after fit and readiness checks.
Four fields · about two minutes
Request access
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.
Request to decision
No account or client use opens automatically.
The request starts a conversation. Every later step — scope, security boundary, evidence — is agreed with you before anything is provisioned.
- 01
Request
Send the four-field request and receive your traceable SRS reference.
Owner · Client sponsor - 02
Qualify
We confirm fit, the controlled scope, commercials and security needs. No invitation is implied.
Owner · SOMA launch lead - 03
Confirm readiness together
Identity, storage, accessibility, numerical and security evidence is completed against one exact build.
Owner · Named reviewers - 04
Record a clear decision
Controlled onboarding or client use begins only after an evidenced go decision.
Owner · Release and client acceptance owners
No live client data, invitation or relied-upon result is authorised by this request.
Client materials
Accessible current-state material.
These HTML pages remain the primary current source. Machine-checked, tagged PDF companions are available from the resources page.
01Accessible HTML
Current product boundary
Module status, current availability and explicit exclusions.
Open accessible page 02Accessible HTMLEvidence and status
Current candidate status, limitations and the reviews that remain open.
Open accessible page 03Accessible HTMLSecurity & data handling
The control-plane boundary and client-controlled storage model.
Open accessible pageThe 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.
Request access
Start small. See every step.
Four safe fields now. No account, client data or product release follows without a separate evidenced decision.