HortusFox

Self-hosted plant tracking and collaborative journaling, honestly reviewed. No marketing fluff, just what you get when you run it yourself.

TL;DR

• What it is: Open-source (MIT) self-hosted plant management and tracking system — think a collaborative garden journal plus a task manager, all on your own server [README][5].
• Who it’s for: Plant enthusiasts, households with multiple people sharing plant care duties, and privacy-conscious users who don’t want a subscription app tracking their horticultural habits [5][website].
• Cost savings: Competing plant care apps (Planta, Greg, PictureThis) run on annual subscription models ranging roughly $25–$40/year. HortusFox self-hosted costs the price of a VPS or runs on a home NAS for free. Managed hosting via Elestio starts at $14/mo if you don’t want to maintain it yourself [4].
• Key strength: Surprisingly complete feature set for a niche tool — plant tracking, task scheduling, inventory, weather, group chat, plant identification, REST API, themes, and backups all in one package [README][2].
• Key weakness: No native mobile app, built in PHP on MariaDB which limits modern deployment flexibility, and the community is small with no third-party reviews that go deep into reliability or long-term use [1][5].

---

What is HortusFox

HortusFox is a self-hosted web application for managing your plants. You catalog your plants (with photos, tags, watering schedules, sunlight requirements, notes), assign them to locations in your home, set recurring care tasks, and track history over time. The project describes itself as a “collaborative plant management system,” which means multiple users can share access to the same instance — so you and a partner, roommate, or family member can manage a shared collection without duplicating effort [README][website].

The GitHub description says “self-hosted collaborative plant management and tracking system for plant enthusiasts,” which is accurate and usefully unambitious. This isn’t trying to be anything other than what it is [README][1].

The project is built by a solo developer (Daniel Brendel) in PHP with MariaDB as the database backend. It’s MIT licensed, actively maintained (last commit April 2026), and has been running since 2023 [README][1]. As of this review it sits at 1,382 GitHub stars with 74 forks — a small but real signal of community interest for a tool this specific [1].

What distinguishes it from a spreadsheet or a notes app is the operational scaffolding around plant care: warning indicators for plants that need attention, a tasks system that survives between sessions, weather integration for context, a group chat for coordinating with housemates, and a REST API for integration with other tools. It’s closer to a lightweight CRM for your plant collection than a simple journal [README][2][5].

---

Why people choose it

The XDA Developers review [5] is the most personal account available. The author, Dhruv Bhutani, describes a recognizable problem: caring about plants but losing track of their needs across a collection large enough that memory fails. The turning point wasn’t a feature comparison — it was the combination of a clean dashboard and local data control:

“I’ve tried plenty of plant care apps before, but they always came with limitations or intrusive ads. HortusFox felt refreshingly different.” [5]

The specific wins he cites: setup took under an hour on a home NAS using Docker, the interface had no clutter or onboarding friction, adding plants was “oddly satisfying,” and — critically — the task system made plant care proactive rather than reactive. He went from noticing a drooping leaf to having a schedule that prevented it [5].

The data sovereignty angle matters here in a way it doesn’t for most tools. Plant care apps aren’t processing payment information or medical records, but they do build detailed profiles of your home, your habits, and your schedule. The main alternatives — Planta, Greg, PictureThis — are VC-backed apps where the data model is part of the business model. HortusFox runs on your hardware, and that’s the primary pitch [5][website].

AlternativeTo [1] shows the tool positioned as an alternative to GrowTracker, Snappit, Wildex, StaghornPal, Leaforio, and Ploi — mostly niche plant tracking apps rather than mainstream consumer apps. The 7 likes and minimal comments suggest a small but engaged user base rather than mainstream adoption. That’s appropriate for a tool this specialized.

LinuxLinks [2] covers the feature set technically without hands-on assessment, which is typical for that publication. What’s notable is their inclusion of it in a roundup of self-hosted tools at all — it signals the project has passed basic quality thresholds in the self-hosting community.

---

Features: what it actually does

Based on the README, website, and first-hand accounts:

Core plant management:

• Add plants with name, preview photo, tags, notes, gallery photos, watering frequency, sunlight needs, fertilizer preferences [README][5]
• Assign plants to custom home locations (living room, balcony, greenhouse, etc.) [README][2]
• Visual dashboard showing which plants need attention, with a warning system for overdue care [README][5]
• History log tracking all actions taken by all users [README][2]
• Search across the instance’s database [README][2]
• Plant identification feature — identify species from photos [README][2]
• Growth tracking with notes and progress photos over time [5]

Task and scheduling system:

• Tasks system for scheduling care activities (watering, pruning, repotting, fertilizing) [README][2]
• Calendar system for upcoming dates and appointments [README][2]
• Reminders [README][website]
• Mark tasks complete, snooze if needed [5]

Collaboration and communication:

• Multi-user support with authentication [README][website]
• Collaborative group chat for coordinating with housemates, partners, or family [README][2][5]
• Admin dashboard for managing the instance and users [README][2]

Inventory and logistics:

• Inventory system for tracking gardening supplies, tools, and materials [README][2]
• Weather feature with forecasts based on your location, useful for adjusting care schedules [README][2]

Technical and platform:

• REST API [README][website]
• Themes for UI customization [README][website]
• Backup and restore [README][website]
• Plugin system [merged profile]
• Docker and Docker Compose deployment [README][4]
• Automated installer option for non-Docker setups [README]
• Available in 10+ languages: Danish, German, English, Spanish, French, Dutch, Norwegian, Polish, Brazilian Portuguese, Russian [website]
• Mobile-ready (responsive design, not a native app) [website]

One thing conspicuously absent: a native mobile app. The website says “ready for both mobile and desktop,” which means it’s responsive in a browser — not the same as a dedicated app with push notifications [website]. For a plant care tool where the primary interaction might be standing in front of a plant with your phone, this is a real gap.

---

Pricing: SaaS vs self-hosted math

HortusFox itself: $0. MIT license, no feature gating, no tiers [README].

Managed hosting via Elestio: Starting at $14/month. Includes automated backups, SSL certificates, monitoring, alerts, custom domains, and automatic updates. This removes all infrastructure maintenance [4].

Official HortusFox Hosting: The project also offers its own managed hosting service at https://www.hortusfox.com/hosting — pricing not published on the homepage at time of scrape. Presumably in a similar range to Elestio [website].

Self-hosted on your own VPS:

• Software: $0
• A $5–10/month VPS (Hetzner, Contabo, DigitalOcean) is sufficient for a single household — this is a low-traffic PHP app with a small database
• Your time to set up Docker and maintain it

Competing subscription plant apps: Consumer plant care apps like Planta, Greg, and PictureThis operate on freemium models with premium subscriptions. Specific current pricing is not available in the source materials for this review, but these are commercial apps funded by subscriptions and/or in-app purchases — the pricing structure is fundamentally different from a self-hosted tool with a $0 license fee.

The honest math: if you’re already comfortable self-hosting (running a NAS, a home server, or a cheap VPS for other things), HortusFox adds near-zero marginal cost. If you’d be self-hosting specifically for this tool, the comparison shifts — $14/mo managed hosting vs. the free tier of a consumer app is less compelling for a niche personal use case. The value case is clearest for households already running a homelab or self-hosted stack where adding one more Docker container costs essentially nothing.

---

Deployment reality check

The XDA review [5] provides the most useful ground truth here: setup on a home NAS using Docker took under an hour, even for someone who doesn’t do this every day. That’s a reasonable signal that the Docker path is genuinely approachable.

What you actually need:

• A Linux machine, NAS, or VPS with Docker and Docker Compose installed
• About 1–2GB RAM for a household-scale instance
• MariaDB/MySQL (bundled in the default Docker Compose setup)
• A reverse proxy (Caddy or nginx) and domain name if you want HTTPS access from outside your home network
• Basic ability to edit a docker-compose.yml to set admin credentials and timezone — the README walks through this explicitly [README]

The install path:

1. Clone the repository
2. Set environment variables in docker-compose.yml (admin email/password, timezone, database passwords)
3. Run docker compose up
4. Optional: configure cron jobs for reminders and weather updates [README]

What can go sideways:

• The weather feature requires an external API for forecasts — you’ll need to configure an external service key separately [README][2]
• Plant identification similarly depends on external services (plant identification APIs) [README][2]
• No documented update path in the third-party reviews, though the Docker setup presumably supports docker compose pull && docker compose up like most containerized apps
• The tech stack is PHP + MariaDB, which is serviceable but not what most modern self-hosters are optimizing for. If your homelab runs primarily Node/Go/Rust services, this adds a different runtime to maintain [README]
• Cron jobs for reminders and notifications require separate configuration outside Docker — the README lists this as a distinct setup step [README]

Realistic time estimate: For a technically comfortable user with Docker already installed: 30–60 minutes to a working instance. For someone new to self-hosting following the guide: 2–4 hours including domain setup. The XDA reviewer’s “under an hour” tracks with a NAS setup where Docker is already configured [5].

One useful option: the project offers a live demo at https://www.hortusfox.com/demo so you can evaluate the interface before committing to setup [website].

---

Pros and cons

Pros

• MIT licensed, genuinely free. No feature gating, no commercial license needed for any part of the functionality. You can run it, fork it, or embed it without legal overhead [README][1].
• Surprisingly complete feature set for a niche tool. Most plant trackers do plant tracking. HortusFox adds tasks, inventory, calendar, weather, group chat, history logging, plant identification, REST API, themes, and backups — more operational depth than you’d expect [README][2].
• Genuinely collaborative. Multi-user with shared state, group chat, and history log designed for households rather than solo use. If more than one person cares for your plants, this is a real differentiator [README][5][website].
• Data stays on your hardware. No third-party servers receiving your home layout, schedules, and plant photos [5][website].
• Docker deployment works. The XDA reviewer deployed it on a NAS in under an hour without issue [5].
• Active maintenance. Last commit April 2026, v5.7 released, developer responsive enough that the project has stayed current for three-plus years [README][1].
• Multilingual. 10+ languages including non-English European languages — useful for households where English isn’t the primary language [website].
• Managed hosting option exists. Elestio at $14/mo removes all self-hosting friction if that’s the trade-off you want to make [4].

Cons

• No native mobile app. Responsive web interface is not the same as a native app with push notifications. For a tool where primary use is standing next to a plant with your phone, this is a real limitation [website][5].
• Solo developer project. Built and maintained by one person (Daniel Brendel). No team, no company, no commercial entity backing it. This is fine until it isn’t — project continuity risk is real [README][1].
• Small community. 1,382 stars and 74 forks [1]. No Stack Overflow presence, no Reddit megathreads, no ecosystem of third-party guides. If you hit an unusual problem, your options are the GitHub issues (31 open as of this writing) and the Discord [1][README].
• PHP + MariaDB stack. Works, but adds a different runtime to a homelab that might be optimized for other stacks. Not a dealbreaker, but worth noting [README].
• External services for key features. Weather forecasts and plant identification both depend on third-party APIs — the “self-hosted” story has asterisks [README][2].
• No third-party deep-dive reviews. Beyond the XDA piece [5] and LinuxLinks [2], there’s essentially no independent long-term assessment of reliability, performance, or upgrade behavior. The XDA review is from June 2025 — a few months of use. No multi-year retrospective exists.
• Niche use case limits the community pool. HortusFox lives in a narrow category. Fewer users means fewer bug reports found and fixed, fewer plugins, fewer how-to guides.

---

Who should use this / who shouldn’t

Use HortusFox if:

• You have more than a handful of plants and you’ve lost track of their care schedules — the dashboard and task system directly solve this [5].
• Multiple people in your household share plant care duties and need a shared source of truth [README][website].
• You’re already running a homelab or NAS and can add a Docker container at near-zero marginal cost.
• You object to your plant photos, home layout, and daily routines being stored on commercial servers [5][website].
• You want a live demo before committing — the project offers one at https://www.hortusfox.com/demo [website].

Skip it if:

• You want a native mobile app with push notifications. The responsive web interface won’t scratch that itch.
• You’re new to self-hosting and would be setting up a server specifically for this tool — the overhead probably doesn’t justify a personal plant tracker.
• Your plant collection is small (under 10 plants) and a phone reminder or a sticky note does the job.
• You need commercial support guarantees or contractual uptime. Solo developer projects don’t offer SLAs.

Consider managed hosting (Elestio or HortusFox Hosting) if:

• You want the functionality without the infrastructure work — $14/mo from Elestio [4] handles setup, updates, backups, and monitoring.
• You’ve tried self-hosting before and found maintenance friction annoying over time.

---

Alternatives worth considering

From the AlternativeTo page [1] and general knowledge of the category:

• Pl@ntNet — Free mobile app focused on plant identification using community-driven AI. Excellent identification, no tracking or task management. Not self-hosted.
• PictureThis — Consumer plant identification and care app, subscription-based, polished mobile experience. Better identification than HortusFox’s external API approach. Closed source, commercial.
• Greg — Freemium plant care app, watering reminders, care schedules. Mobile-first. No self-hosted option, subscription for full features.
• GrowTracker — Cited as an alternative on AlternativeTo [1]. Android-focused plant tracking app. Narrower scope than HortusFox.
• Leaforio — Listed as an alternative on AlternativeTo [1]. Limited public information available.
• Spreadsheet + calendar — Genuinely competitive for small collections. Free, requires no setup, works everywhere. Loses on photos, history tracking, and multi-user state.

The honest competitive set for HortusFox is consumer mobile apps (Planta, Greg, PictureThis) on one side and a personal spreadsheet on the other. It beats the consumer apps on privacy and the spreadsheet on operational depth. It loses to both on mobile experience.

---

Bottom line

HortusFox is a well-executed self-hosted tool for a narrow use case: households with multiple plants, multiple caregivers, and a preference for keeping their data local. The XDA review [5] is the most credible signal — a hands-on user deployed it on a home NAS in under an hour, used it for months, and found it genuinely changed how they managed plant care. That’s a meaningful data point for a tool with minimal third-party coverage.

The limitations are real: no mobile app, solo developer dependency, small community, external API requirements for some headline features. If you need push notifications or a polished onboarding experience, the consumer apps are better products. If you’re already self-hosting and want plant management that doesn’t report back to anyone, HortusFox is the only serious option in the self-hosted category.

For a non-technical user who wants this functionality without the infrastructure work, Elestio’s managed deployment at $14/mo [4] is the pragmatic middle path — or upready.dev can deploy it for you as a one-time setup, after which you own the instance and stop paying monthly.

---

Sources

1. AlternativeTo — HortusFox listing (7 likes, 35 alternatives, 1,382 GitHub stars). https://alternativeto.net/software/hortusfox/about/
2. LinuxLinks — “HortusFox: Self-hosted collaborative plant management system for your local environment”. https://www.linuxlinks.com/hortusfox-self-hosted-collaborative-plant-management-system/
3. Launchtory — Collaboration Projects listing (HortusFox 4.0 entry). https://launchtory.com/topics/collaboration
4. Elestio — “Managed HortusFox as a Service” (starting at $14/mo). https://elest.io/open-source/hortusfox
5. Dhruv Bhutani, XDA Developers — “This self-hosted app helped me stop killing my houseplants” (Jun 12, 2025). https://www.xda-developers.com/this-self-hosted-app-helped-me-stop-killing-my-houseplants/

Primary sources:

• GitHub repository and README: https://github.com/danielbrendel/hortusfox-web (1,382 stars, MIT license, maintained by Daniel Brendel)
• Official website: https://www.hortusfox.com
• Documentation: https://hortusfox.github.io/
• Live demo: https://www.hortusfox.com/demo