Docs / Start

Stable

Atmosphere Account docs

Build with a shared Atmosphere sign-in picker, host registry, and thin routing to PDS-owned account pages.

Use Atmosphere Login when an app wants a consistent account picker before starting its own AT Protocol OAuth flow.Use host service records when a PDS host wants Atmosphere to route users to its account page without giving custody or account-control authority to Atmosphere.Passwords, devices, OAuth grants, keys, backups, recovery, deletion, and migration are managed by the user's PDS host, not by Atmosphere.Use conformance tools before claiming compatibility in the host directory.

Architecture

Thin coordination, host-owned account controls

Atmosphere Account coordinates UX, discovery, and contracts. The user’s account host remains the authority for account security, account controls, and data custody.

01

Universal sign-in

Apps send users to the hosted picker. Atmosphere returns a signed selection token, then the app starts normal AT Protocol OAuth with the chosen account.

02

Shared app records

Apps use interoperable listing records for discovery, reviews, favorites, and community app identity. The old Atmosphere profile record is legacy compatibility.

03

Host account routing

PDS hosts publish a service record. Atmosphere shows where the account lives and links users to the account page the host explicitly publishes.

04

Developer ecosystem

Docs, examples, validator APIs, CLI checks, and future conformance badges help apps and hosts interoperate without a central token broker.

Security boundary

Atmosphere does not broker app OAuth tokens, revoke PDS grants, manage devices, change passwords, rotate keys, perform account recovery, store backups, delete accounts, or move accounts. Those actions belong to the user’s account host.

SurfaceAtmosphere doesPDS host does
Sign inLets the user choose an account and returns a signed selection token.Issues the app's OAuth grant after the app starts normal AT Protocol OAuth.
Account homeShows the current account, remembered browser accounts, Atmosphere Login connections, developer apps, reviews, and a link to the host.Manages passwords, devices, OAuth grants, account deletion, recovery, backups, exports, and migration.
Host directoryShows reachable, intentionally public provider profiles with signup information, location/style, and optional compatibility signals. Raw observed personal PDSes remain private.Publishes authoritative host service/profile records and owns the account page destination.
App directoryIndexes shared app records, merges duplicates, and shows reviews/favorites from interoperable records.Publishes app-owned records from the app account and remains the source of truth for app-specific OAuth grants.

Choose the right integration

You are buildingUseResult
An Atmosphere appAtmosphere Login and shared app recordsOne consistent account picker, followed by your own AT Protocol OAuth session and interoperable app discovery.
A PDS hostHost service recordAtmosphere can route people to the explicitly published account page without duplicating account controls.
A directory or compatibility badgeConformance validatorClaims are backed by testable manifest behavior instead of manual copy.
On this page

Next steps

Keep building