About
Auth + billing infrastructure, built in the open.
ReliPay is in public beta. The goal: a self-hostable Clerk-style auth + provider-agnostic billing in a single Docker Compose stack, multi-tenant from line one, designed for the era where most of the integration code is written by an AI assistant.
Design pillars
- Multi-tenant from line one
- Every domain row carries applicationId. There is no 'default' application — operations always specify one. Adding multi-tenancy later is a months-long rewrite; building it in costs nothing.
- Provider-agnostic billing
- Stripe, PayPal, and Razorpay sit behind a BillingProvider interface. Top-level types express the intersection; provider-specific data lives in metadata: Json. Geographic routing across providers is supported.
- AI-first DX
- Errors carry a stable `code` and a `fix:` line. Public APIs have zero `any` / `unknown`. Public functions ship with JSDoc @example. The CLI runs non-interactively. A read-only MCP server is included.
- Self-host first
- ReliPay boots with `docker compose up`. The hosted plan (launching at v1.0) is for teams who'd rather not run infra, not a gate on features.
Where things stand
- · Public beta — self-host today; hosted-plan teams onboard in cohorts.
- · Try it — a live panel runs at panel.relipay.dev (no install).
- · Distribution — published Docker image today; the MIT-licensed source opens after Beta 1 concludes.
- · SDKs (`@relipay/node`, `@relipay/react`, `@relipay/nextjs`, `@relipay/cli`, `@relipay/mcp`) — live on npm under the `@relipay` scope.
- · Hosted plan — private beta; pricing announced at v1.0.