Self-hosted auth, in private beta

Centralized authentication for every API you run.

Every API ends up building its own auth, and none of them do it well. P'adentro is one self-hosted service every API on your stack delegates to, so login, sessions, and account lockout live in one place.

// your API, delegating a login
POST/v1/auth/login → p'adentro
X-API-Key: <tenant-id>.<secret>
{ "email": "j.doe@acme.com",
  "password": "<password>" }
// p'adentro responds
200 OK
{ "access_token": "v4.public.…",
  "token_type": "Bearer",
  "expires_in_seconds": 900 }

Token abbreviated; refresh fields omitted. MFA-enabled accounts get an extra challenge step.Full login contract →

Every API rebuilds auth. Badly.

Inconsistent security, duplicated code, audit headaches. Every team reinvents the same brittle wheel. Moving auth into one service means one place to configure lockout, rate limits, and token verification.

Built for outcomes, not features

Safe

Self-hosted: your user data stays on infrastructure you control.

Secure

Account lockout after failed logins, per-tenant rate limiting, and short-lived, signed PASETO access tokens your API can verify locally.

Straightforward to adopt

One API for login, sessions, and accounts. Self-hosting needs PostgreSQL, Redis, a signing keypair, and a license key.

Auditable

Authentication and account events are recorded and readable through the API. Unknown-account and incorrect-password attempts return the same invalid-credentials response.

Scoped access control

Each tenant's API key only gets the resource-level permissions it needs, such as users:read or memberships:write.

How it works

Get a tenant API key

During the private beta, an operator provisions your tenant and approves its permissions.

Security & trust

Protections built into every login.

Lockout

Accounts lock automatically after repeated failed logins.

Rate limiting

Per-tenant limits keep abuse from one tenant contained.

Token safety

Signed, short-lived access tokens. A stolen token works until it expires, so keep lifetimes short.

No account enumeration at login

Unknown-account and incorrect-password attempts return the same invalid-credentials response.

Who it's for

01

Indie developers and solo builders shipping an API without wanting to own auth.

02

Startups and small dev teams who need auth solved once, correctly.

03

DevOps and infrastructure teams standardizing auth across many services.

04

Agencies and outsourcing firms building software for other companies, where trust matters most.

Private beta

Get early access

No spam, just one email when a spot opens up.