Mobile-first beekeeping management app for tracking hives, inspections, queen records, and equipment with streamlined data entry optimized for field use.
License: MIT. Built with: TypeScript, Nix, PLpgSQL, CSS, Shell, HTML, JavaScript, Dockerfile. Website: https://hivepal.app. Source: https://github.com/martinhrvn/hive-pal.
services: app: image: ghcr.io/martinhrvn/hive-pal:latest ports: - '80:3000' environment: NODE_ENV: production DATABASE_URL: postgres://postgres:postgres@postgres:5432/beekeeper ADMIN_EMAIL: [email protected] ADMIN_PASSWORD: changeme123 FRONTEND_URL: https://yourdomain.com STORAGE_TYPE: local # use 'local' for filesystem or 's3' for S3-compatible storage volumes: - uploads:/data/uploads depends_on: postgres: condition: service_healthy postgres: image: postgres:14 environment: POSTGRES_USER: postgres POSTGRES_PASSWORD: postgres POSTGRES_DB: beekeeper volumes: - postgres_data:/var/lib/postgresql/data healthcheck: test: ['CMD-SHELL', 'pg_isready -U postgres -d beekeeper'] interval: 10s timeout: 5s retries: 5 volumes: postgres_data: uploads:
Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.
Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through Hive-Pal. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.
Last verified: 2026-05-22