Orla vs Pabau

Pabau is a wide platform. It spans practice management, clinical records, marketing and reporting, and it serves a lot of different sectors — aesthetics and cosmetic clinics as well as physiotherapy and allied health. Breadth is a genuine strength: if you need one system to do many unlike things, breadth is exactly what you want.

Orla is deliberately narrower. It is a clinic operating system for physiotherapy, chiropractic, osteopathy, podiatry and multidisciplinary practices, in Ireland and the EU. And it is in build, recruiting build partners rather than customers.

The comparison is really about focus.

Narrow on purpose

Software built for many sectors has to make everything configurable, because what a physiotherapy clinic needs and what an aesthetics clinic needs are different shapes. Configurable is powerful and it is also work: somebody has to do the configuring, and somebody has to keep it right.

Orla makes assumptions instead, and the assumptions are about clinical practice:

• Care plans are a first-class thing — "six sessions over four weeks" — and one that has quietly lapsed surfaces on its own rather than waiting for a report.
• Rooms and equipment are booked with the appointment, not after it, and a slot with no free room never appears.
• Notes sign and lock, with amendments recorded rather than overwriting.
• Invoices carry the practitioner and CORU number an Irish patient needs to claim health expenses.

None of that is configuration. It is what the software assumes you are doing.

What that costs you

Being narrow means Orla will not stretch. If your practice also runs something that is not clinical allied health — retail, aesthetics with its own before-and-after workflows, a sector with different record-keeping rules — Orla is the wrong shape and a broad platform is the right one. That is not a weakness we are hiding; it is the trade we made.

Where Orla goes deeper

Reporting from the records themselves

Orla's figures are derived from the bookings, invoices and offers themselves, not from a separate reporting table that can drift out of step. The consequence worth knowing: a correction made today changes last month's report, because the report is the records. That is the behaviour you want and it surprises people, so the page says so.

The waitlist acts on its own

A cancellation is offered to every matching waiting patient at once, with an expiry, first tap wins, and everyone else told plainly that it went. No phone calls. How it works.

EU-only, and provable

Application, database and files in the EU. Per-clinic isolation enforced by PostgreSQL row-level security under every query rather than by application code remembering to filter. Reads journalled as well as writes, in an append-only log the application cannot rewrite.

What to check before you move — including on us

• Can you export everything, readably, with no exit fee? Ours.
• Are reads logged, or only edits?
• Does the import dry-run first, with counts on both sides?
• Which features are live today and which are roadmap? Ask every vendor this, us loudest of all.
• How many clinics run it in production today? Pabau's answer beats ours.

Moving, if you decide to

Pabau exports CSV; Orla reads it directly, with duplicate detection and a checked count on both sides, and nothing written until the dry run looks right. You run a parallel week before switching. The process.

When Pabau is the better choice

• You need breadth. More sectors, more modules, more configurability.
• You are outside the EU, where EU-only hosting is a constraint with no upside.
• You want built-in marketing at scale. Orla does recalls, campaigns segmented on real history, and review requests — but a dedicated marketing suite is a bigger thing than that.
• You want a finished product today rather than a weekly call and a say in what gets built.

If the narrow, opinionated version is what your clinic actually wants, that is the one we are building.