Trust Center
Security overview, subprocessors, compliance status, policies, audits, status, disclosure, and downloads.
Security & trust
Trust the protection boundary, and verify the evidence.
Public security, architecture, compliance-claim, legal, status, and disclosure materials live in the AtlaSent Trust Center and public documentation.
Architecture & docs
Understand the authority lifecycle, APIs, integrations, evidence model, and implementation boundaries.
Responsible disclosure
Security researchers can report concerns privately, without needing Console access. Please do not open a public issue.
AtlaSent does not turn framework alignment into a certification claim. Current public compliance claims are controlled by the canonical claims matrix in the documentation.
Where we are today
What is true now, and what you can check yourself.
No SOC 2 report yet
No SOC 2 report of any type has been issued, and no audit period has started. We will not claim one until it exists. Current status is in the Trust Center.
Check the evidence without trusting us
AtlaSent evidence packages are signed and hash-linked. You can verify one offline with the source-open atlasent-verify tool, against the public keys published at keys.atlasent.io. The tool reads keys from a PEM file with one kid per key; converting the published key set to that file, and leaving out revoked keys, is a manual step today.
A founder-led company
One person is accountable for production changes at AtlaSent today. Production deploys of our console backend and runtime require an AtlaSent permit and leave the same kind of evidence we provide to customers. The console frontend is not yet behind that gate.