Project · Multi-tenant SaaS · Live in production
Unlimit
A platform that lets agencies plug WhatsApp into their CRM - many phones, many brands, many agents, one inbox.
- Period
- 2026
- Role
- Full-stack engineer
- Client
- GoSetter - live at unlimit.gosetter.ai. Agency-style platform: a parent account creates 'apps' for each brand or sub-client and attaches WhatsApp devices to each.
4
roles in the permissions matrix
1
schema per tenant (true isolation)
2-process
split: API + worker on shared DB / Redis
live
in production with paying customers
Problem
Sales agencies want to message customers on WhatsApp the way they already message them in their CRM - but WhatsApp has phones, not seats, and a real agency runs dozens of phones across many brands. The platform needed to let an agency add a phone, scan a QR code to pair it, and from then on every inbound WhatsApp message routes to the right agent inside their existing CRM (GoHighLevel) and every CRM reply goes back out to the customer's phone.
Approach
- 01
Designed a true multi-tenant architecture: every agency gets its own isolated database schema on signup. No customer of one agency can ever see another agency's data, even by accident.
- 02
Built the WhatsApp integration as a separate worker process so a customer's connections survive every deploy. WhatsApp sessions are backed up to object storage and restored automatically if the worker restarts.
- 03
Wrote a permissions matrix loaded from the database into memory - Super Admin, Agency Admin, Manager, Agent - with the ability to re-sync without code changes.
- 04
Plugged the platform into GoHighLevel as both a CRM (every inbound message becomes a conversation) and a billing layer (more apps or more devices = an automatic subscription bump).
- 05
Built the front-end with TanStack Router and Query so the UI is fully typed, fast, and only fetches what's on screen.
From the live product

The product surface at unlimit.gosetter.ai - many numbers, one platform.

What the platform does, in the customer's words rather than the architecture's.

Onboarding in four steps - pair, assign, route, sync.
Stack
- Node.js · TypeScript · Express · Sequelize
- PostgreSQL (schema-per-tenant) · Redis · Bull queues
- Evolution API (self-hosted WhatsApp bridge)
- GoHighLevel OAuth + Conversation Provider
- Cloudflare R2 / MinIO (media + session backup)
- React 19 · Vite · Tailwind v4 · TanStack Router/Query · shadcn-style UI
Lessons
- Schema-per-tenant pays for itself the first time you onboard a customer whose data must never appear in anyone else's report. Cross-tenant queries become impossible by construction, not by code review.
- WhatsApp sessions are precious - losing them on a deploy means every customer's phone has to re-pair. Backing them up to object storage so the worker can rehydrate on restart is the difference between a smooth release and a Sunday-night incident.
- The CRM is the user. Once we modeled GoHighLevel as the primary surface - and Unlimit as the WhatsApp adapter - every confusing product decision got easier.