Security
Your environment.Your data.Your decisions.
Every customer runs Sofie in its own isolated AWS environment, with enterprise sign-in, encrypted data, human approval for consequential actions and a traceable history of who did what.
Eight commitments, in every deployment.
These apply to every customer deployment.
An isolated deployment for every customer
Your own AWS environment for the application and database: a dedicated VPC, private subnets and an encrypted database.
Your data never trains a model
Customer content is used to do your work, and nothing else.
Enterprise sign-in
SAML SSO with Okta, Entra ID, Google Workspace and more, passkey MFA and configurable idle timeouts.
Human approval where it matters
Sending, sharing and unattended work pause for approval by default.
Evidence for every conclusion
Answers carry page-level citations, and Sofie is built to flag missing evidence rather than fill the gap.
Traceable history
Security events, access reviews and change history your administrators can review.
Memory you can inspect
Memory stays within your organization, and every person can see, correct or delete what Sofie keeps.
SOC 2 program underway
Controls mapped and monitored continuously ahead of our SOC 2 audit.
Isolated deployment
One customer, one environment.
Sofie is deployed privately for each customer. Your application, automation and database live in your own network on AWS, never alongside another customer’s.
Dedicated VPC
A separate virtual network per customer, with VPC flow logs.
Private subnets
Application and database tiers run in private subnets within that network.
Encrypted Aurora
Your data is stored in an encrypted Aurora PostgreSQL database of your own.
AI services
Knowledge bases and embeddings run on AWS Bedrock. Answers come from the model providers you enable, such as Anthropic, OpenAI and Google, under terms that exclude training on your data.
Your people
- SSO sign-in
- Passkey MFA and step-up
Your dedicated AWS environment
Single tenantDedicated VPC · flow logs enabled
Private application subnets
Private database subnets
AI services
- AWS Bedrock knowledge bases
- Model providers you enable
Another customer’s environment: its own VPC, subnets and database
Separate per customer
Identity & access
The right people, and only them.
Sign-in, session and permission controls your IT team already expects, applied to every workspace, document and Surface.
Single sign-on
SAML single sign-on with any standard identity provider, including Okta, Microsoft Entra ID, Google Workspace, OneLogin, JumpCloud and Auth0, plus direct Okta and Microsoft Entra ID sign-in. Email magic links where SSO is not in place.
Passkey MFA with step-up
Passkeys as a second factor, with a fresh check before sensitive actions.
Idle timeout you set
Sessions end after a period of inactivity you choose, from 15 minutes to 24 hours (1,440 minutes).
Roles built from fine-grained permissions
Workspace owner, admin, editor and viewer roles built from 19 permissions, and organization-wide workspace roles for broader programs.
Guest access by invitation
External partners see only what their invitation allows, with view or participate access scoped to specific records. Invitations last 14 days by default, up to a year.
Protected connections
OAuth tokens for connected systems are encrypted, internal services authenticate with per-service keys, and callbacks are signed.
AI governance
Sofie drafts. People decide.
Anything consequential waits for a person. Everything Sofie concludes carries its evidence.
Sequence · Weekly supplier digest
Waiting for approvalSofie wants to
Send an email to 4 recipients
To supplier-quality@larkspurbio.com +3
Subject Approved suppliers: one new Form 483 posted
3 sources cited · draft attached
- 01
Human approval by default
Sending email, writing to calendars, updating Salesforce and posting to team messaging pause for a person to approve, including in unattended Sequences.
- 02
Pre-approvals you control
Teams can pre-approve routine actions. Pre-approvals are optional, expire after 7 or 30 days by default, and can be revoked at any time.
- 03
Citations on every conclusion
Answers and drafts carry page-level citations. When the evidence is missing, Sofie names the gap instead of filling it from memory.
- 04
Memory you can inspect
Memory stays within your organization, each person can see, correct or delete what Sofie keeps, and every change to it is recorded.
- 05
Server-checked actions
Actions on Surfaces run through server-enforced eligibility rules, duplicate prevention and approvals, not just the interface.
- 06
Your data never trains a model
Customer content is used to do your work and nothing else.
Traceability
A clear history of who did what.
Sofie is an operational tool that supports your teams' workflows alongside your quality systems; it is not a system of record. It keeps a traceable history of security events, access and changes for your administrators to review.
Security event log
Security-relevant events are recorded in a log your administrators can review.
Access reviews
Access review snapshots list privileged users, workspace admins, permission overrides and pending invitations, so access stays matched to the people who need it.
Record and version history
Surface records keep their history, tracked changes and comments in documents carry their author, and saved versions can be restored.
Compliance status
Where we are, stated plainly.
We would rather tell you exactly where our program stands than overstate it.
SOC 2 readiness program
In progressOur SOC 2 program is underway. Controls are mapped and monitored continuously in Vanta ahead of our SOC 2 audit. We are not SOC 2 certified today, and we will walk your security team through current status during evaluation.
Designed for GxP work
In placeDocuments keep their Word fidelity and tracked authorship, records keep their history, and consequential steps wait for human review. How Sofie is qualified for your intended use remains a decision for your quality system, and we support that assessment.
Evidence, not advice
In placeSofie summarizes and cites evidence from official sources and your own documents. It does not provide legal or regulatory advice; decisions stay with your qualified experts.
Questions
Frequently asked
Is our data shared with other customers?
No. Each customer's application and database run in its own AWS environment, with a dedicated VPC, private application and database subnets and an encrypted database. Document conversion and regulatory search run on shared TransferAI services that keep each customer's data separate.
Is our data used to train AI models?
No. Customer content is used to do your work and nothing else. No model is trained on it.
Are you SOC 2 certified?
Not yet. Our SOC 2 readiness program is underway, with controls mapped and monitored continuously in Vanta ahead of the audit. We will share progress with your security team during evaluation.
Can Sofie send email or change records on its own?
Not by default. Sending, sharing, calendar writes and updates to connected systems pause for human approval, including in scheduled work. Pre-approvals are optional, expire by default and can be revoked.
Which identity providers do you support?
SAML single sign-on with any standard identity provider, including Okta, Microsoft Entra ID, Google Workspace, OneLogin, JumpCloud and Auth0, plus direct Okta and Microsoft Entra ID sign-in. Passkey MFA and step-up verification protect sensitive actions.
How do external partners get access?
By invitation only. Guests see only the Surfaces and records their invitation covers, with view or participate access you choose, and invitations expire.
Does Sofie give regulatory advice?
No. Sofie summarizes and cites evidence from official sources and your documents. Decisions stay with your qualified experts.
Bring your security team
to the first session.
We will walk your security, IT and quality reviewers through the deployment architecture, identity controls, approval model and our SOC 2 program status, and work through your security questionnaire with you.