Roadmap

Request A first-party command-line tool for Atlas: authenticate, inspect and manage applications, instances, users, roles and OAuth providers from the terminal, and script common admin tasks in CI. Context Everything is available through the API today, but there is no official CLI, so teams write th

Request Please ship a generally-available Terraform provider so Atlas configuration — applications, instances, OAuth providers, roles and SCIM connections — can be managed as code and reviewed in pull requests. Context A Go-based terraform-provider-atlas exists in the repo. GA would mean a published

Problem Usage analytics today are strongest at the application/instance level. Org administrators lack an aggregate view across all their applications — sign-ins, active users, provider mix and MFA adoption in one place. What we're planning An org-wide dashboard aggregating authentication volume, ac

Problem Standing up a self-hosted Atlas today means assembling the API, worker, web and marketing services, Postgres and routing by hand. That is too much friction for teams who want to run it themselves. What we're planning A one-command installer (Docker Compose / Helm) that provisions the full st

Problem Atlas already supports SCIM 2.0 provisioning with the Enterprise User extension (manager, department, work email), retry with backoff and dead-lettering. The remaining gap is deeper, more faithful group synchronization. What we're planning Richer group membership sync, including nested group

Problem Audit events (now enriched with user-agent and platform actor type) live inside Atlas. Security teams need those events in their own SIEM for retention, correlation and alerting — they can't today. What we're planning Bulk export of audit logs over a stable, filterable API. Streaming to comm

Problem Atlas currently runs on a single box: one host, one Postgres, no failover. That is fine for the current stage but is a single point of failure and adds latency for users far from the region. What we're planning Postgres replication with automated failover to remove the single database as a p

Problem Passwordless is now table stakes, but passkey behavior needs to be tunable per deployment — ceremony options, cross-device flows, and the fallbacks around them. What we're doing Per-method passkey settings, including WebAuthn ceremony knobs and the cross-device QR flow (phase two has shipped

Problem Social and enterprise login is only as useful as its provider coverage, and half-populated scope menus force integrators to hand-type scope strings and guess which are valid. What we're doing Doc-verified scope catalogs across 100+ providers — Google, Microsoft Graph, GitHub, Meta, Discord,

Problem The 11-language SDK matrix is code-complete, but the packages are not yet installable: the JavaScript packages are still marked private at version 0.0.0, and the non-JS bindings have never been pushed. So the goal of “add Atlas with one install command” is only half done — coverage is finish

Problem Usage was rendered with a hand-rolled SVG chart and no headline numbers, so it was hard to read a trend or reconcile against a bill at a glance. What shipped Metering KPI tiles sit above the charts, surfacing the headline numbers first. The hand-rolled SVG chart was replaced with Recharts fo

Problem Teams existed in the data model but membership didn't translate into real, scoped access to an application's instances. Instance-scoped dashboard routes each resolved access ad hoc. What shipped A Team dashboard section with an invite/accept flow. App-team members now receive real instance a

Problem The dashboard shipped a heavy JavaScript entry bundle. An earlier attempt to enable tree-shaking was blocked by the app structure, so dead code rode along on every load. What shipped Rollup tree-shaking was re-enabled after the code was restructured to make it safe (App.tsx and the auth-conf

Problem Subscription lifecycle events happened silently. A failed charge or an upcoming renewal could pass unnoticed until access was already disrupted, and the account-level notification toggles were cosmetic. What shipped Platform billing notifications wired to real Stripe events, with the account

What shipped Atlas now provides first-class SDKs across three tiers so you can integrate from whatever stack you already run: Backend / server (secret key, local JWT verification, 45 resource namespaces): Go, Ruby, PHP, Java, .NET — alongside the existing TypeScript and Python backend SDKs. Frontend