DOCUMENTATION

Public documentation.

What developers need to integrate with Atom9, and what security and compliance reviewers need to evaluate it. Product help for day-to-day work lives inside the workspace.

For developers

Add "Continue with Atom9" to your app	The quickstart: add a sign-in app, point any OIDC library at `id.atom9.com`, key your users on the stable `sub` claim.
Examples by stack	Working configurations for Node, Next.js, Python, Spring Boot, ASP.NET Core, and Rust — no vendor SDK required, by design.
Rules & responsibilities	The do/don't checklist, and the plain statement of what Atom9 is responsible for versus what your app owns.

Trust, security, and compliance

Security	How accounts, sessions, and the platform's security controls work, and how to report suspicious behaviour.
Compliance	The compliance model: safety checks, evidence, audit trails, and data handling commitments.
DORA alignment	For financial-sector customers: ICT risk, incident handling, resilience testing, provider risk, and continuity controls.
GDPR	Data protection roles, personal-data handling, and how export and removal requests work.

Reference

Glossary	Plain-language explanations of terms like OIDC, processor, audit trail, data residency, and approval gate.
Terms	The binding agreement for using Atom9.
Privacy Policy	What we collect, why, and your rights.

Looking for help using the product — projects, boards, content, automations, team access? That documentation lives inside your workspace at admin.atom9.com, alongside the things it explains.