Quick start
Two routes to a running Openbeehive instance you can open in a browser:
Single binary
The simplest way to run Openbeehive on your own machine is the single binary. In the selfhost profile, Openbeehive serves the web app and the API from one process, stores its data in a local SQLite file, and keeps uploaded photos on the filesystem. No Docker, no Postgres, no object store - just one executable.
Docker & Compose
Run Openbeehive as a single container for a self-host setup, or bring up the full cloud stack (Postgres and MinIO) with Docker Compose.
Configuration
Openbeehive is configured entirely through environment variables. This page is the complete reference.
Databases
Openbeehive stores all of its server-side data in a relational database. The backend is database-agnostic: it speaks to a pluggable storage layer and ships drivers for SQLite, PostgreSQL and MySQL. You choose which one to use with two environment variables.
Blob storage
Openbeehive stores your records in a database, but photos and other binary
Authentication
Openbeehive lets you choose how much authentication you need. A solo beekeeper running the single binary at home can skip login entirely. A shared instance can use built-in email/password accounts, passkeys, sign-in through an identity provider, or a combination.
Reverse proxy & TLS
Openbeehive listens on plain HTTP (BEEHIVE_ADDR, :8080 by default). For any deployment other people reach, put a reverse proxy in front that terminates TLS and forwards to the app. This page shows working configurations for Caddy and nginx.
Backups & restore
A few minutes spent setting up backups now will save you a great deal of worry later. This page covers what to back up, how to do it safely, and how to restore when you need to.
Upgrading
Upgrades are simple: replace the binary or pull a new image, restart, and the server brings the database schema up to date on its own.
Demo mode
Demo mode installs a ready-made demo account and tenant so visitors can try