Public surfaces
Landing pages, docs, and support intake stay fast, branded, and safe for internet-facing visitors.
Secure identity. Protect every API.
Self-hosted identity and API gateway controls for teams that need secure sessions, tenant-aware routing, and server-side key handling — without trusting the browser with secrets.
Landing pages, docs, and support intake stay fast, branded, and safe for internet-facing visitors.
Tenant-specific setup, operational flows, and sensitive examples live behind the main dashboard.
Services sit behind centralized identity, policy, audit, and abuse controls instead of duplicating auth logic.
Self-hosted
Deployment
Run in your controlled environment
HttpOnly
Sessions
Opaque cookies, memory-only UI state
Tenant-aware
Access
Context without trusting the browser
Audit-ready
Operations
Structured events for security review
Capabilities
From authentication to request governance, AuthDeep gives operators one controlled place to secure API access without leaking service secrets.
No service keys in browser code. Opaque cookie sessions keep auth material outside JavaScript.
Service credentials stay server-side at the gateway boundary. Frontend code never receives them.
Protect APIs with per-user and per-endpoint limits configured in the gateway.
Review request volume, errors, and latency trends from gateway telemetry.
Route requests to multiple registered services through one policy-aware gateway.
Define access by tenant, role, method, and path without exposing private service credentials.
Dashboard
Inspect service routes, request activity, and access controls from a console designed for secure operations.
Live
Request stream
Trend
Latency view
Rules
Access checks
Multi
Service routes
How it works
Three launch steps that keep credentials server-side while operators define tenant and service boundaries.
Register a service endpoint, store service credentials server-side, and define tenant-aware access rules.
Define public or restricted access per method and path. Set rate limits and usage quotas per user or team.
Use credentialed browser requests while AuthDeep keeps service credentials on the server side.
Pricing
Pay for what you protect. Gateway services and enterprise SSO connections drive cost. Users come free until you scale past generous soft limits.
Free
Evaluate AuthDeep with no commitment. 2 services, full local auth stack.
2 services · 10 users hard cap · 7-day audit logs
Starter
Small teams standardising identity. LDAP, SAML, and passkeys included.
5 services (+$4/extra) · 100 users · 30-day audit logs
Growth
Product teams protecting real workloads. Up to 2 enterprise SSO connections.
20 services (+$3/extra) · 500 users · 90-day audit logs
Scale
Growing businesses with complex multi-tenant and multi-SSO requirements.
100 services (+$2/extra) · 2,000 users · 365-day audit logs
Enterprise
Unlimited services, self-hosted license, dedicated support, and a contractual SLA.
Unlimited services · Unlimited users · 730-day audit logs
What counts as a service?
Each protected route or API proxy target in AuthDeep's service registry counts as one service.
What counts as an SSO / IdP connection?
Each SAML IdP or enterprise OIDC provider configured under a tenant. Social providers (Google, GitHub, etc.) do not count.
Can I upgrade mid-cycle?
Yes. Admin changes the plan; billing is pro-rated manually. Stripe integration arrives in v0.25.0.
What happens when the trial expires?
The account rolls to Free plan limits automatically. No data is deleted.
Can I run AuthDeep without internet access?
Yes. Enterprise self-hosted licensing works offline with no call-home requirement.
How is billing handled today?
v0.24.0 uses manual activation: you contact us, receive an invoice, and admin activates the plan. Stripe arrives in v0.25.0.
Review the security model, map your tenant and service boundaries, then launch with controls that keep secrets out of browser code.