mint-you is the working project name for ChaiOS — The Operating System for Cafés & Tea Shops, a production-quality multi-tenant SaaS platform that lets cafés, tea shops, coffee shops, bakeries, juice shops, and small restaurants run their business from one dashboard. ChaiOS exists to replace notebooks, Excel sheets, and WhatsApp-based management with a single, fast, premium, professional workspace per café.
The product is built for independent operators who run their business from a phone between rushes and from a laptop after close. They are not designers, but they live inside Shopify, Stripe Dashboard, Linear, Notion, and Vercel Dashboard, so they read craft as trust. The interface must therefore feel minimal, fast, premium, and professional — dense enough for power use, warm enough that a chai shop owner feels it was made for them.
This document is the System Requirements Document for the product. It specifies the current delivery: owner authentication, per-café multi-tenant workspaces, and the owner's management of products, orders, customers, inventory, staff, analytics, finance, and settings — all scoped so that no café's data is ever exposed to another café.
Audience. Café owners (the primary, explicit persona) and the staff/employees who work inside a café's workspace (an accepted inferred persona). The document is also the engineering contract for the frontend, backend, and deployment work.
ChaiOS is a React + TypeScript + Vite single-page application (Tailwind CSS, shadcn/ui, React Router) backed by Supabase (Auth, Database, Storage, Edge Functions where necessary) and deployed on Vercel. The provisioned runtime inventory is a shared FastAPI backend process for application APIs and domain modules, a MariaDB database for application-owned persistent data, and a React frontend. Feature APIs are added as routes and modules inside the shared backend rather than as new services.
Actors. The closed active-human persona set is:
Accepted behavior. Owner authentication (email/password login, forgot password, remember me, protected routes, logout, session persistence); per-café multi-tenant isolation; owner management of products and categories, orders and order items, customers, inventory (ingredients, recipes, suppliers, purchases), staff (employees), analytics, finance (expenses, payments, loyalty transactions, coupons, notifications, audit logs, subscriptions), and settings; a dashboard that summarizes the business and routes into each area.
Ownership. All human-facing work is owned by first-party application pages. Supabase Auth owns credential verification and session issuance; Supabase Database owns tenant-scoped persistence; Supabase Edge Functions own server-side work where necessary; Vercel owns hosting and delivery.
Narrow exclusions. No demo code and no placeholder pages. No cross-café data exposure. No customer-facing storefront, no POS hardware integration, and no payment-processor integration are specified by the source and are therefore out of current scope.
Removed from scope
ChaiOS is delivered as a first-party web application. Anonymous visitors reach the Landing page and the Login and Account Recovery surfaces. Once an owner establishes identity, all workspace destinations (Dashboard, Products, Orders, Customers, Inventory, Staff, Analytics, Finance, Settings) are protected and render only the signed-in owner's café data.
Identity is application-owned and established through Supabase Auth. First use is self-service enrollment with email and password; returning owners verify with email and password, optionally with remember-me session persistence. Password recovery runs through the forgot-password flow. Logout terminates the session and returns the owner to the public entry. These are journey prerequisites, not a separate account-management product.
Tenant isolation is a hard delivery boundary: every record is scoped to the owner's café, and no surface — including the café switcher, tables, and charts — may expose another café's data. The current delivery horizon covers everything described in this document. No future-horizon features are specified by the source.
Not applicable — no reference directive declares content_source. The visual-inspiration reference (Shopify, Stripe Dashboard, Linear, Notion, Vercel Dashboard) supplies feel only and contributes no product facts, copy, or capabilities.
FR-1 — Owner self-service enrollment (required_inference) As a Café Owner, I should be able to enroll with my email and password before first workspace access, so that I can establish my identity and reach my café workspace.
FR-2 — Owner login with email and password (explicit) As a Café Owner, I should log in with my email and password, so that I can access my café workspace.
FR-3 — Remember me and session persistence (explicit) As a Café Owner, I should be able to choose "Remember Me" and have my session persist, so that I do not re-enter credentials on every visit.
FR-4 — Café workspace provisioning and tenant scoping (required_inference) As a Café Owner, I should have my own café workspace, so that every record I see belongs to my café and never to another café.
FR-5 — Forgot password (explicit) As a Café Owner, I should be able to recover a forgotten password, so that I can regain access to my account.
FR-6 — Protected routes (explicit) As a Café Owner, I should be blocked from workspace pages until I am authenticated, so that my café data is never shown to an unauthenticated visitor.
FR-7 — Logout and session termination (required_inference) As a Café Owner, I should be able to log out, so that my session ends and I return to the public entry.
FR-8 — Manage products and categories (explicit) As a Café Owner, I should manage my café's products and categories, so that my menu is accurate.
FR-9 — Manage orders and order items (explicit) As a Café Owner, I should review and manage my café's orders and order items, so that sales are recorded accurately.
FR-10 — Manage customers (explicit) As a Café Owner, I should browse and manage my café's customer records, so that I know who I serve.
FR-11 — Manage inventory, ingredients, recipes, suppliers, and purchases (explicit) As a Café Owner, I should manage inventory, ingredients, recipes, suppliers, and purchases, so that stock stays accurate.
FR-12 — Manage staff (explicit) As a Café Owner, I should manage my café's employees, so that my team roster is current.
FR-13 — Review analytics (explicit) As a Café Owner, I should review analytics for my own café, so that I can make informed decisions.
FR-14 — Manage finance records (explicit) As a Café Owner, I should manage expenses, payments, loyalty transactions, coupons, notifications, audit logs, and subscriptions for my café, so that money and records are tracked.
FR-15 — Configure settings (explicit) As a Café Owner, I should configure my café's workspace settings, so that the workspace reflects my business.
FR-16 — Staff records sales and stock activity (required_inference) As a Staff / Employee, I should record sales and stock activity within my café's workspace, so that the owner's dashboard reflects reality.
FR-17 — Tenant isolation guarantee (explicit) As a Café Owner, I should never see another café's data, so that my business information stays private.
Muse: Rasmus Andersson. Headline: Warm-paper product craft with one hot tangerine signal.
Light mode tokens
#F6F3EE (warm paper)#FFFDF9#E4DFD6#141517#E4572E (tangerine, under 8% of any screen)#1F7A5C (deep tea green — success, settled payments, stock-healthy)#8A857C#FBF8F2Dark mode tokens
#141517#1C1E21#2A2D31#F6F3EE#E4572E (unchanged)#3FA37E (lifted green for contrast)#8A857CTypography
-0.03em tracking, sentence case, tabular-numeral figures as display objects.clamp(40px, 6.2vw, 84px) for the landing hero; section heads clamp(28px, 3.2vw, 40px); dashboard KPI numerals clamp(32px, 3.4vw, 44px); table body 14px; labels 12px uppercase 0.08em tracking.Shape language
#E4DFD6 (light) / #2A2D31 (dark).0 8px 24px rgba(20,21,23,0.08).Layout
#FBF8F2.Imagery
Avoid: Any blue or indigo primary; Inter, Roboto, Arial, Helvetica, Open Sans, Lato, Poppins, or system-ui as heading or body fonts; gradient-blob heroes, glassmorphism, rows of identical hover-lift cards; pill-shaped buttons; stock photography of smiling baristas or latte-art close-ups in the hero; decorative looping animation, bouncy easing, or particles; exposing any cross-café data in tables, charts, or the café switcher; treating dark mode as an afterthought.
The landing first screen is a 12-column warm-paper editorial spread, not a centred SaaS hero.
clamp(40px, 6.2vw, 84px) across three tight lines — "The operating system / for cafés & / tea shops." — with the second line in tangerine #E4572E and the rest in ink #141517. Beneath it a 46ch subline in Inter Tight 18px and a single tangerine primary button "Open your café" inline with a text link "See the dashboard".The concept recomposes only accepted content and controls: the product name, tagline, audience, the "Open your café" and "See the dashboard" actions, and the order/KPI concepts already accepted.
Interaction Model: Static Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief
components/, layouts/, hooks/, services/, types/, and utils/ structure.
ChaiOS — The Operating System for Cafés & Tea Shops
Products, orders, customers, inventory, staff, analytics and finance live in one workspace for tea shops, cafés, coffee shops, bakeries, juice shops and small restaurants — replacing the notebook, the spreadsheet and the WhatsApp thread with one dashboard your café owns.
No orders in the queue yet
Orders placed at the counter, by phone or from the floor land here in the order they arrive, with the café’s own IDs and totals.
Orders today
0
Avg ticket
0.00
Low stock
0items
Revenue
0.0012% vs last week
Ready when the rush is
Products, orders, customers, inventory, staff, and analytics live in your own workspace — every record belongs to your shop, and nothing else.

ChaiOS — The Operating System for Cafés & Tea Shops
Products, orders, customers, inventory, staff, analytics and finance live in one workspace for tea shops, cafés, coffee shops, bakeries, juice shops and small restaurants — replacing the notebook, the spreadsheet and the WhatsApp thread with one dashboard your café owns.
No orders in the queue yet
Orders placed at the counter, by phone or from the floor land here in the order they arrive, with the café’s own IDs and totals.
Orders today
0
Avg ticket
0.00
Low stock
0items
Revenue
0.0012% vs last week
Ready when the rush is
Products, orders, customers, inventory, staff, and analytics live in your own workspace — every record belongs to your shop, and nothing else.
No comments yet. Be the first!