Household task apps usually make you choose between sharing everything and sharing nothing. Dægwork shares one task at a time, with real dependencies, and never shows you what you're not allowed to see. Self-hosted, on your own hardware.
Shared to-do apps tend to offer one setting: share the whole list, or don't. That's fine for groceries. It's wrong for anything with structure: a task that depends on another, a document only one person should see, a chore that's private until it's done. So a shared calendar and a note on the fridge end up covering the gaps, badly.
Every task belongs to one person, who decides whether to share it and how much: read-only or full access, with one person or a group. Dependencies work across everything, not only inside one list, so real household logistics hold together. Finish the shopping list, then do the shop.
If you haven't been given a task, you can't tell it exists, even as a locked placeholder or a hint about what's blocking something else. A blocked task just shows as blocked.
Sub-tasks are for breaking things down. Dependencies say one thing has to happen before another, between any two tasks, wherever they sit. Most task apps give you one or the other. A real household needs both.
No vendor account, no data-retention policy to read. It runs as a couple of containers on hardware you control, next to Armarium.
A couple of small Docker containers, on the same FastAPI, async SQLAlchemy and React stack as Armarium, with SQLite by default. It runs as a sibling app on the same server.
It's still being built, and I'm not rushing it. It'll be open source once the sharing and dependency model is solid enough to trust with real households, and not before. The whole premise is people trusting each other with private tasks, so getting that right is most of the roadmap.