Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Applications

An application in Aero2 is an isolated authentication environment. Each application has its own user pool, authentication settings, identity providers, branding, and API keys. Users in one application are completely separate from users in another.

Isolation Model

Every application gets its own subdomain (e.g., swift-maple.aero2.dev), providing complete cookie and CORS isolation. Slugs are auto-generated as adjective-noun pairs when you create an application. This means:

  • Users in one application cannot see or access users in another application
  • Authentication sessions are scoped to the application's subdomain
  • API keys from one application do not work with another
  • Identity provider configurations are independent per application

Use Cases

  • One application per product — If you operate multiple products, each gets its own Aero2 application with separate user pools.
  • Staging and production — Create separate applications for your staging and production environments to keep test users out of production.
  • White-label products — Each customer deployment can have its own application with custom branding.

Creating Applications

Applications are created through the developer dashboard. On creation, Aero2 generates your API keys and sets up default roles and permissions.

Create your first application

Learn More