Dilan Dilruksha — Associate Software Engineer in Colombo, Sri Lanka

Small businesses were juggling WhatsApp, Instagram, email, customer records, product catalogs, payment proof, bookings, and follow-ups across disconnected tools. Owners needed visibility, staff needed shared context, and customers needed faster responses across every channel.

• Tenant-scoped access across inboxes, contacts, orders, bookings, websites, billing, analytics, and platform-admin workflows.
• Messaging and webhooks need background reliability without slowing dashboard requests.
• Website builder publishing must avoid leaking draft tenant data into public pages.
• AI concierge flows need memory, retrieval, and intent routing without taking over normal staff workflows.

1. 01
   FastAPI control plane with tenant-aware dependencies.

   Authentication, membership checks, plan limits, and RBAC happen in backend dependencies and service layers, so tenant boundaries do not depend on UI discipline or request-body trust.

2. 02
   Redis and Celery for work that should not block users.

   Messaging, appointment, subscription, AI, Instagram, WhatsApp, notification, and system jobs run through workers. The dashboard stays responsive while long-running operations are retried out of band.

3. 03
   Publish records for public websites.

   Website builder drafts can move into explicit publish manifests, so public pages read stable website, product, service, booking, and inquiry data instead of mutable dashboard state.

4. 04
   AI concierge as specialist agents behind a supervisor.

   Retrieval, memory, and specialist routes let the system answer product, order, booking, and reservation intents while preserving a clear path back to human staff workflows.

• Live at iroh.shop.
• Omnichannel inbox foundation across WhatsApp, Instagram, and email.
• CRM, catalog, checkout, orders, invoices, payment proof, bookings, and reservations share one tenant model.
• Website builder and publish records support public tenant sites, product/service pages, booking pages, and inquiries.
• AI concierge foundations include embeddings, retrieval, memory, and intent routing.
• Dashboard analytics summarize sales, orders, customers, payments, campaigns, bookings, communication, team activity, top products, and recent orders.

Tuition institutes were running operations across spreadsheets, payment receipts, chat groups, and physical attendance sheets. They needed a single platform that owners, tutors, students, finance, and admissions could share — without leaking one institute's data into another's.

• Tenant isolation across seven distinct user roles.
• Financial flows must stay auditable end-to-end — fees, ledgers, outstanding balances, receipts.
• Mixed-trust surfaces — a public marketplace sitting alongside private tenant data.
• One codebase, one deployment, many tenants.

1. 01
   Tenant identifier on every record.

   Role-based access enforced at the query layer through Prisma — not in the UI — so a misrouted page never becomes a data leak.

2. 02
   pnpm monorepo for a unified workspace.

   Front-end, server, and shared types live together. A permission change in one place propagates as a single, reviewable PR.

3. 03
   Receipt upload + super-admin approval.

   Tenants upload payment receipts; a super admin gates activation. A human checkpoint replaces auto-billing while the platform is still finding its shape.

4. 04
   QR attendance on the same data plane as the community feed.

   Students scan in once. Tutors, parents, and admissions all read the same record — no separate notification pipeline to keep in sync.

• Live at gurulink.online.
• Supports 7 user roles with tenant-isolated data.
• Seven role surfaces served from a single deployment.
• Fee → ledger → outstanding → receipt covered end-to-end.
• QR attendance, subscription approval, fee tracking, and public marketplace flows are covered.