About
Build for one. Pluralize for thousands.
Pluralize is the multi-tenant backend for indie developers. Auth, billing, file storage, and per-tenant data — wired up in minutes, not weeks.
Why this exists
Every solo project that ships starts the same way: build a single-user app, then realize multi-user support means weeks of plumbing — auth, email verification, password resets, billing, plan gating, tenant isolation. By the time you've built it, you've forgotten what you were trying to ship.
Pluralize collapses that plumbing into a few lines. You keep your domain logic, your database, and your design. Pluralize hands you the tenant identity and lets you scope your data by it. When you're ready to charge, hook up Stripe Connect from the dashboard and Pluralize enforces plan limits for you.
How it works
- Sign up as a developer, create an app in the dashboard. You get an
appIdand anapiKey(publishable, like Stripe's). - Drop the SDK into your app. The browser SDK handles signup, login, sessions, password reset. The server SDK verifies tokens and gives you the tenant id to scope queries.
- Configure plans + entitlements (max records per tenant, AI quotas, feature flags) from the dashboard. Pluralize enforces caps; you read entitlements in your code where it matters.
- Connect Stripe in one click. Your customers pay you directly, Pluralize takes a flat 5% application fee.
Who builds it
Pluralize is built by Pablo Llorens — solo indie developer, based in Spain, building the platform he wished existed for his own side projects. The first consumer of Pluralize is Menaki, a multi-user mealplanner. Every gap Menaki hits becomes a feature on the Pluralize roadmap.
That dogfooding is intentional. Pluralize's scope is bounded by what one developer actually needs to ship a real product, not by theoretical platform completeness.
Principles
- Bring your own database.Pluralize hands you the tenant id; your data stays in your Postgres. We don't want to be the place your domain data lives.
- Honest pricing.Hobby tier is free, fully functional, with caps that protect both of us. Paid tiers exist because compute isn't free, not because of artificial scarcity.
- Standards over magic. Web Standard
Request/Response, JWTs, plain HTTP introspection, OAuth where it fits. No SDK lock-in we couldn't replace tomorrow with a curl command. - Small surface, deep coverage.Auth + billing + light data store. We don't do AI orchestration, vector DBs, or ten flavours of file processing. Other tools do those better.
Get in touch
Questions, bugs, feature requests, or you just want to tell me your weekend project — drop a line at hello@pluralize.app. Issues live on GitHub.