Set up your auth project
Create a project, choose the sign-in providers, add your callback URLs, and set the app name, logo, and domain your users will recognize.
Elixpo Accounts · Identity for the Elixpo suite
Add sign-in, sign-out, account switching, secure sessions, and complete user management to your app. Choose your providers and branding, register the app, follow the docs, and ship without building an authentication platform first.
Get started
We host the difficult identity screens and security flows. You choose how your app should look, connect one callback, and keep building your product.
Create a project, choose the sign-in providers, add your callback URLs, and set the app name, logo, and domain your users will recognize.
Install the Developer SDK or use standard OAuth 2.0 and OpenID Connect. Add sign-in and sign-out, then let the hosted account screens handle the rest.
What you get
Authentication is more than a login form. Keep the user, session, security, and app lifecycle together from day one.
Offer email and password, Google, GitHub, Microsoft, and Discord from one sign-in screen. Users can also choose a passkey when they want passwordless access.
Sign-in, sign-out, account switching, consent, session refresh, and revocation work together instead of becoming separate features your team must maintain.
Give users one place for profiles, security methods, active sessions, devices, connected apps, notification choices, and account deletion.
Show your app name, logo, and verified domain during the hosted handoff. Underneath, standard OAuth 2.0 and OpenID Connect keep the integration portable and inspectable.
Developer SDK
Runs in Node.js and edge runtimes, and stays compatible with standard OAuth if you ever want to integrate without the package.
TypeScript · MIT
@elixpo/accounts creates login links, protects callbacks, refreshes access, and verifies user identity against JWKS.
$ npm install @elixpo/accounts
import { createAccountsClient } from "@elixpo/accounts"
// PKCE, state and nonce built in
const request = await accounts.createAuthorizationRequest()Standards first
OAuth authorization server metadata, OpenID configuration, and signing keys are public for any client to read.
Security defaults
The parts teams usually get wrong are on from the first request, for every app on the network.
Every authorization code is bound to a verifier, with state and nonce checks on the way back.
Refresh tokens rotate atomically per family, and reuse revokes the whole family.
ID and access tokens verify against published keys from standard discovery documents.
TOTP, WebAuthn passkeys, trusted devices, sign-in alerts, and session revocation per device.
Questions
Anything else is in the documentation.
Elixpo Accounts is a hosted identity provider. It gives your application sign-in, sign-out, single sign-on, account switching, MFA, and user management over standard OAuth 2.0 and OpenID Connect, and it is the account system behind every Elixpo product.
Email and password, Google, GitHub, Microsoft, and Discord, plus WebAuthn passkeys. Users can add TOTP or passkey second factors and manage trusted devices from their account.
No. The @elixpo/accounts package handles login links, PKCE, callbacks, refresh, and token verification for Node.js and edge runtimes, but any standards-compliant OAuth 2.0 / OIDC client works against the published discovery and JWKS endpoints.
The Hobby plan is free for up to 1,000 monthly active users per app. Paid plans raise the limit to 10,000 and 100,000 monthly active users per app and are billed in INR.
Yes. Users can keep multiple accounts signed in on one browser and choose which one to continue with on the consent screen, without signing out.
Ready when you are
Create your auth project, choose the providers and brand your users should see, then follow the quickstart. We handle the account system behind it.