Project detail · technical deep-dive
Architected and built a full SaaS platform for the Brazilian real-estate market: NestJS backend with Clean Architecture, multiple Next.js frontends, a React Native mobile app, and solid infrastructure for queues, payments, and integrations.
Role
Full-stack / systems architecture
Timeline
2025–2026
Tech
NestJS 11, Next.js 15/16, React 19, React Native (Expo), Prisma 7, PostgreSQL 17, Redis, Bull, Docker
3 page views
Product showcase

Landing page: product story and entry into the MylarPro ecosystem.
In production
Status
9 projects
Applications
100+ entities
Data models
Clean Architecture backend
NestJS API with Use Case → Repository → Prisma, immutable domain entities, Either monad for errors, and strict scoping by organizationId (rigorous multi-tenancy).
Specialized frontends
Next.js App Router across four apps (dashboard, customer portal, admin, public catalog), each with its own auth, modern stack (React 19, Tailwind v4), and shared React Query + Zod patterns.
Payments & queue infrastructure
Stripe and ASAAS integrations, Bull queues for async work, Gotenberg for PDFs, Cloudflare R2 for storage, Evolution API for WhatsApp, and a full billing pipeline with fines, interest, installments, and reconciliation.
Live product, repository, or both—pick what matters for this case.
MylarPro is a complete multi-tenant SaaS for the Brazilian real-estate market, built so agencies can manage the full lifecycle of contracts, billing, payouts to owners, and customer relationships. The monorepo bundles nine independent applications—backend, four web frontends, mobile apps, a public catalog, and marketing pages—all integrated via API and backed by a single PostgreSQL database with 100+ Prisma models.
More than a CRM, it is a financial-operations system that automates dunning, boleto/PIX issuance, commission math, owner payouts, DIMOB (Brazilian rental-income reporting), and bank reconciliation—with accounting discipline aligned to how the local market actually works.
organizationId with ownership checks on each operation. Isolation enforced at the application layer.services, queries, models, components) and a consistent stack: React Query, Zod, react-hook-form, shadcn/ui.PARTIALLY_PAID status and full transaction history.PENDING_APPROVAL → admin approves/rejects with a full audit trail.IN_AGREEMENT status.Entity.create(), abstract repositories, explicit mappers, and Either in 100% of use cases.organizationId validated on every operation, audited by default at the controller layer.