Home Manifesto Contact

Get in touch

Whether you're exploring Orava for your organisation or interested in the vision behind it, we'd like to hear from you.

Frequently Asked Questions

What is OravaOS?

OravaOS is the clinical operating system for residential aged care. It brings together documentation, care planning, rostering, family communication, and compliance into a single intelligent platform — designed so that compliance is a natural byproduct of care that's genuinely working, rather than the thing operations are organised around.

Who is Orava for?

Orava is built for residential aged care operators — from single-facility providers to multi-site organisations. The platform is designed for the full care team: clinical leaders, registered nurses, care workers, allied health professionals, and facility managers. Our goal is a system that meets each user where they are, including the more than half of the care workforce who speak English as a second language.

How does OravaOS reduce documentation time?

Documentation currently consumes roughly 30% of every care shift. OravaOS is designed to bring that down to a fraction by capturing care information in the way that's fastest and most natural for each caregiver — then structuring it for clinical accuracy, continuity, and compliance automatically. The goal is documentation that takes minutes, not hours.

What stage is Orava at?

We're early. The vision is large and the work is foundational. We're building the core platform, working closely with aged care operators to ensure every decision is grounded in real operational reality. The direction is clear, the foundations are being laid, and we're focused on getting the fundamentals right before scaling.

How does OravaOS handle compliance?

Rather than organising operations around compliance requirements, OravaOS is built on the principle that every metric, standard, and audit criterion should fall naturally out of genuinely good clinical operations. The compliance data still gets captured — but the humans using the system aren't organised around the checkbox.

What does implementation look like?

We work directly with each organisation to understand their operations, workflows, and team dynamics before anything is deployed. Implementation is guided, staged, and designed to minimise disruption. We're building a system that meets its users where they are, not one that demands they change overnight.

Is resident data secure?

Absolutely. Clinical data security is foundational to everything we build. OravaOS is designed with healthcare-grade data protection, encryption at rest and in transit, and strict access controls. We treat resident data with the same care that the people in our system extend to the people they look after.

How is Orava funded?

Orava is privately funded and building toward sustainability through its platform. We're focused on creating genuine, lasting value for aged care operators — not on growth metrics that don't translate to better care. If you're interested in the investment side, we'd welcome a conversation.