Two vendors, two failure modes
Auth provider hiccups, payments provider hiccups, webhooks land out of order. The reconciliation logic to keep them in sync is the part nobody wants to own.
Public beta · Built for the agent era
Auth + Billing for every app you ship.
Clerk-style auth + provider-agnostic billing in a single self-hostable Docker Compose stack. Multi-tenant from line one.
Provider-agnostic billing, typed SDKs, a built-in MCP server, and errors that tell you exactly how to fix them.
Self-host free · MIT licensed · Public beta — feedback welcome
1 stack
docker compose up
Multi-tenant
every row has appId
MCP
agent-ready
The status quo
Auth and billing shouldn't cost you two vendors
Most teams glue an auth provider to a payments provider with hand-written webhooks, then spend the next quarter chasing race conditions. The hidden costs add up fast.
Pricing assumes one app, forever
Vendor pricing pages assume you'll only ever ship one product. The moment you launch a second, you're double-paying per-MAU on shared users and per-seat on your team.
Lock-in by data gravity
Customer identities, subscription history, and webhook receipts all live in the vendor — exporting is technically possible but operationally painful at scale.
Built for humans, not agents
Errors say `400: invalid_request`. No machine-readable `fix:` hints, no MCP server, no introspection tools — your AI assistant is flying blind when something breaks.
How ReliPay fits
One stack. One panel. One API surface.
ReliPay is a self-hostable monolith that owns the auth + billing seam. You bring the payment provider; ReliPay owns the data, the panel, and the SDKs.
Self-host in one command
`docker compose up` boots the API, Postgres, Redis, and the admin panel. The same image runs in production.
Multi-tenant from line one
Every row carries `applicationId`. Run a marketing site, an admin tool, and a mobile app from the same ReliPay instance — separate data, shared infra.
Provider-agnostic billing
Stripe, PayPal, and Razorpay all sit behind a single `BillingProvider` interface. Top-level types express the intersection; provider-specific fields live in `metadata`.
AI-first DX
Errors carry a stable `code` and a `fix:` line. Public functions ship with JSDoc `@example`s. An MCP server lets Claude / Cursor / Claude Code introspect a live instance.
Modules
Everything in the seam, nothing outside it
ReliPay does auth and billing well. It doesn't ship a CRM, an email blaster, or a feature-flag service — pair it with the tools you already use.
Auth
- Email + password
- OAuth — Google, GitHub, plus 5+ providers via OIDC
- MFA with TOTP + downloadable backup codes
- Refresh-token rotation + session revocation
- End-user roles per Application (RBAC) with default-role enforcement
- WebAuthn / passkeys — register, sign in, and revoke
Billing
- Subscription, License, and Usage plan kinds
- Stripe, PayPal, and Razorpay all live behind one interface
- BYO provider credentials per Tenant (encrypted at rest)
- Geographic routing across providers
- Webhook receipts persisted + replayable from the panel
- Coupons + discounts live; trials and proration planned for v1.0
Usage & Licenses
- Track any metric — API calls, MB ingested, model tokens
- Auto-bill against usage plans
- License keys issued on plan activation, validated by SDK
- Per-Application meter definitions with units + aggregation
- Real-time meter dashboard in the panel
- Bulk CSV/JSON export — planned
Developer experience
- Typed SDKs: `@relipay/node`, `@relipay/react`, `@relipay/nextjs`
- Read-only MCP server: `list_applications`, `recent_payments`, `replay_webhook`
- `@relipay/cli` — non-interactive, `--json` everywhere
- Every error carries `code`, `message`, and `fix:`
- OpenAPI spec served at `/docs` on every running instance
- Admin panel built fresh in Next.js — same UX as the SDK examples
Pricing
Free to self-host. Hosted plan is in private beta.
ReliPay is in public beta — self-host today. The hosted plan is in private beta, opening to a small cohort first, with pricing announced at v1.0.
Self-host today · hosted plan in private beta
Self-host
Run the whole stack yourself. Recommended path today.
Free/beta
- Self-host Docker image + admin panel + SDKs
- Unlimited Applications, Tenants, End Users
- Bring your own Postgres + Redis
- Bring your own Stripe / PayPal / Razorpay keys
- Community support
- MIT licensed
Coming at v1.0
Hosted
ReliPay-hosted, you own the data. Pricing announced at v1.0.
Contact/for pricing
- Per-app + usage pricing (model — likely, finalized at v1.0)
- No per-seat fees — invite the whole team
- Daily backups — planned
- Uptime SLA — planned at v1.0
- Live MCP endpoint for your AI agents
- Priority support
Per-app + usage — pay for what you run, not per-seat
Join the waitlistEnterprise self-host
Self-host with private support + roadmap influence.
Custom/annual
- Everything in Self-host
- Named support contact
- Custom auth providers — SAML, LDAP, SCIM (planned)
- Early access to in-flight modules
- Influence quarterly roadmap
- Available from v1.0
For regulated environments
Talk to usFrequently asked questions
If you don't see your question here, ask via the contact form — this page is updated from real questions.
ReliPay is in public beta — self-host, the SDKs (on npm), and the API are available today. The hosted plan is in private beta, opening to a small cohort first. General availability (v1.0) finalizes licensing and hosted pricing.
Phase 1 · Onboarding in cohorts
Stop renting auth + billing.
ReliPay is in public beta. Talk to us if you'd rather not glue two vendors together for the next quarter.
Public beta · Self-host today · Feedback welcome