Reservations that don't collapse at scale.

Yes. Managed-cloud deployments are operated by our team on AWS, GCP, or other cloud providers per customer preference. Self-hosted deployments run on your VPC or on-premises infrastructure and ship with the same source code, a deployment runbook, and an update cadence agreed during contracting.

Data classification and residency are architected per engagement. Singapore is our default controller seat for regional deployments. Per-country hosting is supported where regulations require it (Indonesia public-scope on Indonesian territory under PP 71/2019, Vietnam impact-assessed transfers under PDPD 13/2023). Transfer logs and named DPO contacts are provided per jurisdiction.

Schema-preserving data export including bookings, members, payment line items, and audit logs, delivered within an agreed window at no additional charge. For custom-engineered deployments, source code is yours; we hand it over with documentation and a runbook.

Yes. Pricing and promo rules are composable filters applied at the session-payment join: tier eligibility, time window, branch scope, single-use vs bulk codes, blackout dates, capacity-fill conditions. Marketing teams configure these in the admin UI without engineering tickets. Our multi-branch boutique fitness case study walks through a worked example.

Branch is a first-class scoping dimension. Each branch runs its own schedule, roster, cash float, and inventory; HQ gets consolidated views in real time. Member tier and pack balance travel across branches with branch-specific priority rules respected.

Payment: Stripe, Xendit, Midtrans, and DOKU out of the box, plus bank-direct gateways scoped per engagement. POS: native counter and kiosk UI included; integration with external POS systems (Toast, Square, in-house) is scoped per deployment and quoted explicitly.