Authentication inside your app.
Stargate embeds email/password and OIDC sign-in, sessions, API keys and an account panel in your existing HTTP server. The authentication runtime is written in Rust and shared across language integrations.
Choose your integration
Install the package for your host language:
Node / Express
npm install @syntropika/stargate expressPython / FastAPI
python -m pip install syntropika-stargate fastapiRust / Axum
cargo add syntropika-stargate --rename stargateGo integration is available from the repository and links to the Rust C ABI. See the Go integration guide.
Mount the runtime
Provide the public HTTPS origin, embedded Turso database and your selected sign-in methods. For OIDC, register https://app.example.com/auth/callback with the provider, mount Stargate, then protect the routes that require an identity or scopes.
The account panel is served under /auth/. Your application supplies the HTTP server, TLS and configuration; Stargate does not discover configuration files or environment variables.
For email/password sign-in without an identity provider, follow the local accounts guide.
Understand the current scope
Stargate targets one process and one embedded database. Choose local accounts, OIDC, or both. With local accounts enabled, the first completed signup becomes the administrator and can manage users. Email verification, invitations, password recovery, MFA and distributed sessions remain future work.
Read configuration and security before shipping an integration. All cookies use Secure, and browser account mutations require session authentication and CSRF protection.