About
Built for hospitality, by people who've run a shift.
halopos is a Sydney-based company building the POS Australian hospitality actually deserves.
Why we're building halopos
Australian hospitality runs on POS systems designed in the US or Europe a decade ago, with AU compliance bolted on as an afterthought. GST, BAS, EFTPOS and the quirks of our surcharge rules deserve a first-class model, not a checkbox in settings.
We also think the POS market is hostile to operators: long contracts, locked hardware, punitive processing skim. halopos ships three pricing models so you can pick the one that aligns with your margin — and switch when your business changes.
Our architecture, in one paragraph
Next.js App Router on TypeScript strict, Postgres with RLS for tenant isolation, Drizzle for schema, tRPC for the API, Ably for realtime, Stripe for billing, Clerk for auth. A Hardware Bridge runs locally at each venue to drive printers, EFTPOS terminals and cash drawers — so the register keeps working when the internet doesn't. Data lives in Sydney.
Where we are in the roadmap
M0 (foundation) and M1 (closed pilot) are code-complete. M1.5 sprints A–F hardened realtime, billing, reporting and the audit log. M2 shipped multi-branch mode, central staff, pricing models, floor plan polish and second-reference printer + EFTPOS adapters. We're currently in the M3 run toward GA.
Want to chat?
Book a 20-minute call with the team and we'll walk you through a real shift.