Skip to main content
ÆAetheria OS/ about
Log inGet started
Who builds this

Built in a villa office,
for people who run villas.

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.

6
Live product screens
Six apps you can open today; more across the suite and roadmap.
1
Event core
One record for a booking, task, payout and guest.
24/7
Distribution running
Two-way OTA sync with an auto-retrying queue.
Live
In daily operation
LEAD Luxury Management runs on it every day.
How we work

Five rules we don’t break

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, payout and guest. No syncing between our own products, no exports, no reconciliation.
03
Your brand, not ours.
Guests and owners see your logo, your domain, your sending address and your tone. Aetheria stays behind the curtain by default.
04
Boring where it matters.
Card data never touches us. Backups are nightly and restorable. Every write is audited. We would rather ship slowly than explain an incident.
05
No lock-in as a strategy.
Full export any month, open API on every entity. 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 event stream
A booking, a task, a payout 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
Offline-tolerant workspace
Built for staff on patchy signal: actions queue on the device and sync when it returns, so a villa marked ready at 07:00 is not lost at 07:01.
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 from the Hotel tier.
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.
Next step
Read the inventory,
then judge us.
What’s includedBook a demo