- Constraint
- The platform must facilitate payments without holding professional funds.
- Decision
- Model payment providers behind an adapter and split transactions at the source.
- Why it mattered
- The professional receives their share directly while Noxvi records only its fee.
- Trade-off
- Provider onboarding and payout status become first-class parts of the product flow.
Fintech · Full-stack product
Independent productNoxvi
A multi-tenant SaaS that takes independent fitness professionals from client registration to payment collection and monthly earnings.
Read this first
The system at a glance.
- What I built
- A business and payments workspace for independent fitness professionals in Brazil.
- My contribution
- Product architecture and full-stack delivery across onboarding, clients, payments, subscriptions, and analytics.
- Core challenge
- Keep tenant and money state correct while making every collection step understandable to a solo professional.
- Key technologies
- React, Hono, PostgreSQL, Drizzle, Better Auth, Stripe
Capability flow
How the system works.
Each step connects a user action to the system capability behind it.
-
Become payout-ready
The professional completes identity and bank-account setup before collecting money.
-
Register a client
Tenant-scoped client records become the source for charges and recurring arrangements.
-
Create the charge
PIX, boleto, and card flows expose the exact platform fee before confirmation.
-
Reconcile payment state
Provider events move payments through explicit, replay-safe lifecycle transitions.
-
See the business
Payment history and earnings turn transaction state into an actionable monthly view.
Engineering judgment
Decisions that shaped the system.
- Constraint
- Every client and payment belongs to one professional in a shared database.
- Decision
- Carry the professional identifier through every tenant-scoped query and model payment changes as explicit states.
- Why it mattered
- Isolation and legal state transitions stay visible in the domain instead of depending on UI behavior.
- Trade-off
- Repositories and tests must enforce the tenant boundary on every new workflow.
Technical evidence
Skills backed by this system.
Open any skill to see the other products and professional work connected to it.
- React Delivers the responsive workspace for onboarding, client operations, charges, and earnings.
- Hono Exposes typed product APIs while keeping payment and tenant rules inside focused services.
- PostgreSQL Stores tenant-scoped professionals, clients, payments, subscriptions, fees, and lifecycle history.
- Drizzle Keeps the relational payment model and its migrations explicit across the monorepo.
- Better Auth Handles secure sessions across the marketing, dashboard, admin, and API subdomains.
- Stripe Powers the separate Free-to-Pro platform subscription lifecycle without mixing it with client payments.
Technology stack
- React
- Hono
- PostgreSQL
- Drizzle
- Better Auth
- Stripe