Password verified
Redirect URI, origin, tenant, and role checks pass.
Authentication infrastructure
Authentication for customer apps, without the usual integration mess.
ZDX Auth gives teams a working path for app password login, callback code exchange, local sessions, server-side token verification, tenant boundaries, and Stripe-backed plan limits.
Password login + auth codeServer token verifyStripe-backed plans
Customer appSign in with ZDX Auth
Callback code issued
Your app exchanges the one-time code server-side.
Access verified
Token checks include issuer, audience, JTI, and limits.
Stripe syncedServer verifiedTenant aware
Platform
The auth surface your customer apps need
The product is organized around the actual integration path: tenant setup, client app provisioning, login, callback exchange, token verification, billing, and operational review.
Client app management
Create app credentials, manage exact redirect URIs, control allowed origins, and restrict access by role.
Password login for apps
External apps can use email and password login without depending on shared ZDX Auth cookies.
Token lifecycle control
Short-lived access tokens, opaque refresh tokens, one-time callback codes, JTI tracking, and revoke routes.
Stripe-backed plans
Checkout, portal, webhook sync, and server-side plan limits keep billing tied to actual access.
Guided onboarding
The server-side Ollama assistant helps users wire login, callbacks, local sessions, token verify, refresh, and revoke.
Operational visibility
Dashboards surface tenants, users, client apps, API keys, runtime events, AI usage, and verification volume.
Integration flow
From signup form to verified server request
ZDX Auth handles identity and token authority. Your application owns its local session after the server-side exchange.
- Create a tenant and client appGenerate a client ID and secret, then register redirect URIs, origins, and allowed roles.
- Start password loginYour app sends email, password, redirect URI, origin, scope, and state to ZDX Auth.
- Exchange the callback codeYour server trades the one-time code for access and refresh tokens, then creates a local session.
- Verify access server-sideProtected routes verify token activity, issuer, audience, JTI state, tenant claims, and plan limits.
Security
Controls buyers expect before trusting auth
Access decisions are made with registered app settings, stored token state, tenant membership, role boundaries, and subscription status.
Exact redirect URI checksOrigin allow-listingClient role restrictionsHashed client secretsHashed refresh tokensOne-time callback codesGateway-protected verifyWebhook-backed billing state
Pricing
Start small, then scale the same integration
Every plan uses the same auth foundation. Paid tiers increase tenant, client app, API key, token verification, and onboarding limits.
Onboarding
Give users a guided path instead of a blank dashboard
The onboarding assistant reads redacted tenant, billing, and client app status, then helps users wire login, callbacks, token verify, refresh, revoke, and production checks.
Open Developer GuideImplementation support
Need ZDX Auth wired into your app?
ZeroDriveX can help configure client apps, callback routes, server-side token verification, billing limits, and the first protected routes in your product.
Request Integration Help- Create tenant
- Create client app
- Add redirect URI
- Post app password login
- Exchange one-time code
- Verify token server-side
Start building
Launch a clean auth flow for your customer app.
Start free, validate the integration, and move into higher limits or custom implementation support when your product needs it.
View Pricing