Early build · schema + RLS proven

OpenDash

White-label ordering pages, WhatsApp bots, and operator dashboards for small Philippine delivery services.

Problem

Small delivery operators in Philippine tourist towns run on notebook-and-Messenger logistics; existing platforms take margins they can't afford.

Solution

A multi-tenant platform — each operator gets ordering pages, a WhatsApp bot, and a dashboard on shared infrastructure, with tenant isolation enforced in the database itself.

Architecture

Storefront / WhatsApp order → Webhook → Postgres (RLS per tenant) → Operator dashboard

OpenDash shows the build philosophy at its most explicit: the database, its security model, and a script that proves the security model came first — sessions before storefronts. The RLS verification harness runs after every schema change, making tenant isolation a tested invariant rather than a hope.

Repo evidence

Multi-tenant schema, row-level security, and re-runnable seed shipped as committed migrations — before any UI
verify:rls script proves tenant-isolation and anonymous-access rules hold after every change
Production Supabase project provisioned with matching migration history
Knowledge-base groundwork (platform brief, marketing research) maintained in the Gitea knowledge repos

Next build step

The Boracay pilot storefront and first operator dashboard over the proven schema.