Contact us

Send us a message and we will reply to the address you leave here.

Talk to a human at Atlas. Whether you're evaluating Atlas, running it in production, or reporting a security issue, this page points you at the right inbox — and tells you when to expect an answer.

Atlas is the identity layer for modern applications: 56 social and enterprise logins, passkeys and MFA, multi-tenant organizations with roles and permissions, and first-class sessions — self-hostable from day one. Before you write in, two shortcuts that are usually faster than an email: the documentation at docs.atlasauth.net answers most integration questions, and status.atlasauth.net tells you in seconds whether something is already a known incident.

We answer during UK/EU working hours, Monday to Friday, 09:00–18:00 UTC. Here's what to expect once your message lands:

  • Support & general — first reply within one working day; most tickets are resolved the same day.

  • Sales & enterprise — a named contact within one working day, often the same day for evaluations on a deadline.

  • Security disclosures — acknowledged within 24 hours, with a triage assessment inside 72 hours (see below).

  • Billing — within one working day.

If you're mid-incident and Atlas itself is down, don't wait on email — check status.atlasauth.net, where we post updates as we work the incident.

A little context up front saves a round-trip and gets you an answer faster. Where it applies, tell us:

  • The email on your Atlas account (or your organization / tenant ID).

  • Whether you're on a test (pk_test_…) or live (pk_live_…) key, and roughly when the problem started.

  • What you expected to happen, and what happened instead — the exact error message or code beats a paraphrase.

  • The SDK and version you're using (for example @atlas/react) and the environment (browser, server, self-hosted or managed).

  • A request ID or timestamp if you have one — it lets us find the exact log line.

Please never send us passwords, full session tokens, or secret keys (sk_live_…). We never need them to help, and a redacted snippet is always enough.

Email isn't the only way to reach us, and often isn't the fastest:

  • Documentation — guides, API reference and SDK quickstarts at docs.atlasauth.net.

  • Community — ask a question or search past answers at community.atlasauth.net; other builders and the Atlas team are both there.

  • Status & incidents — live uptime, maintenance windows and incident history at status.atlasauth.net. Subscribe there to be notified before we email.

Prefer to write? The addresses below go straight to the right team.

Support options

Running into a bug, an integration question, or something the docs didn't cover? Email support@atlasauth.net or pick Support in the form above.

Before you write, it's worth a quick look at docs.atlasauth.net — the OAuth, passkey, MFA and organizations guides cover the questions we see most. For anything that looks like an outage (logins failing across the board, elevated errors), check status.atlasauth.net first; if it's not already posted there, tell us and include a request ID or timestamp so we can trace it.

General questions that don't fit a category? Choose General in the form and we'll route it for you.

Enterprise & sales

Evaluating Atlas for your company, comparing plans, or need SAML, enforced SSO, SCIM provisioning, audit logging, a custom data-residency or self-hosting arrangement, or an MSA and security review? Talk to us at sales@atlasauth.net or choose Sales in the form.

Enterprise features aren't a paywalled afterthought at Atlas — organizations, roles and permissions ship with the product. Sales is where we help you plan a rollout, run a proof of concept against a deadline, size volume pricing, and complete procurement and vendor-security paperwork. Tell us your identity providers, rough user and organization counts, and your target go-live date, and we'll come prepared.

Security & responsible disclosure

Found a vulnerability? We want to hear from you. Email security@atlasauth.net directly — please don't open a public community thread or file it as an ordinary support ticket.

We acknowledge every report within 24 hours and aim to give you a triage assessment within 72 hours, then keep you updated through to a fix. We support coordinated disclosure and are happy to credit you once a fix has shipped. To help us move quickly, include clear reproduction steps, the affected endpoint, SDK or component, and the impact you observed.

Please test only against your own accounts and data. Don't run automated scans against production, don't access or modify other users' data, and avoid anything that could degrade the service for others — good-faith research within those bounds is always welcome. If a report involves personal data or a privacy concern, you can also reach our privacy team at privacy@atlasauth.net.

Email
support@atlasauth.net
Hours
Mon–Fri, 09:00–18:00 UTC
Usually answers within
one working day
Something urgent
Open