Multi-tenant Platform

Taxi Club

Multi-country taxi platform from a single repo with no hardcoded country logic.

Taxi Club — product screenshot
Taxi.club — live product (taxisclub.com).
Problem

Launching across France, UK, Italy, and Spain without forking the codebase per country.

Solution

Domain-based tenant resolution over a single Next.js + NestJS repo, with booking workflows, admin dashboards, and a unified customer experience.

Architecture

Domain-based multi-tenant resolution · single Next.js + NestJS repo · per-tenant config

EntryFR · UK · IT · ES domainsHost header
ResolutionTenant resolver middlewarePer-tenant configNo hardcoded country logic
AppSingle Next.js + NestJS repoBooking workflowsAdmin dashboards
Request / data flow, left to right.
Why it's built this way

Overrode an early proposal for three separate frontend repos - that path multiplies maintenance by country and guarantees drift. One multi-tenant app resolving the tenant from the Host header serves every market and future country from a single deployment, with country behavior in config.

Impact →Four-market launch path on one maintainable codebase.
Next.jsNestJSMulti-tenantDomain routing
Visit live site ↗Discuss a build like Taxi Club →← All work
More work
PaylioFlagship SaaSiBoardingPassPayments & AnalyticsE-VignettesMulti-currency Commerce