Skip to content
Design mockup (D92) · prices per D139 · back to the reference index

Architecture

How SchedHubPH is built

Written for owners who want to know their business is in safe hands, and for the IT person they ask. No marketing fog: this is the actual design.

The big picture

Five layers, each with one job

Keeping jobs separate is what lets us add a new app, like TuluyanOS for hotels, without touching how your payments or customer records work.

1 · Channels

Where people meet it

Web app, the SchedHub phone app for customers and staff (coming), the booking page and widget, Facebook Messenger, the QR join page, self check-in kiosk and queue TV board, kitchen and customer displays, printers.

2 · Apps

Six modules

ReserbaOS, BentaOS, BisnesOS, SukiOS, HintayOS and TuluyanOS. Each can be switched on alone; connections turn on when two are on.

3 · Shared core

One source of truth

Business, branches, team and roles; customers and consent; the booking engine (rooms, tables, deposits); payments; messaging; audit trail; billing.

4 · Platform

Runs everything safely

Tenant isolation, sign-in and SSO, encryption, the Console our team uses, support cases and the knowledge base.

5 · Outside world

Connects out

Open REST API and signed webhooks, SMS and email providers, GCash/Maya pay links, iCal to Airbnb and Booking.com, AI assistants over MCP.

Modules

Apps that work alone and connect by themselves

No app needs another to work. The booking engine, customers and payments live in the shared core, so ReserbaOS and TuluyanOS can both use the same rooms without either depending on the other.

When these are both on……this happens by itself
ReserbaOS × BentaOSA finished booking becomes a bill; deposits come off the total; the service provider is filled in.
ReserbaOS × SukiOSMember discounts and credits at booking; completed bookings earn points; visits and no-shows counted.
ReserbaOS × BisnesOSOnly staff on shift, or on their fixed or rotating schedule, can be booked; approved leave blocks them; commissions from completed bookings (once built).
ReserbaOS × HintayOSRestaurants can seat a queue ticket at a table as a checked-in booking.
BentaOS × SukiOSSales earn and redeem points; member prices and credits apply at the counter.
BentaOS × BisnesOSClock in at the POS; commissions, tips and RA 11360 service charge feed payroll (once built).
BentaOS × HintayOSServing or seating a ticket can open an order.
SukiOS × HintayOSMembers are marked in the queue; served tickets count as visits.
HintayOS × BisnesOSRecords who served each ticket at which window.
TuluyanOS × ReserbaOSDay use and overnight stays share one calendar; spa and tours post to the room folio.
TuluyanOS × BentaOSCharge a restaurant bill to the guest’s room.
TuluyanOS × BisnesOSHousekeeping tasks go to rostered housekeepers; leave takes them off the board.
TuluyanOS × SukiOSMember room rates; stays count as visits and spend.

Turn one off and the connection pauses; no data is lost. SukiOS × BisnesOS and TuluyanOS × HintayOS have no connection in v1.

Multi-tenancy

Your data, isolated

Thousands of businesses share the platform; none can ever see another’s data.

๐Ÿงฑ

Your own address and customers

Each business lives at its own name.schedhubph.com. Every record carries your business ID, and the database itself refuses to show one business’s rows to another.

๐Ÿ—๏ธ

Your own encryption keys

Customer phone numbers and emails are encrypted with a key that belongs to your business, so the same person at two businesses can’t be linked.

๐Ÿช

Branch-level access

Managers and staff see only the branches they are assigned to. Owners see all of them in one view.

๐Ÿ”Ž

Tested on every change

Automated tests try to read across businesses on every release and must fail to do so.

Security

Security by default

The basics done properly, every time.

๐Ÿ”

Sign-in, SSO and PINs

SAML single sign-on for businesses that use Google Workspace or Microsoft 365, with an emergency Owner sign-in that needs an authenticator code. POS PINs for approvals at the counter. Our own team always signs in with two-step codes.

๐Ÿงพ

Audit trail

Discounts, voids, refunds, payroll approvals and any SchedHubPH access are logged with who, when and why.

๐Ÿ”’

Encrypted everywhere

HTTPS in transit; private files (IDs, payslips) in a private bucket, opened only through short-lived signed links.

โœ…

Approvals built in

Risky actions such as big discounts, voids and payroll need a manager or owner, even from a phone.

๐Ÿ›ก๏ธ

Least privilege for our team

Support can see your data only with your consent on a case, or in a logged emergency with a written reason.

๐Ÿ“ฆ

Checked before release

Dependencies are audited and each release gets a security review before it goes out.

Privacy

Built for the Data Privacy Act (RA 10173)

You are the personal information controller for your customers; we process it for you, only as you instruct.

โœ๏ธ

Consent on record

Marketing messages go only to customers who agreed, and the consent is stored with the date and channel.

๐Ÿ“ค

Access, correction, deletion

Customers ask you; you handle it in Privacy requests within the legal deadline. Export everything any time.

๐Ÿ—“๏ธ

Keep only what’s needed

Guest ID photos are deleted 30 days after checkout; other retention periods are set per record type.

Reliability

Built not to double-book, not to lose a sale

The failures that hurt a small business most are designed out.

๐Ÿ“…

No double-booking

The database itself refuses two bookings on the same chair, table or room at once, even if two people tap at the same second.

๐ŸŽซ

One number, one window

Call next locks the ticket, so two windows can never call the same customer.

๐Ÿงพ

Money stays consistent

Receipts, refunds and payroll are written once and never edited; corrections are new records. Each business day closes with a Z reading whose running total never goes down.

Before launch

What we will prove before we take paying customers

  • Backups
    Automatic backups with a tested restore and a written recovery plan.
  • Monitoring
    Error and speed targets, alerts, and a public status page.
  • Security check
    An outside review of sign-in, tenant isolation and payments.

Integrations & AI

Open by design

Your data should work with the tools you already use.

๐Ÿ”Œ

REST API and webhooks

Scoped API keys and signed webhooks for bookings, orders, payments and more.

๐Ÿ’ฌ

Messenger, email and SMS

Link your Facebook page to your booking page today; an AI receptionist that books from real availability is coming. Email and SMS go through your own provider.

๐Ÿค–

AI, with your permission

Ask SchedHub (beta) answers questions about your business inside the app. Coming: an MCP connection so your own assistant (Claude, ChatGPT, n8n) can work with your data.

Tech stack

What it runs on

Proven, mainstream technology that any good developer can maintain.

App

Next.js 15 · Node.js

One deployable serves the web app, the public booking pages and the API.

Database

PostgreSQL + Prisma 6

Database-level rules make double-booking a room, table or chair impossible.

Interface

Tailwind CSS 4 · shadcn/ui · Motion

Accessible components, keyboard-friendly, respects “reduce motion”.

Phones

Capacitor (iOS, Android), planned

The same screens as the web app, with push, camera and location.

Sign-in

JWT + httpOnly cookies · SAML SSO · TOTP

Short-lived tokens, company single sign-on, authenticator codes for Owner emergency sign-in and for our own team.

Quality

Vitest, Supertest, dependency audits

Every change is tested and security-reviewed before release.

Questions from your IT person?

We’re happy to walk through security and data handling.