Baby Buddy
Baby Buddy is a private self-hosted child care tracker that centralizes feeding sessions, sleep cycles, diaper changes, and developmental health milestones into a collaborative dashboard for parents and caregivers. Caregivers can start quick timers on mobile devices to measure nursing intervals, bottle feedings, naps, and tummy time sessions with single-tap precision. The dashboard automatically calculates daily averages, feeding amounts, and awake windows to help families establish consistent daily sleep and feeding routines. Parents can track diaper changes by recording wetness, stool consistency, and color anomalies to spot digestive health changes early. Physical measurements including weight, height, and head circumference plot directly against World Health Organization growth curves to visualize percentile progression between pediatric visits. Multi-child profiles allow families with twins or multiple young children to switch contexts instantly and monitor individual growth timelines. Granular user permissions let parents invite nannies, babysitters, and relatives with restricted logging permissions while keeping administrative settings private. The built-in REST API and webhook system enable physical smart button clicks and home automation routines to log events instantly without opening a browser. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. BSD-2-Clause licensed.
Mealie
A recipe manager that feels like a consumer product rather than a homelab experiment: Mealie pairs a FastAPI backend with a reactive Vue frontend for the most polished self-hosted meal planning around. The killer feature is the recipe scraper: paste a URL from hundreds of supported cooking sites and Mealie imports the ingredients, steps, times, and photos automatically. Structured HTML/JSON paste, a Markdown-capable manual editor, and imports from other recipe apps (like Tandoor) cover everything else. Meal planning uses a drag-and-drop calendar with breakfast, lunch, dinner, and snack slots, plus rule-based random recipe insertion - constrain the pool by tags or categories per meal type or weekday. Shopping lists link recipes so all ingredients land in one place, organized into supermarket sections, and update in real time for everyone in the household. The multi-tenancy model is genuinely thought through: isolated Groups can host multiple tenants, and Households within a group share recipes and organizers while keeping meal plans and shopping lists private. Cookbooks group recipes by your own criteria, a cooking mode stays readable on a phone propped against the backsplash, and 35+ language translations ship built-in. A fully documented REST API and scheduled webhooks (e.g., today's meal plan to Home Assistant) make it automatable, with SQLite or PostgreSQL storage and automatic backups.
Yuvomi
Replace a dozen household subscriptions with one app that keeps your family's tasks, calendars, meals, budget, and shopping in a single private place you control. Nineteen modules cover the daily rhythms of a household: assign chores with deadlines and priorities, plan the week's dinners and push the ingredients to a shared shopping list in one tap, track income and expenses by category with automatic subscription renewal warnings, and log health activities from vitals to medications. Two-way sync connects to Google Calendar via OAuth, iCloud and Nextcloud via CalDAV, and Outlook via Microsoft Graph, so every family member's phone shows the same schedule without switching apps. CardDAV keeps contacts in sync with external address books. The budget module handles accounts, loans, split expenses, and per-category planning with savings goals and month-over-month comparisons. Documents attach to tasks, receipts link to transactions, and a checked-off grocery item books itself back into the pantry inventory with its quantity. A Kanban board, recurring task schedules, and a rewards ledger that pays out points for completed chores keep kids and adults accountable. Wall mode turns a kitchen tablet into a glanceable family dashboard, and the Immich screensaver shows your own photos when the screen goes idle. API tokens and a built-in MCP endpoint let AI agents and third-party tools interact with every module programmatically. Deploy on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
MediKeep
Your medical history, fragmented across a dozen patient portals, in one place on your server: MediKeep (formerly Personal Medical Records Keeper) is a self-hosted health record system. Built with a React frontend and FastAPI backend over PostgreSQL, it organizes 14 categories of medical data - medications with dosages and schedules, conditions, procedures, allergies, immunizations, symptoms, injuries, doctor visits and encounters, treatments, lab results, and even medical equipment with service dates and supplier info. Treatment management is genuinely sophisticated: an advanced mode links treatments to their medications with per-medication overrides for prescriber, pharmacy, and effective dates, and reverse lookup shows which treatments use a given medication. A dashboard summarizes records and recent activity, file uploads attach documents to records, and tagging works across categories. When a new specialist asks for your history, the report builder assembles custom reports by category and exports to PDF, JSON, or CSV - a curated, portable summary instead of a folder of photocopies. Authentication supports Google and GitHub SSO with OIDC providers like Keycloak and Authelia expected to work, and the built-in backup system protects the archive. Health data is exactly what should never live in someone else's cloud.
Hammond
When Clarkson, the once-popular fuel logger, stopped receiving updates, Hammond stepped in as its logical successor - a self-hosted vehicle expense tracker. Written in Go with a Vue.js interface and SQLite storage - a single lightweight container, no external database - it tracks every cost your vehicles generate: fuel fill-ups with cost, volume, and odometer readings; maintenance and repairs; and arbitrary other expenses, each attachable with photos and documents stored against the vehicle. The multi-user, multi-vehicle design is what sets it apart from phone apps: a household or small business adds all its vehicles and all its drivers, shares vehicles across users, and every fill-up lands in one ledger no matter who was driving. The Quick Entries feature respects how expenses actually happen - snap a photo of the receipt or pump screen at the gas station, then complete the structured entry later when you have a minute. Reporting works at both the vehicle level (cost per distance, fuel economy trends) and across the whole fleet. Migration matters here: importers for Clarkson, Fuelly, and Drivvo bring years of fill-up history along, so switching does not mean starting your data over.
Zusam
From the German "zusammen," together: Zusam is a private social space for a group of friends - a self-hosted alternative to the family WhatsApp group or the friends Facebook group, with no ads, algorithms, or data harvesting in between. The AGPLv3 project is deliberately modest in scope and stack: a Symfony PHP backend exposing a REST API over SQLite, with a lightweight Preact single-page frontend, designed for a low server footprint that runs comfortably on small hardware. Groups post messages into shared feeds that handle real life well: video and image uploads (with FFmpeg processing), photo albums for trips and events, and rich link previews with inline embeds for YouTube, Vimeo, Imgur, SoundCloud, Twitch, and Bandcamp - so sharing a song or a clip looks the way it should. When something needs to leave the circle, public link generation exposes a single message to non-members without opening the group. The interface is fully responsive and mobile-friendly, targeting Firefox ESR and recent Chrome. It is the small-web answer to a real question: where does a group chat's shared history live when you want it owned by the group instead of a platform?