Skip to content

IDENTITY PROVIDER — BUILT BY COMBINE

One identity.
Every door.

Your applications belong together. Give people one account to move between them, and give your team one place to manage access.

OIDC + OAUTH 2.1 MULTI-SPACE SSO CUSTOM DOMAINS
SIGNED IN
MASTER

acme.example.com

SPACE ACTIVE
Workspace
CONSOLE
Portal
SSO
Docs
SSO
Billing
SSO

ONE SESSION // 4 CONNECTED APPS

ONE SPACE // ONE SESSION // EVERY CONNECTED APP

01

Sign in once. Keep moving.

Single sign-on across your applications.

02

A space of your own.

Your users, your providers, your rules.

03

Standards at the core.

OpenID Connect and OAuth 2.1.

01 / HOW IT WORKS

One less barrier. A lot more possibility.

Authentication should get people where they're going. Citadel brings your applications into a shared space, so the next sign-in is one they can skip.

  1. 01

    A PLACE TO BELONG

    Start with your space.

    Give an organisation or application group its own identity home, on its own subdomain or a verified domain you bring.

  2. 02

    A FAMILIAR ENTRANCE

    Connect the ways in.

    Choose your sign-in methods, connect your identity providers, and register applications using OpenID Connect.

  3. 03

    ROOM TO MOVE

    Let one account do more.

    People sign in once and move between connected applications. Their profile, security settings and active sessions have one home.

02 / THE PLATFORM

Everything identity. All in its place.

A considered foundation for the people who use your apps and the teams who build them.

Separate spaces. Shared simplicity.

Each space keeps its own users, sessions, providers and applications. Clear boundaries for your organisations, with a consistent way to manage them.

A

Acme

acme.example.com

S

Studio

studio.example.com

A familiar way in.

Passwords, magic links, email codes or a provider people already know. Choose what fits each application.

  • Google
  • Steam
  • Email
  • OpenID

Your brand at the door.

A login that feels like your product. Choose a design, make it yours, and preview it before it goes live.

Sign in

name@company.com
Continue

DISTINCTLY YOURS

Confidence, built in.

Add a second factor with authenticator and recovery codes. Keep provider credentials encrypted at rest.

7FK2-9QXAM3V8-TR4DKX61-09PLD2NA-77QF9WHE-BB12QZP4-55RM

MORE THAN A PASSWORD

A clear control centre.

Manage users, applications, domains and connections in one console. People get their own account area.

128

USERS

3

APPLICATIONS

2

DOMAINS

THE RIGHT TOOLS FOR EACH ROLE

03 / FOR DEVELOPERS

Your stack. A common language.

Use the OpenID Connect client you already know. Citadel handles identity; your application gets back to doing what makes it useful.

  • Authorization code flow with PKCE
  • Discovery, JWKS and userinfo endpoints
  • Refresh tokens, revocation and logout
Let's talk integration

auth.example.com — OPENID CONNECT

// Your space. Your issuer.

issuer = "https://auth.example.com"

GET/.well-known/openid-configuration
GET/oauth/authorize
POST/oauth/token
GET/oauth/userinfo

EXAMPLE ENDPOINTS // CUSTOM DOMAIN

04 / A LITTLE CLARITY

Good questions. Straight answers.

Have something else in mind?

Talk to the team

Can I use my own domain?

Yes. Every space runs on its own subdomain, or on a custom domain you verify. Issuer URLs, cookies and branding all follow your domain.

Which sign-in methods can I offer?

Passwords, magic links and email codes out of the box, plus external providers such as Google and Steam. You choose per space.

Does it work with my existing OIDC client?

Yes. Citadel speaks standard OpenID Connect and OAuth 2.1, with discovery, JWKS and userinfo endpoints. Any conforming client library works.

How is data isolated between spaces?

Each space keeps its own users, sessions, providers and applications. Nothing crosses a boundary you did not draw.

05 / GET STARTED

Bring your apps together.

Let's give your people a simpler way in. Tell us about your applications. We'll take it from there.

Get started