Developer documentation for unified Flutter and Dart authentication
Use the docs hub to install the SDK, compare provider integrations, copy implementation-ready code, and move from onboarding to production rollout without switching documentation patterns.
One SDK surface for Firebase, Entra ID, Cognito, Auth0, Okta, Magic, and more.
This portal is built like infrastructure documentation, not a marketing site. Installation, provider setup, API usage, and troubleshooting all stay one click away with consistent headings and copyable examples.
Quick start path
The homepage acts as a navigation hub. Start with the four common tasks below, then jump directly into the code blocks that move a project from zero configuration to an active login flow.
Understand the recommended sequence before wiring providers.
Add the core package and provider adapters.
Register client identity, redirect URIs, and provider registry values.
Use the minimal login example and verify session state.
Provider integrations
Every provider guide follows the same sequence: overview, prerequisites, installation, configuration, authentication flow, example implementation, error handling, advanced options, best practices, and troubleshooting.
Firebase
AuthIntegrate Firebase Authentication through the shared Aortem auth contract.
Microsoft Entra ID
AuthConnect Azure tenant policies and OpenID scopes with the same SDK surface.
AWS Cognito
AuthBridge Cognito user pools and hosted UI flows into a single SDK contract.
Auth0
AuthDeploy Auth0 login, MFA, and custom domains through consistent SDK primitives.
Okta
AuthMap Okta org configuration, policies, and logout handling to Aortem auth APIs.
Magic
AuthSupport passwordless email and wallet logins using Aortem session management.
Stytch
AuthUse Stytch factors, OTP, and passkey flows through the same auth abstractions.
Ping Identity
AuthBring Ping authorization servers and enterprise login policies into a single SDK flow.
Transmit
AuthConnect Transmit CIAM login journeys and custom challenges to unified auth methods.
Fingerprint
AuthUse device signals and risk scoring alongside Aortem session and policy controls.
Common developer workflows
The docs hub is organized around the tasks engineering teams actually perform during implementation and rollout, not around feature marketing categories.
Add authentication to a Flutter app
Install the SDK, initialize once, and keep provider logic out of view code.
Configure redirect-based login
Set callback URIs correctly across mobile, web, and desktop targets.
Enable multiple providers
Register adapters without branching the core auth flow per provider.
Manage sessions and refresh
Inspect normalized session state and refresh before expiry.
Handle authentication errors
Treat provider mismatches and token issues as operational failures first.
SDK resources
Source code, packages, examples, and contribution guidance should remain directly accessible from the docs hub so implementation and maintenance stay close together.