Yuvomi: A self-hosted household hub that ties tasks, meals, and budget together
Project brief: Self-hosted family planner - tasks, calendars, shopping, meals, budget. Your data, your server.
At a glance
- What is it?
- Yuvomi is a self-hosted family planner with nineteen modules, from tasks and meals to budget and health. Its key strength is that modules write to each other, so a meal plan becomes a shopping list and a pantry checkout restocks automatically.
- Who is it for?
- Adopt Yuvomi if you want a single self-hosted container to replace several household apps and you value module integration over depth in any one area. Skip it if you need a mature project with a large community or if you rely on polished mobile apps.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What Yuvomi replaces and who it is for
Yuvomi targets households that currently stitch together a to-do app, a calendar subscription, a cost-splitting tool, a meal planner, a grocery list, and a pantry tracker. The README lists a dozen separate app categories and claims Yuvomi replaces them with one self-hosted container. The intended user is a family, a couple, or a single person who wants to run their own server or NAS and does not want each service to hold a separate copy of their data. The project states that the only thing leaving the server is a version check, which is a strong privacy claim. The documentation emphasizes that all nineteen modules are independent, so you can switch off what you do not need. That modularity is the core value proposition: you are not forced into a monolithic workflow, but the integration between modules is where the project differentiates itself from a folder of separate apps.
How the modules talk to each other
The README gives concrete examples of cross-module data flow. The week's meal plan writes the shopping list: when you plan a meal for Thursday, the ingredients appear on the list. The pantry module books items back in when you tick them off a shopping list, with quantity. A task that is ticked off pays points to the assigned member, and those points can be spent in a reward catalog. A receipt uploaded once attaches to a transaction, a shared expense, and an inventory item at the same time. This is the architectural point: instead of separate silos, Yuvomi has a shared data model where modules read and write to each other. The schedule module is another example: it computes a read-only overlay for the calendar on read, so changing a shift pattern leaves no stale appointments behind. That design choice avoids the synchronization problems that would come from writing generated events into the calendar store.
The nineteen modules and what each one covers
The README lists all nineteen modules in a table. Tasks offer a Kanban board with deadlines, priorities, subtasks, tags, recurring schedules, and multi-member assignment. There is a history view that shows what was completed grouped by day, and you can lock a task so only its creator and admins can redefine it while others can still tick it off. Shopping lists are aisle-organized and support swipe gestures. Meals is a weekly drag-and-drop planner with a recipe sidebar and direct export to shopping. Recipes can be created, duplicated, and scaled, and you can mirror a Mealie or Tandoor instance read-only. Pantry tracks stock, storage location, and best-before dates with expiry and low-stock filters. Calendar syncs two-way with Google and CalDAV, one-way with Outlook via Microsoft Graph, and supports subscriptions and per-event visibility. Documents can use WebDAV or Google Drive storage. Inventory is off by default and tracks purchase price, warranty, and linked receipts. Budget has accounts, loans, subscriptions, and per-category planning, plus a personal mode that hides titles and categories while keeping amounts shared. Housekeeping handles staff schedules and billing. Rewards gives points on tasks with an auditable ledger. Health tracks vitals, medications, labs, activity, and cycles. Schedule handles rotating shifts and fixed timetables. Notes and Contacts includes Markdown sticky notes and CardDAV sync. Birthdays auto-creates calendar events. Family manages member profiles and invite links. Reminders covers tasks, events, renewals, warranties, and best-before dates via in-app badges, push, or Gotify, ntfy, or webhook. API Tokens provide Bearer or X-API-Key auth with an OpenAPI 3.0 spec and a built-in MCP endpoint for AI agents. Backup supports manual and scheduled backup/restore with pre-restore rollback.
Getting it running: install and first steps
The README says you can install in minutes and points to a container image at GitHub Packages. The exact commands are not in the provided material, but the repository has a container package, so you would pull the image and run it on a home server or NAS. The documentation section is linked but not included here, so the precise docker run command or docker-compose file is not visible. The project offers a web-based tour and screenshots at yuvomi.cloud. The README mentions 24 languages and a German translation, so localization is built in. The installation is container-based, which matches the target audience of home server and NAS users. The version check is the only outbound network call, which is a deliberate privacy feature. There is no mention of a desktop app or mobile client; the interface appears to be web-based, with a wall mode for kitchen tablets and an Immich screensaver for idle screens.
Security, encryption, and API access
The README highlights optional AES-256 database encryption and zero trackers. That is a meaningful claim for a self-hosted app: even on your own server, you can encrypt the database at rest. The API Tokens module provides Bearer or X-API-Key tokens, an OpenAPI 3.0 spec, and a built-in MCP endpoint for AI agents. Writes are retry-safe via an optional Idempotency-Key header. That idempotency support is a thoughtful touch for automation, because it prevents duplicate side effects when a client retries a request. The MCP endpoint is notable for AI integration, but the README does not detail how that endpoint is secured or rate-limited. The version check is the only outbound traffic, but if you enable Google, CalDAV, Outlook, WebDAV, Google Drive, Mealie, Tandoor, or cloud backup, those integrations will necessarily send data to those external services. The README does not clarify whether the version check sends any identifying information beyond a version number. The encryption is optional, so you must enable it yourself.
Limitations and cases where it is the wrong tool
The README does not list any limitations, but several are apparent from the material. First, the project is young: the latest release v2.52.1 was pushed on 2026-08-29, and there are three releases on the same day, which suggests rapid iteration but also a fast-moving codebase that could introduce breaking changes. The README is truncated, so the full documentation is not available to verify installation details or upgrade paths. Second, the schedule module is off by default, and inventory is off by default, so you must enable them. That is a design choice, but it means the default install does not include all features. Third, the calendar sync is one-way for Outlook, not two-way, which may be a limitation for households that rely on Outlook. Fourth, the Housekeeping module targets households with staff, which is a niche use case and may be irrelevant for most families. Fifth, the project has no mention of a mobile app; if you need native push notifications or offline access, you depend on the web interface and opt-in push. Finally, the README claims 19 modules and 24 languages, but the actual quality of each module is not described in depth. For a household that only needs one or two functions, a single-purpose app might be simpler and more mature.
Alternatives and how they differ
The README mentions Mealie and Tandoor as recipe managers that can be mirrored read-only into Yuvomi. That is a direct alternative for the meals and recipes part: Mealie and Tandoor are dedicated recipe and meal planning apps, whereas Yuvomi's recipe module is one of nineteen. The difference in approach is that Mealie and Tandoor focus deeply on recipe management, with features like import from URLs, nutrition, and meal planning, while Yuvomi integrates recipes with shopping, pantry, and budget. For a household that already uses Mealie, Yuvomi can mirror it, so you do not have to migrate. Another alternative for the broader household planner space is Home Assistant, but the README does not mention it, so I cannot compare directly. The key difference is that Yuvomi is a single application with a unified data model, whereas a set of separate apps requires manual or API-based integration. The trade-off is depth versus integration. If you value recipe-specific features, a dedicated app is better; if you want the meal plan to write the shopping list, Yuvomi has that built in.
Maintenance, license, and upgrade cost
The project is licensed under MIT, which is permissive and allows commercial use, modification, and redistribution with attribution. The repository is not archived and has recent releases, so it is actively maintained. The release cadence is high: three releases on the same day (v2.52.1, v2.52.0, v2.51.2) indicates a fast development cycle. That means you should expect frequent updates, and you will need to keep your container image current to get bug fixes and new features. The README includes a changelog, which is good practice for tracking changes. The backup module offers manual and scheduled backup/restore with pre-restore rollback, which is a safety net for upgrades. However, the README does not specify a migration path between major versions or whether database schema changes are automatic. Given the rapid release pace, you should test upgrades in a staging environment if you have one. The optional cloud upload for backups means you can store backups offsite, but that also means data leaves your server by your choice. The maintenance cost is moderate: you need to monitor releases, apply updates, and occasionally test the integrations. The MIT license simplifies adoption because there are no licensing fees or restrictions, but you are responsible for your own support since there is no mention of a commercial support offering.
Editorial conclusion
Adopt Yuvomi if you want a single self-hosted container to replace several household apps and you value module integration over depth in any one area. Skip it if you need a mature project with a large community or if you rely on polished mobile apps. Before adopting, verify that the AES-256 encryption, backup rollback, and the specific module integrations (Google, CalDAV, Mealie, Tandoor) match your server environment and data needs. The project is under active development with frequent releases, so plan for regular updates. If you are comfortable with a young codebase and want data to stay on your own server, Yuvomi is a concrete, integrated alternative to a stack of separate subscriptions.
Community notes