Own your data: a second PIMS you control

The most common reaction we hear from practices is some version of: "I love the idea, but changing my PIMS is a nightmare I'm not signing up for." That's not resistance. It's wisdom. A PIMS migration is one of the riskiest things a clinic can do. So we stopped asking for one.

The model: connect, don't switch

Instead of rip-and-replace, picture a second PIMS that runs alongside the one you already use, and that you fully own. You connect it with an API key, your data flows in, and now you have a live, exportable copy of your practice's records in a system you control. No migration weekend. No retraining the front desk. Your incumbent keeps doing its job while you quietly gain leverage over your own data.

• Attach your existing PIMS by API key and mirror your records into a system you own.
• Build on the open API (reminders, analytics, AI agents) without asking a vendor for permission.
• Export everything, anytime. The whole point is that leaving is always easy.
• When you're ready, run it as your primary. Or never. The choice stays yours.

Where this goes

The near-term is self-hostable and open: clone it, run it, connect it. The next step is making it effortless: a hosted option where a clinic logs in, attaches their current system, and watches their owned copy populate, no DevOps required. Same open core underneath; we just run the boring parts for you.

Owning your data shouldn't require a migration. It should require an API key.

This is the part we're actively building, and it's where outside input matters most. If your PIMS has an API we should mirror, tell us. If it doesn't, tell us that too. That's a story worth telling.