login.broker
FACT SHEET · AUGUST 2026

Login Broker, at a glance

A concise, implementation-checked reference for customers, partners and writers.

What it is

Login Broker is a hosted social-login broker. It handles provider OAuth and OpenID Connect differences and gives a customer’s trusted backend a completed login result containing an email address.

It is deliberately not a full identity platform: customer applications retain their own user records, sessions, roles and permissions.

Product facts

Providers
Google, GitHub, Apple, Facebook, LinkedIn and Microsoft
Integration modes
Redirect and popup
Primary result
Email address from a completed provider login
Session lifetime
10 minutes
Client library
Version 4.1.0 in the current codebase
Tenant names
Lowercase a–z and 0–9

How the flow works

  1. The application starts a provider login with a tenant, provider and unique session ID.
  2. Login Broker records a pending attempt and redirects to the provider.
  3. The provider callback completes or fails the broker session.
  4. The application can poll a public endpoint that returns only the status.
  5. The customer backend retrieves the tenant-scoped result with its secret API key.
  6. The customer creates its own user and application session.

Security boundaries

  • The result endpoint requires X-LoginBroker-ApiKey.
  • Result lookup is scoped to the requesting tenant.
  • The public status endpoint returns only pending, completed or failed.
  • Provider and broker secrets remain in server-side configuration.
  • Tenant API keys can be rotated; the previous key then stops working.
  • Expired sessions return an explicit gone/expired error.

Pricing

Express
€0 per month for up to 100,000 monthly active users
Trial
None; the free plan has no timer or card requirement
Pro
€19 per month, including 100,000 monthly active users
Additional users
€0.005 each on Pro
MAU definition
A distinct email that completes at least one login in a calendar month

Commercial terms are taken from the website’s current pricing page and may change. The pricing page is authoritative.

Technical endpoints

Initiate
/{tenant}/auth/{provider}/session/{sessionId}
Status
/{tenant}/auth/status/{sessionId}
Result
/{tenant}/auth/result/{sessionId}

The initiation and status routes are public. The result route is for server-to-server verification and requires the tenant API key.

Data handled

A login session can contain its ID, tenant, provider, status, error, email, return URL and creation time. Tenant records include configuration, an API key and rolling success/failure activity. Account data supports users, tokens and tenant roles.

The customer’s full user profile, authorization model and long-lived application session are outside Login Broker’s product contract.