About
Auth + billing infrastructure, built in the open.
ReliPay is a self-hostable, multi-tenant service that puts user auth and provider-agnostic billing 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 docker compose up, and the data stays in your Postgres. It's a public beta from a small team, MIT licensed, and you can read the source before you trust it.
Design pillars
- One record for who a user is and what they pay for
- A user's login and their subscription state share one tenant model. A paying customer doesn't get locked out, and access doesn't linger after a failed payment, because both sides read the same record.
- 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 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
- A user's agent reads their own account over scoped OAuth 2.1 (read-only). A separate operator MCP lets your own agent run the workspace — read metrics, create apps, configure billing, cancel subscriptions — behind explicit, scoped consent (read / write / admin). No static admin key changes hands.
Where things stand
- · Public beta: self-host, the npm SDKs (`@relipay/node`, `@relipay/react`, `@relipay/nextjs`, `@relipay/cli`, `@relipay/mcp`), and the API are live today.
- · Try it: a live panel runs at panel.relipay.dev, no install.
- · Source: MIT licensed, a Docker Compose stack you build from source, code at github.com/relipay-dev/relipay.
- · Billing: Stripe, PayPal, and Razorpay behind one BillingProvider interface, with geographic routing by country.
- · Auth: email and password, OAuth (Google, GitHub, plus more via OIDC), MFA, refresh-token rotation, and passkeys for register and sign-in. SAML and SCIM are planned.
- · Planned for v1.0: trials and proration, bulk user export, and the hosted plan with announced pricing.