Singapore is a small home market and a regional head office: many Singapore operators run or market resorts in Bintan, Batam, Desaru, Bali, Phuket and the Maldives, and sell them to Singapore residents for short breaks. A booking app there usually handles several properties, currencies and ferry or flight add-ons.
Where and who
We build for Singapore hospitality groups and operators of island and regional resorts, with properties in Sentosa, Bintan, Batam, Desaru and Bali. The app is designed around how those stays are actually sold: unit types, seasons, packages and the add-ons guests buy with the room.
Languages
English and Chinese, with Malay, Bahasa Indonesia, Japanese or Korean for regional guests.
Payments, taxes and price display
Guests pay through Stripe Singapore with SGD settlement, PayNow and GrabPay. GST and service charge are itemised with the total shown before payment. The fee and tax set-up is confirmed with your accountant before launch.
Compliance
We design for the PDPA and PDPC guidelines (consent, purpose limitation, access and correction, breach notification, the Do Not Call registry), the Spam Control Act for email and SMS, PCI DSS scope kept inside Stripe, WCAG 2.1 AA for public-facing services, and MAS Technology Risk Management guidelines where a financial institution is the client (you hold the licence, not us), at the time of writing (October 2026). Your counsel or DPO signs off; we implement. For resort bookings we also scope with your counsel the Hotels Act licensing that applies to Singapore properties and the local tourism rules of each country your resorts are in; guest ID documents are stored encrypted with retention rules.
Hosting
AWS ap-southeast-1 (Singapore), Google Cloud asia-southeast1 (Singapore), or Vercel with a Singapore region, in your accounts with your billing; encrypted Postgres, S3 and a CDN in front. Data stays in Singapore unless you choose otherwise.