Identify
DE (Deutsch)Request a demo
Menu
Identity without lock-in

Know exactly how independent you are.

A European identity provider beside Microsoft Entra ID or Google Workspace. Use it as your fallback, or move your apps' sign-in to it, MFA intact.

Request a demoSee how it works
The Independence view in the Identify Console. Example tenant, illustrative figures.
Why it matters

Your sign-in hangs on one vendor.

Every app your people use depends on one identity provider. Moving away is usually a long consulting project.

An outage
Sign-in stops for everyone.
A price rise
You pay it, because leaving is hard.
A contract dispute
Your negotiating power is gone.
How it works

Your users move themselves, at their next sign-in.

Apps trust Identify. Entra or Google is asked only at a user's first sign-in.Your appsYour directoryApp · OIDCApp · SAMLApp · OIDCSigns your users inMicrosoft Entra IDGoogle WorkspaceOIDC / SAMLFirst sign-in only123Apps trust Identify. Entra or Google is asked only at a user's first sign-in.Your appsApp · OIDCApp · SAMLApp · OIDCOIDC / SAML1Signs your users in3Microsoft Entra IDGoogle WorkspaceFirst sign-in only2Your directory
Apps trust Identify. Entra or Google is asked only at a user's first sign-in.

  1. Connect your apps

    Your apps connect over standard OIDC or SAML. We copy their app registrations from Entra, roles included.

  2. Users sign in once, as usual

    They sign in at Entra or Google, with the MFA they already have. We never see their Entra or Google password.

  3. Then Identify signs them in

    They set a new password and a second factor, or a passkey. From then on, Identify signs them in.

The Independence view

Independence from your directories

The Identify Console opens on one number: how many of your users can already sign in without Entra or Google.

Example tenant northwind. Figures are illustrative.

Before you switch the fallback off, Identify shows how many people would be locked out. You confirm that number, or nothing changes.

Before Entra goes off, the Identify Console names who would be locked out. Example tenant, fictional data.
Two ways

Fallback or exit. You decide.

Keep your directory

Entra or Google stays your system of record. Identify stands beside it, so migrated users keep signing in when it's down.

Fallback: On

Move your apps' sign-in over

Run the same steps to the end, then switch the fallback off. Your apps then sign in through Identify alone.

Fallback: Off

Each tenant picks its own path. The safety check is the same for both.

Migration

Bring your apps along.

Identify reads your app registrations from Entra, with roles and users, and gives you the settings to paste back.

  • OIDC and SAML apps, with roles and assignments
  • Provisioning to your SaaS apps over SCIM, without deleting anyone
  • Self-service password reset and a personal account page
Users in the Identify Console, and the sign-in page. Example data.
For engineers

Your platform team will feel at home.

Everything in the Console is also an API call. Standard OIDC and SAML, OpenAPI, signed webhooks and a complete audit export.

Engineering details →

Sovereignty

Built to be operated in Europe.

For organisations that want identity under European law. The Identify service runs on STACKIT in Germany and is operated by a German company.

Your applications connect to Identify over standard OIDC and SAML, with no proprietary SDK.

See the facts →

Identify ends identity lock-in.

We'd love to show you. See it live on a demo tenant, and bring your questions.

Request a demo