Centralized auth for every SaaS you ship.
ZeroDriveX Auth gives you tenant-aware users, short-lived tokens, Redis-backed revocation, and immutable audit logging – in one service you can drop behind any domain.
{
"tenant": "acme-saas",
"clientId": "zdx_client_123",
"issuer": "https://auth.zerodrivex.com",
"audience": "zdx-auth-clients",
"redirectUri": "https://acme.app/auth/callback"
}- • Redis-backed JTI blacklist
- • Per-IP rate limiting with KarmaStrike
- • Immutable runtime logs to ZDX
What ZeroDriveX Auth gives you
A focused auth plane that doesn't try to be your app – just your identity spine.
Tenant-aware identity
Users, tenants, and memberships are first-class. One identity, many applications – with explicit roles per tenant.
DB-backed tokens
Access and refresh tokens are tracked in Postgres. Redis caches the hot path; revocation checks degrade gracefully if cache is unavailable.
Centralized revocation
JTI-based revocation, device/session cuts, and “log out everywhere” – without relying on best-effort client behavior.
Immutable logging
Auth decisions and rate-limit strikes can be mirrored into an append-only log database for long-term forensic safety.
Multi-domain SaaS
Keep ZDX cookies scoped to .zerodrivex.com while issuing standards-based tokens your customers can validate on their own domains.
Simple integration
Onboarding APIs generate per-tenant client configs and code skeletons; you plug them into your stack and keep control.
How it fits into your stack
- 1
Onboard a tenant
Create a tenant, register domains and redirect URIs, and let the system mint a client ID and secret.
- 2
Drop in the callback handler
Use the generated code for your stack to handle the callback, exchange codes for tokens, and set your own cookies.
- 3
Rely on ZDX for the hard parts
Delegate auth, revocation, and logging to ZeroDriveX Auth, so your app code stays focused on actual product behavior.
Pricing for builders, not tourists
Start in sandbox with capped tenants and users. When you're ready to expose it to real traffic, flip a switch – not your stack.
- Up to 3 tenants
- Up to 250 users total
- Full token + revocation pipeline
- Audit logging enabled