SDKs
- Written for
- ＋ Written for
- Deprecated
- ＋ Deprecated
- Applies to
- ＋ Applies to
SDKs
Atlas ships official SDKs across three tiers. Pick the frontend SDK for your framework, the backend SDK for your server language, and (for native apps) a mobile SDK.
Tier | What it does | Credential |
|---|---|---|
Mount the provider, render sign-in/account UI, read the user, call | Publishable key | |
Manage the instance over the BAPI; verify session JWTs locally | Secret key | |
Native sign-in and session storage over FAPI | Publishable key |
Frontend (8)
@atlas/js (framework-agnostic core) · @atlas/react · @atlas/nextjs · @atlas/vue · @atlas/nuxt · @atlas/angular · @atlas/svelte · @atlas/react-native
Backend (7)
Node (@atlas/backend) · Python (atlas-backend) · Go (atlas-go) · Ruby (atlas-auth) · PHP (atlas-auth/atlas-php) · Java (net.atlasauth:atlas-java) · .NET (Atlas.Sdk)
Mobile (3)
Swift (iOS/macOS) · Kotlin/Android (net.atlasauth:atlas-android) · Flutter/Dart (atlas_auth)
The shared contract
Every SDK targets the same API and the same authorization primitive: a condition like { permission: 'org:billing:manage' } evaluates identically on the frontend (has()), on the backend (authenticateRequest().has()), and on mobile. A check written for one surface behaves the same everywhere. The wire is snake_case JSON and the SDKs type it directly rather than inventing a second dialect.
Generate a client for any other language from the API surface documented in the Backend endpoint index.