One record for who a user is and what they pay for.
AboutIf your access checks and your billing system keep two different answers to "is this person allowed to do this," Rekey puts both questions behind one API. A user's login and their current plan live in the same tenant model, so the two stop drifting apart. You run it yourself with one docker compose command, the data stays in your Postgres, and the source is MIT licensed, so you can read it before you trust it.
What changes for you
- One record for who a user is and what they pay for
- A user's login and their subscription state live in one record. Access checks read what payment webhooks write, so there's never a second copy to reconcile, or to drift.
- Bring your own payment processor
- Stripe, PayPal, and Razorpay sit behind one BillingProvider interface, set per Application. You change a config value, not your billing code, and you keep your own processor account. Provider-specific fields live in metadata, and routing can pick a provider by country.
- You run it, you own the data
- docker compose --profile full up boots the API, Postgres, Redis, and the panel. There's no per-MAU meter, the Postgres is yours, and it's MIT licensed with the source on GitHub.
- Built for agents, read and operate
- Your users' agents can read their own account over scoped, read-only OAuth 2.1. That end-user MCP is off until you enable it per Application in the panel. A separate operator MCP lets your own agent run the workspace (read metrics, create apps, configure billing, cancel subscriptions) behind explicit consent scoped to read, write or admin. No static admin key changes hands.
Where things stand
- · Available today: self-host, the npm SDKs (`@rekey.dev/node`, `@rekey.dev/react`, `@rekey.dev/nextjs`, `@rekey.dev/astro`, `@rekey.dev/cli`, `@rekey.dev/mcp`), and the API.
- · Two ways to run it: self-host for free under the MIT license, or run it on Rekey Cloud, free to start. Want it inside your own cloud account instead? Ask about the enterprise licence.
- · Source: MIT licensed, a Docker Compose stack you build from source, code at github.com/rekey-dev/rekey.
- · Billing: Stripe, PayPal, and Razorpay behind one BillingProvider interface, with geographic routing by country.
- · Auth: email and password, OAuth (Google, GitHub, Microsoft, Discord, GitLab, Slack, plus any OIDC provider), MFA, refresh-token rotation with reuse detection, and session revocation.
- · Planned, not built: proration, bulk user export, SAML, LDAP, and SCIM. End-user passkeys are not available yet.