Rebuilt on ten years of feedback from thousands of clinics. Our job isn't to add every feature — it's to keep the core dependable, solve the deep problems, and give you an open API to build everything that makes your clinic unique.
We're making the features you use every day faster, simpler and rock-solid. The things your clinic depends on should feel effortless.
Every request points at something real. We find the underlying need and fix it at the foundation, once, properly — so every clinic benefits.
Workflows unique to your clinic no longer wait for a roadmap slot. Build them on a clean, open REST API — the primary, fully supported way to customise.
It's never been easier to build features — or harder to please every user. Say yes to all of them and you get every button anyone ever wanted, and a product nobody wants to use.
Sixty controls, nothing you can find. Everything to everyone ends up being nothing to anyone.
Four things, obvious at a glance. The rest of the requests were the same problem wearing forty faces.
A clean REST API with webhooks and access to every endpoint. Docs written to be read by AI tools as much as by people, with native MCP support so an assistant connects to your data directly and securely.
A few years ago a custom workflow meant hiring a developer. Now you describe it in plain English and build it — yourself, with a developer, or with an assistant at your side.
There is an API now, but building with it takes developer expertise. The LLM-first version described here — where you describe what you need in plain English — is coming soon.
A portal full of open requests implies a promise: that if your idea gathers enough votes or waits long enough, it gets built. For most requests that was never going to be true, and we won't set expectations we can't meet.
“A great product is defined as much by what it refuses to become as by what it ships. Our commitment is a platform that's dependable at its core, a joy to use, and flexible enough to grow with your clinic — however your clinic works.”
Tell us what you're trying to do — not the feature you think you need. The deep problems are exactly what we want to hear about.
