Who builds this
Aetheria OS started as internal software for a Bali management company that was tired of reconciling four systems by hand. Everything in it exists because a real operator asked for it on a real Tuesday — not because a roadmap needed filling.
Aetheria OS is part of the Leisure Group, the Bali-based group behind The Luxury Bali. Your property’s data stays in your own workspace, isolated from every other account and yours to export at any time.
9
Apps on one data core
Nine apps you can open today, with more on the roadmap.
1
Data core
One record for a booking, a task, a statement and a guest.
24/7
Distribution running
Two-way OTA sync with an auto-retrying queue.
Live
In daily operation
LEAD Luxury Management — our own villa-management company — runs on it every day.
They read like opinions. In practice they are the reason the product stays small enough to understand and fast enough to trust.
01
Operators first, dashboards second.
If a housekeeper on a three-year-old Android cannot use it one-handed at 07:00, it is not finished. Reporting is a by-product of doing the work, not a separate ritual.
02
One record, never two.
Every module reads and writes the same booking, task, statement and guest. No syncing between our own products, no exports, no reconciliation.
03
Your brand, not ours.
Guests and owners see your logo, your colours and your tone on every plan, and your own domain on Boutique. Emails carry your name and branding, sent from our verified domain.
04
Boring where it matters.
Card data never touches us. Backups are nightly and restorable. Sensitive changes are logged with who and when. We would rather ship slowly than explain an incident.
05
No lock-in as a strategy.
Export your data any time as JSON, and owner statements as CSV. We would like you to stay because it works, not because leaving is expensive.
What it runs on
Built for a real operations team
Not a feature list — the four things underneath that decide whether a villa team can trust it on a Saturday changeover.
Distribution
Two-way OTA rail
Rates, availability and restrictions push out; reservations pull back in. A queue with auto-retry and a sync log means a failed push is visible, not silent.
Core
One data core
A booking, a task, a statement and a guest are one record each. Every surface reads the same row, so the owner's calendar and the housekeeper's queue can never disagree.
Field
A workspace for the field
Built for staff on a phone: each team sees its own queue, and a villa marked ready writes straight to the board the manager is looking at.
Brand
White-label by default
Your logo, palette and typography across the workspace and owner surfaces on every plan; a fully white-label guest booking engine on your own domain, with no Aetheria branding, on Boutique.
The team you actually get
Small on purpose
No tiered support desk. The people who reply are the people who build it, and whoever wrote the module you are asking about is one message away.
Talk to us →Roster to follow. Rather than list roles we cannot yet stand behind, this space stays empty until the names and responsibilities are confirmed — the same rule we apply to every figure on this site.