Buildora
Multi-tenant e-commerce SaaS — every merchant store on its own subdomain, one shared codebase.
- Role
- Founder & sole engineer
- Status
- In development
Context
Buildora is a Shopify-style e-commerce platform. A merchant signs up, picks a plan and gets their own store on a subdomain.
It is currently in development.
My role
Founder & sole engineer.
The problem
Running a separate deployment per merchant means new infrastructure to provision, patch and pay for with every store. Buildora serves every store from one shared codebase instead, so a new store does not need a new deployment.
That puts three requirements on the backend: route each request to the right store, never let one merchant's data leak into another's, and bill each merchant on a subscription.
Subdomain → tenant resolution
Each merchant store lives on its own subdomain. An incoming request's subdomain identifies the tenant, and the backend resolves it to that merchant before serving the store.
Per-tenant isolation
All tenants share one codebase, but each merchant's data is isolated from every other merchant.
Billing & plans
Merchants subscribe to a plan, and subscription billing is built into the platform.
What I built
- Subdomain-based routing so each store resolves to its tenant.
- Per-tenant data isolation across the shared platform.
- Subscription billing and plan management for merchants.
Stack
- Node.js
- MongoDB
- AWS