The current boundary, in plain English.
Availability, reliance, data, pricing and privacy for SOMA Risk Studio (SRS) — straight answers, matched to the formal product status on the status page.
Availability and scope
Is SOMA Risk Studio generally available?
Not yet. V2.12.1 is in controlled availability — a small number of schemes, each provisioned individually with an agreed reliance boundary. The status page lists exactly what remains open.
What does submitting the public request do?
It creates a traceable enquiry reference and starts a qualification conversation. It does not create an account, issue an invitation, authorise product release or permit client data to be uploaded.
What is inside the current scope?
QSRA validation and Schedule Lens are available now, evaluated on your reference data under agreed controls. Internal quantitative results are produced as cross-check evidence.
Can SRS replace the approved external engine?
No. Risk Studio works alongside your approved engine of record, which remains the formal system of record. No SRS quantitative result is authorised for independent client reliance at this stage.
What is the status of QCRA and QSCRA?
QCRA is in supervised evaluation while formal validation completes. QSCRA is not currently offered, and no release version, date or replacement claim is made.
Should I send an XER or risk register through this website?
No. Do not email, paste or upload schedules, risk registers, credentials, scheme identifiers or sensitive client detail through the public booking, contact or request journey.
Where does client content live during an engagement?
Sensitive scheme inputs and outputs remain in approved client-controlled storage. The hosted control plane is limited to identity, tenancy, entitlement, audit metadata and opaque storage pointers.
What happens if Risk Studio Ltd stops trading?
Continuity is built into how the product is deployed, not promised on trust. Your scheme data lives in client-controlled storage that stays with you; the product can be deployed to run in your own environment; and exit terms and source-code escrow can be scoped into an engagement so you keep running if we are not there.
Why are public prices not shown?
Fees are agreed per engagement rather than published, because scope, storage and support differ per client. The engagement page explains scope and decision points; a written quote follows qualification.
Is the website or product WCAG certified?
No certification claim is made. Automated accessibility checks are part of the candidate gate, but named manual keyboard, screen-reader, zoom, forced-colours, motion and document review remain required.
Does the booking page load Cal.com automatically?
No. The booking page does not embed or contact Cal.com. Cal.com opens in a separate tab only after you select the external scheduler button, where Cal.com's own privacy and storage practices apply.
Still need an answer?
Ask a high-level question without client files or sensitive scheme detail.