Multi-tenant management platform

Run a service business from one place.

Appointments, sales, treatment packages, inventory, staff and customer care — for beauty spas, salons, clinics and retail shops. Every shop gets its own isolated data, multiple branches, and an app that opens on a phone or a desktop.

  • Beauty spas
  • Hair & nail salons
  • Clinics
  • Retail shops

Sign in

For staff and shop owners who already have an account. The sign-in form is in Vietnamese.

Đăng nhập dành cho các gian hàng

Quên mật khẩu? Đặt lại qua email — cũng mở khoá khi bị khoá vì gõ sai nhiều lần.

Tài khoản chưa có email thì nhờ chủ gian hàng đặt lại mật khẩu tạm cho bạn.

A day at the counter, as the app sees it

Today's schedule4 ·
Invoice HD000128 Transfer received
Revenue, last 7 days42.8M ₫ +18% vs last week
To do today

Illustrative UI — names and figures are examples, not real data.

From a real shop to a platform

A family-run beauty business built its own management software, then opened it up as a platform for many shops. The founder built it with Claude Code, uses it every day at the first shop, and every feature ships with automated tests and a step-by-step guide. The numbers below are counted from the source repository itself.

800+
commits since 5 Sep 2026
28
numbered production releases, 1 Oct 2026 → 12 Oct 2026
4,600+
automated tests across 312 files
119
controlled database schema migrations
40
step-by-step guide articles inside the app
31
data-rule check suites (money, stock, bookings, payroll)
  1. Sep 2026

    Started from a real need

    Studied the day-to-day of an operating skin-care clinic and committed to a three-tier architecture (platform → shop → branch) from the very first line of code.

  2. Sep 2026

    Twelve modules in one month

    Bookings, point of sale, packages & cards, inventory, payroll & commissions, cash book & reports, customer care, online booking, clinic records, platform tier — each with its own unit tests and data-rule checks.

  3. 1 Oct 2026

    Release 1.0.0 — live at the first shop

    Operations moved onto the platform; from here every deployment is a numbered release with a changelog written for the counter, and nightly backups go to two independent destinations.

  4. 10–11 Oct 2026

    Multi-branch: 5 rounds in 2 days

    Per-branch visibility, stock transfers, per-branch cash and reports, staff across branches, per-branch payroll — one release per round, enforced by database constraints.

  5. Next

    AI in the shop owner’s hands

    Business analytics Q&A and AI-drafted customer care messages, powered by Claude — see the roadmap below.

  • Built by the founder with Claude Code — nothing outsourced.
  • Used for real, every day, at the first shop before opening to others.
  • Every feature ships with automated tests and a step-by-step guide.

Built for many shops, not just one

A three-tier architecture from day one: platform admin → shop (tenant) → branch. Each tier has its own permissions and data.

  1. Strict per-shop data isolation

    Every business table carries a shop id and every query is scoped by it — one shop can never see another shop’s data.

  2. Vocabulary per business type

    The same feature is a "session" for a spa and a "visit" for a clinic. The platform sets defaults per type; each shop can override them.

  3. Multiple branches inside one shop

    Stock, cash drawers, shifts and pay periods are kept per branch; staff can be granted access to several branches; cross-branch collections leave a clear paper trail.

  4. A platform administration tier

    Plans and quotas, allowed business types, custom domains, and read-only "act as shop" sessions that are fully audited.

The full toolkit for a service business

Twelve modules in production, one interface, one data set.

  • Point of sale & invoices

    A counter-first sales screen: parked orders, several staff on one line, per-line notes, printable invoices, cancellations with a reason.

  • VietQR payments

    A bank-transfer QR code pre-filled with the amount and reference for each invoice — the customer scans and it is done.

  • Appointments & online booking

    Day, week and per-staff calendar views; a public booking page for customers with branch selection and bot protection.

  • Packages, prepaid cards & loyalty

    Multi-session packages, prepaid cards, expiry and renewal; every change of sessions or balance goes through a ledger.

  • Inventory & multi-branch transfers

    Stock cards, stocktakes, consumption norms, low-stock alerts and transfer slips between branches.

  • Cash book & end of day

    Cash / bank / wallet accounts, receipts and payments, per-branch closing and cash counts, cross-branch collections.

  • Staff, shifts, payroll & commissions

    Work schedules, attendance, pay periods per branch, and commissions snapshotted with the rule that applied at the time of sale.

  • Automated customer care

    Appointment reminders, thank-you notes, birthday wishes, expiring packages — by email, Telegram or Messenger; plus a "to do today" page.

  • Medical records for clinics

    Visits, diagnoses, before / after photos; tiered access rights, and every record view is logged.

  • Reports & CSV export

    Revenue, customers, stock, payroll — on screen or as a CSV file that opens in Excel.

  • In-app & push notifications

    New bookings, online requests, items that need attention — straight to the phone lock screen.

  • Installs on the phone like an app

    A progressive web app with each shop’s own icon and colour on the home screen; no app store needed.

How is it different from typical management software?

Things we do differently because we have stood at the counter long enough to know where it breaks.

  • Real multi-branch

    Not "one shop cloned": stock, cash, shifts, pay periods and per-branch access each have their own rules, enforced by database constraints.

  • Your data stays yours

    Every night the platform compares the data and only writes a new backup when something changed. Owners can download their own data at any time; restores are per shop and never touch other shops.

  • Runs on a global edge network

    The app runs on Cloudflare’s edge, pinned close to the database; backups go to two independent destinations.

  • Modern UI on any device

    Phone, tablet, desktop; light and dark modes; a brand colour per shop; touch targets sized for fingers at the counter.

  • A transparent audit log

    Who changed what, when, and the before / after — including when a platform admin acts on a shop’s behalf. Exportable.

  • Vietnamese-first, with a built-in guide

    Every feature ships with a step-by-step guide written for the person at the counter, updated together with the feature.

Roadmap

Born with AI, evolving with AI

The whole platform was built with Claude Code using a verify-every-criterion workflow. The next step is putting AI in the shop owner’s hands.

Built with Claude Code

Each feature goes through analyse → implement → verify → correct; automated tests and data-rule checks run before every deployment.

  • Coming soon

    Business analytics Q&A

    "Which service made the most profit this month?", "Which customers have not come back?" — ask in plain language, answered from the shop’s own data, powered by Claude.

  • Coming soon

    AI-drafted customer care messages

    Suggested reminders, greetings and package announcements in each shop’s own voice — a person still approves before anything is sent.

In production, not a demo

The first shop has run on the platform since 2026: every invoice, booking and pay period in the app is real business.

  • Numbered releases

    Every deployment is a versioned release with a changelog written for the people at the counter.

  • Tested before it ships

    Hundreds of unit tests and data-rule checks (money, stock, bookings, payroll) run before each deployment.

  • Nightly backups, two destinations

    Backups are written to object storage and to an independent backup drive; restores are rehearsed automatically.

Infrastructure & security

  • Cloudflare Workers · app runs at the edge
  • PostgreSQL · relational database
  • Cloudflare R2 · files & backups
  • Role-based access · per module × action
  • Audit log · every change leaves a trace
  • Bot & brute-force protection · Turnstile after 3 failed attempts

Open your shop on Xumây Beauty

Tell us your business type and number of branches — we will set up a trial shop and walk you through it.