-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
A self-hosted, browser-based workspace that tracks your mead from recipe and fermentation through to the bottle and the cellar — recipes, gravity logs, nutrient schedules, inventory, labels, tasting notes and aging, all backed by one SQLite file.
It's free to use, modify and share for any noncommercial purpose (personal, hobby, research, nonprofit/education) under the PolyForm Noncommercial License 1.0.0. Selling it or using it for commercial advantage is not permitted.
It's built for mead, but the cyser (apple), pyment (grape) and braggot (malt) recipes and the general calculators apply to cider/wine/beer-adjacent brews too. The honey-centric features (honey library, honey ratings, TOSNA honey-darkness scaling) are mead-specific.
No. MeadOS is self-hosted by design — it runs on hardware you control and keeps your data local. That's the point.
Just Python 3.8+. No pip packages, no Node.js, no build step, no separate database. Clone the repo and run python3 server.py.
Any number, on the same network. They all share the same data. Open http://<machine-ip>:8080 from a phone, tablet or another computer.
Yes: python3 server.py --port 9000 --db /path/to/meados.db. See Installation.
Run it under systemd (Linux) or launchd (macOS), or nohup for quick use. Full examples on Security & Deployment.
Yes — it's a PWA. Use your browser's Install / Add to Home Screen. It uses your brand logo as the icon and opens the cached shell offline.
Everything is in meados.db (plus uploaded images under assets/). Back up by copying that one file — safe even while running. Details and restore steps on Backups & Data.
Yes — MeadOS keeps the last 50 saves in a history table. Restore from the in-app history view or directly from the database. See Backups & Data.
No. git pull updates the app files only; your meados.db is untouched. Back up first as a habit.
On a trusted home LAN with no port-forwarding, no. If you expose MeadOS to the internet, set an external-access password and ideally run it behind an HTTPS reverse proxy.
It can be, with care: set the password, put it behind a reverse proxy with HTTPS (and ideally its own auth), and confirm the trusted-network settings. MeadOS adds login throttling, CSRF/origin checks and an audit log on top.
A NAT hairpin, CDN or VPN can make external requests appear with a private or shared IP. Check the security card, and add genuine ranges as trusted networks only when you're sure. Behind Cloudflare, enable the CF-Connecting-IP option.
No. It's entirely optional. Without it, you log temperatures and gravity manually, and the calendar feed gives you reminders. See Home Assistant.
Yes — create from scratch, fork a built-in recipe, save templates, import BeerXML, and export to BeerXML or PDF. See Recipes & Designer.
Each recipe carries a hand-curated verdict for every honey in the library — great / good / workable / clash — with a note on what that honey does to that specific mead, and your in-stock honeys pinned to the top. See Recipes.
By the data, not the calendar: a stable gravity across two readings at target, plus the brew-coach steps you've completed. It flags a possible stall if gravity goes flat too early. See Batches & Fermentation.
Because metabisulfite alone won't reliably stop yeast from restarting on fresh sugar. The two together are what actually stabilise a still mead. (Sparkling/bottle-conditioned recipes deliberately skip stabilising so they can carbonate.)
Yes — the recipe scale slider rescales ingredients, nutrient counts and costs live, with a metric / US / imperial readout. Everything is stored metric internally.
See Troubleshooting, or open an issue on GitHub.
Copyright © 2026 icemanxbe - https://github.com/icemanxbe/MeadOS
Crafted with patience — like mead.
Plan carefully. Brew confidently. Age beautifully.
Getting going
Using MeadOS
- Recipes & Designer
- Batches & Fermentation
- Brewing Tools
- Formulas & Methods
- Libraries
- Cellar & Inventory
- Labels, Sharing & Calendar
Running it well
Help