Marketplace · multi-tenant SaaS · Bogotá, Colombia
A second tenant on the same Barriotech platform, themed with its own identity — same architecture, same Leaflet map, same Wompi integration, just a different visual layer. The platform supports multi-tenant theming from one deployment, so adding a new tenant is a config change, not a code change.
2025
See proj1 / Barriotech case study — same architecture, same tech, same platform. The only difference is the tenant theme (logo, color palette, copy voice) and the domain (gatocolectivo.com vs barriotech.com.co). Adding a new tenant should not require a new deployment.
Multi-tenant theming from one deployment. The Next.js app reads the tenant from the subdomain (middleware extracts it from the Host header), looks up the tenant config in the DB, and applies the theme at render time. Adding a new tenant is: (1) add a row to the tenants table with the subdomain, theme tokens, and copy, (2) point the DNS to the same deployment, (3) ship. No new code, no new deploy. The same Leaflet map, the same Wompi integration, the same admin panel — just a different visual layer per tenant.
Independent practice based in Cali. Automation flows, hand-built UI, and end-to-end web — for teams that would rather have it done than debate it.
Let's talkFrom intake to deploy, the studio keeps work in one place: scope, design, build, ship. Briefs land on the desk, deliverables land on the client.
Andrés Morales
