VirgOS
One guest, one folio, one ledger.
Hospitality software is fragmented by default. The restaurant runs one system, the front desk runs another, the beach club runs a third, and each of them has a different idea of who the guest is. VirgOS puts a shared platform core underneath two composable layers, venue operations for food and beverage and stay operations for hotels, so a check, a cabana tab and a room night are charges on the same folio.
I designed the architecture, wrote the kernel, and build both the backend and the product surfaces. It runs offline first, because a venue that loses its connection still has guests to serve.
virgos.io →