Ship your SaaS on day one

Authentication, organizations, billing, and a native app — sharing one type-safe backend.

Everything the boring parts need

The work you'd otherwise repeat on every project, already done and tested.

Authentication

Passwords, magic links, one-time codes, social sign-in and two-factor with backup codes.

Organizations

Personal spaces and shared workspaces, with roles, invitations and per-tenant data scoping.

Billing

Plans, credit packs, monthly allowances and per-seat billing on Tap (mada, KNET, Benefit, Apple Pay), switched on as blocks.

Web and native

A Next.js app and an Expo app sharing the same API, session, translations and design tokens.

Localized

Locale routing, right-to-left layout, translated emails and type-checked translation keys.

Observability

Structured request logging, error reporting, feature flags and consent-gated analytics.

What is it built on?: Next.js and Expo on the front, Hono and oRPC on the back, Postgres through Drizzle, and Better Auth for identity.
Am I locked into a payment provider?: No. Billing sits behind a rail interface: Tap ships today, and adding another gateway is one file plus configuration. Your plans, credits and receipts live in your own database.
What do I need to configure before it runs?: Nothing. Every integration degrades to a working fallback, so a fresh clone signs up, sends email and renders the whole app before you add a single key.
Is it tested?: Yes. Unit tests cover the pure logic and end-to-end tests drive the real auth flows against a real inbox.

Everything above is already wired, tested and documented.