How we measure, not what we claim.
Brulee API uptime is measured externally — a public number lands here once we have ninety days of trailing data from an independent probe. Until then, this page is the methodology, not the claim.
We’ll publish the figure because we live with it.
- How we measure
Uptime is measured by an external probe hitting our health endpoint every 30 seconds from two regions (Sydney, Melbourne). Outages count from the first failed probe to the first sustained success.
- Offline behaviour
When the network drops, Brulee keeps running. Orders queue locally, the EFTPOS terminal continues to authorise, the receipt printer prints. The moment the connection returns, queued orders sync. We have tested this with the wifi unplugged for two hours of continuous service.
- Data ownership
Your data is yours. Ask and we send a complete CSV bundle of orders, menu, customers, and reconciliation — no fee, no notice period, no “data processing” charge (self-serve export is coming soon). Cancel and take everything with you.
- Incident history
No incidents recorded. When something degrades, it is posted here while we work it — status, severity and resolution time, unedited.
- Breach response
We follow the OAIC Notifiable Data Breaches process under the Privacy Act 1988. We maintain a breach-response runbook internally and review it each quarter.
Reliability you can take with you.
Offline-first, export anytime, no lock-in. Try Brulee free on the iPad you already own.