Why I built Domi Ops

I started building Domi Ops because the tools we used couldn't keep up with our family.

We ran on HomeHub for a while. It covered the basics, but it had nothing for homeschool records or health. We homeschool, and we needed grades, assignments, and records in the same place as the family calendar, not in a separate app. We also needed a shared calendar that stayed reliable.

Health was the biggest gap. My wife manages several conditions, and coordinating her care takes precision: the right doses at the right times, and everyone who helps knowing what's going on. Most apps give health a checklist or a notes field, and both fall apart once things get complicated.

Her medications don't follow "breakfast, lunch, supper, bedtime." Some repeat every few hours, some are as-needed, and some pause and restart. Pill organizers assume a schedule she doesn't have.

Because Domi Ops holds family schedules and medical details, I built it with privacy in mind from the start. Sensitive health fields are encrypted, each record is private or shared on purpose, and on your own server your records stay there. Features that call an outside service, like weather or Google sync, only do so once you set them up. It's open source, so you can run it yourself and check.

Everything in Domi Ops comes from our own daily use. When a workflow is slow or clunky, I fix it. When we're missing something, I build it. My family runs on this every day, which is the best test I know of.