SaaS Product Engineering
Multi-Tenant Event SaaS
Contributed to an end-to-end multi-tenant event platform involving tenant-specific experiences, role-based workflows, event management, payments and production infrastructure.
The Product Challenge
Event platforms look simple from the outside - until multiple organizations run their own branded experiences on shared infrastructure. Every tenant needs its own roles, workflows, payment flows and data boundaries, while the underlying product has to remain one maintainable system.
The engineering challenge was keeping tenant experiences and access boundaries cleanly separated without slowing down feature delivery.
Designed around multiple tenant experiences while keeping product workflows and access boundaries separated.
My Engineering Contribution
- Designed multi-tenant backend services with RBAC-based tenant isolation.
- Integrated Stripe payment workflows alongside Cloudinary, S3 and Google Drive ingestion.
- Delivered a NestJS + Consul microservices platform with a Next.js frontend.
- Owned backend services and APIs end to end - from architecture through production deployment.
- Set up production infrastructure on GCP with Docker, SSL and CI/CD pipelines.
System & Product Considerations
- Tenant isolation as a product boundary, not just a database column
- Role-based workflows that differ per tenant
- Payment lifecycle and billing edge cases
- Service discovery and configuration across microservices
- Safe, repeatable deployments
Technical Areas
What This Project Taught Me
- Multi-tenancy is a product decision before it is an architecture decision - isolation boundaries surface in every feature you ship.
- Payments and onboarding shape more of the architecture than any framework choice.
- Unglamorous infrastructure - CI/CD, SSL, environments - is what actually lets features reach users quickly.