SaaS development
We build multi-tenant platforms: data isolation, plans, recurring billing, and the operations that hold all of it up after launch.
SaaS looks like a web system with a login, and it is not. Serving several customers changes the data model, the testing, the support and the migrations. The bill arrives when the second customer needs something the first did not — or, worse, when one of them can see the other's data.
A platform with per-tenant isolation, roles and permissions, plans with usage limits, integrated recurring billing, and a new customer getting in without anyone configuring anything by hand. Plus the metrics to know who is using what.
It makes sense when you already sell a service manually and want to turn it into a product, when you have a system built for one client and need to serve many, or when billing today is a spreadsheet and an invoice at the end of the month.
Multi-tenant architecture
How each customer's data stays separate, what is shared, and what must never leak between them. It is the most expensive decision to change later, so it is the first one we make.
Plans, limits and recurring billing
Plan, usage limit, trial period, plan change, and what happens when a payment fails. Integrated with a payment provider, with the subscription reflected in access in real time.
New customer onboarding
Sign-up, first configuration and team invitations without depending on you. As long as a new customer costs you an afternoon, it is not a product — it is a service with a screen.
Roles, permissions and invitations
Who administers, who operates, who only looks. Invitation, removal and ownership transfer settled before the first customer asks.
Usage and product metrics
Who signed in, what they used, where they stopped. Without this, product decisions become opinion and support becomes guesswork.
Migration from single client to SaaS
Turning the system that serves one client into a product that serves many, without interrupting whoever already uses it. Done in stages, with the current client becoming the first tenant.
- Application
- TypeScript · Next.js · Node.js
- Data
- PostgreSQL · Redis
- Billing
- Stripe · Pix · Webhooks
- Authentication
- OAuth 2.0 · SSO · RBAC
- Infrastructure
- Docker · AWS · Vercel