A self-hosted household manager.
One deployment per household — calendar, meals, finance, library, inventory,
and the people around it. Your data, your hardware.
from Wyrhta Labs
Heorth · KithLedger · @wyrhta/core · Concept & decisions
Wyrhta Labs (Old English wyrhta — "maker, wright") builds Heorth and the small services around it: each its own repo, each releasing on its own cadence, integrating over plain REST. Not a monorepo, not a plugin platform, not a hosted product.
| Repo | What it is |
|---|---|
| Heorth | The household system — calendar, meals, finance (Feoh), library, inventory, and the Hearth View kitchen touchscreen. |
| KithLedger | API-first personal relationship manager, built to be consumed by other tools rather than used standalone. |
| heorth-mcp | The household's single MCP server: one Streamable HTTP endpoint over the services' REST APIs. Owns no data. |
| wyrhta-core | Shared foundation @wyrhta/core — identity, auth, HTTP kit, household, DB conventions. On npm. |
| wyrhta | The umbrella repo: the concept, the decision records, and the Compose stack that knows every service exists. Start here. |
| website | The public site. Published to be read, not forked — it carries no licence. |
The umbrella repo has both quick starts — set up the workspace (one script clones every service and keeps it current) and run the whole stack (Compose, ports, databases, backups). Each service also runs on its own — see its README.
- Independent repos, shared by version. Services take
@wyrhta/corefrom npm at a pinned range; a core change reaches them only when a pin is bumped deliberately. - REST only; MCP is a container. Services ship HTTP APIs. Agent tooling lives in
heorth-mcp— a new service gains tools there, never its own MCP surface. - External systems stay the system of record. Microsoft 365 owns calendars, To Do owns everyday tasks; Heorth mirrors and enriches behind pluggable providers.
Every cross-cutting decision is an ADR — the fastest way to see why the architecture looks like this.
Pre-1.0, one maker, own household first. MIT, and public so it can be read and run — but "ready for other self-hosters" is the 1.0 gate and we are not there yet. Expect breaking changes between minors.
Please open an issue before a large PR; each repo's CONTRIBUTING.md states the cadence.
Security problems go through GitHub's private vulnerability reporting on the affected
repo, never a public issue — see SECURITY.md.
MIT licensed · built for one household, in the open