SHINY

A multi-tenant platform for Japanese non-profits running disability services, mobility transport, recreation and daycare. Bookings, staff rostering, vehicles, venues, attendance, incidents, daily contact books, compliance documents, live trip tracking and subscription billing sit in one system, with a web dashboard for coordinators and an Expo app for the staff, guardians and participants who are out in the field.

Welfare providers were running the day on paper and phone calls: a booking agreed by phone, a driver assigned on a whiteboard, a contact book filled in by hand and handed over at pickup. Nothing reconciled, guardians had no way to know whether the van was coming, and the compliance record only existed if someone remembered to write it down.

• Run bookings, staffing, vehicles and venues from one schedule
• Give guardians and field staff a phone app, not a cut-down website
• Let a guardian see the van is on its way without exposing a staff member's movements
• Bill in yen through Stripe with compliant Japanese invoices
• Ship the whole product in English and Japanese, not English with a translation bolted on

One Express and Prisma API over PostgreSQL serves three clients: a React dashboard for admins and coordinators, and an Expo app for staff, guardians and participants. Roles are ranked, so an actor can never act on someone who outranks them. Live position is stored on the assignment row and nowhere else, consent is checked twice before a fix is kept, and every guardian-reachable booking read goes through one relation that deliberately omits the live coordinates. Stripe handles hosted checkout in yen, including konbini and bank transfer, and a single daily cron does the reminders, the sweeps and the weekly digest.

• Bookings, staffing, vehicles and compliance records moved off paper into one schedule
• Guardians can see a trip is under way without a staff movement trail ever being stored
• New organisations onboard with zero map configuration and zero map cost
• Billing, invoices and consumption tax handled in-product rather than by hand

The privacy model was the architecture, not a setting on top of it. Deciding early that no movement history would exist made every later feature simpler, because there was never a table to accidentally expose.