Sign-in for apps and games, without the friction

algizian is a multi-tenant OAuth 2.1 and OpenID Connect server where people sign in with Google, Microsoft or Apple. Create a tenant, add a client and your app has a working sign-in, with your branding, on your own domain.

Why teams use it

Built for startups, game publishers and app developers who want people signed in on the first try and do not want to run an identity system.

Social sign-in only

Your users sign in with Google, Microsoft or Apple. There are no passwords to store, no reset emails and no forms to build.

A sign-in domain at once

Every tenant gets its own address, acme-games.algizian.com, the moment it is created. Later, add your own domain with a single CNAME.

Your brand on every screen

Set the name, logo, colours and wording of the sign-in and consent screens per tenant, with one API call.

Standard OAuth and OpenID Connect

Discovery, the authorization code flow with PKCE, refresh token rotation and a public key set. Any OIDC library works.

Made for agents too

A token-gated management API and an MCP server let an agent set things up. Dynamic client registration lets Claude and ChatGPT connectors sign in.

Users stay yours

Users belong to one tenant, and every tenant sees a different subject for the same person. Open sign-up, with the option to block any user.

How it works

  1. Create a tenantOne API call gives you a sign-in address and a signing key. Pick a name of four characters or more.
  2. Add a clientRegister your app with its redirect addresses. A browser or mobile app uses PKCE and needs no secret.
  3. Send people to sign inRedirect to the authorize endpoint. They choose Google, Microsoft or Apple on a screen that carries your branding.
  4. Verify the tokenExchange the code for tokens and check them against the tenant key set, with any JWT library.

One request to start

The whole setup is plain HTTPS and JSON. This creates a tenant; the quick start takes it to a signed-in user.

curl -X POST https://id.algizian.com/api/v1/tenants \
  -H "Authorization: Bearer $ALGIZIAN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "slug": "acme-games", "name": "Acme Games" }'

# The answer carries the issuer: https://acme-games.algizian.com
# Its discovery document: https://acme-games.algizian.com/.well-known/openid-configuration

Where to go next

Quick start

From nothing to a validated token in a few commands.

Start here

Concepts

Tenants, issuers, clients and users, and how they fit together.

Read concepts

Management API

Everything you can set up over REST, with the OpenAPI document.

See the API

MCP and AI agents

Manage tenants from an agent, and sign in connectors.

Read about MCP