Cloud Platform / Product 01

Cyberia Auth Management

Multi-tenant identity, branded end to end, deployed in an afternoon. A complete multi-tenant authentication control plane — organizations, applications, domains, SSO, branded email and a drop-in React component with an npm package.

Release
10+
SSO Providers
7
Email Presets
< 1 day
Time to Integrate
100%
Multi-Tenant Isolation

Generally Available · v2.2.6

// Overview

An identity control plane, not a login form.

Cyberia Auth Management is the first product on the CYBERIA Cloud Platform. It gives engineering teams an Auth Admin control plane where every tenant is a first-class organization with its own branding, applications, tokens, trusted domains, SSO providers and transactional email templates — then hands developers a React component and npm package so shipping login into an application takes an afternoon, not a quarter.

  • Multi-tenant organizations with per-tenant branding
  • Per-application tokens, senders and policies
  • Domain and origin trust enforcement
  • Automatic or admin-approved user registration
  • Third-party SSO: Google, Microsoft, Apple, Facebook, X, GitHub, GitLab, Discord, Slack, Twitch
  • Branded transactional email templates with variable presets
  • Drop-in React component distributed on npm
  • Full auth event audit trail
Auth Manager dashboard
Auth Manager dashboard
The Auth Admin dashboard — applications, app users, active organization and weekly identity activity.
Capabilities

Eight surfaces.
One auth server.

Each capability has its own page with the console screenshots, the configuration model and the security reasoning behind it.

// Inside the console

A guided tour

Organizations
Organizations
Tenants as first-class objects — each with logo, slug and brand colors.
SSO connections
SSO connections
SSO providers enabled per application, credentials held server side.
Domains and origins
Domains and origins
Allowed origins per app and DNS-verified organization domains.
Branded email preview
Branded email preview
Transactional email rendered with the tenant's branding before it ships.
// Developer experience

Install the package. Mount the component. Done.

The React component reads the application's enabled providers and the organization's branding at runtime, so the login screen your users see always matches what the admin configured — with no redeploy.

npm install @cyberia-auth/auth

import { CyberiaAuth } from "@cyberia-auth/auth";

<CyberiaAuth
  serverUrl="https://auth.your-domain.com"
  appToken={import.meta.env.VITE_CYBERIA_APP_TOKEN}
  onSignedIn={(session) => navigate("/dashboard")}
/>;
Drop-in sign-in component
Drop-in sign-in component
The shipped component: tenant logo, brand color, enabled SSO providers and email/password in one screen.
// Case studies

Where teams put it to work.

Case 01 / B2B SaaS vendor

Multi-tenant login with per-customer branding in one sprint

Cloud PlatformSaaSFintech
Challenge
Every enterprise customer wanted their own logo, domain and SSO provider. The in-house login service needed a code change and a release for each of them.
Approach
Each customer became an organization in Auth Manager with its own branding, allowed domains and SSO connections. The product team dropped in the React component from the npm package and stopped touching auth code entirely.
1 sprint
to replace the legacy login
0
code changes per new tenant
Self-serve
customer SSO onboarding
Organizations with independent branding and identity settings.
Organizations with independent branding and identity settings.
Organizations with independent branding and identity settings.
The shipped React login component, themed per organization.
The shipped React login component, themed per organization.
The shipped React login component, themed per organization.
Case 02 / Systems integrator, public sector

Federated SSO and domain-locked authentication across programs

Cloud PlatformDefenseTelecom
Challenge
Programs federated with Google, Microsoft and Apple in inconsistent ways, and no one could state which origins were allowed to start an auth flow.
Approach
SSO providers are registered centrally, domains and origins are allowlisted per application, and registration is either automatic or admin-approved depending on the program's clearance rules.
5
identity providers unified
100%
origins explicitly allowlisted
-80%
identity review effort per launch
Third-party SSO connections managed per organization.
Third-party SSO connections managed per organization.
Third-party SSO connections managed per organization.
Domain and origin allowlists enforce where login may happen.
Domain and origin allowlists enforce where login may happen.
Domain and origin allowlists enforce where login may happen.

Ready to deploy Cyberia Auth Management?

Initialize Engagement