Self-hosting

• DC

  I already run Docker Compose

  available in 0.1.0Matches your answers

  Use the Compose file and env template the installer writes. Postgres, the HTTPS proxy and the in-app updater are Compose profiles you can leave out.

  $ git clone --depth 1 https://github.com/bemmoly/bemmoly$ cd bemmoly/deploy/compose && cp env.template .env$ docker compose up -d

  Fill in .env before the last command: the version, your domain, the profiles to run and the generated secrets.

  The Compose file and env template ↗
• K8

  I run Kubernetes

  plannedMatches your answers

  A Helm chart runs the same image as one Deployment, or as separate api and worker Deployments. It connects to your Postgres instead of running one.

  $ helm install bemmoly ./deploy/helm/bemmoly \ --set publicUrl=https://work.example.com

  Bring Postgres 18 with pgvector, and keep DATABASE_URL and the secret key in a Secret named bemmoly. The chart in the repository is a starting point, not a release yet.

• TF

  I want managed infrastructure

  plannedMatches your answers

  Terraform modules for AWS, GCP and Hetzner will create the VM, with a managed Postgres on AWS and GCP, and run the installer through cloud-init.

  Until they ship, create the VM in your provider’s console and use the one command above.

• AG

  My servers have no internet

  built, untested offlineMatches your answers

  Each release has a bundle with the four images, the installer, the Compose file and checksums. Copy it to the machine; Docker must already be installed there.

  $ tar -xzf bemmoly-airgap-0.1.0-amd64.tar.gz$ cd bemmoly-airgap-0.1.0-amd64$ sudo sh install.sh --version 0.1.0 \ --image-archive images.tar --domain bemmoly.internal

  Later updates: upload the next bundle on the Updates page. For AI, point Bemmoly at a model server on the same network.

• PG

  I have my own Postgres

  available in 0.1.0Matches your answers

  One flag on any path, and the bundled database is left out. With Compose, set DATABASE_URL in .env and drop db from COMPOSE_PROFILES; on Kubernetes it goes in the Secret.

  $ curl -fsSL https://get.bemmoly.com | sh -s -- \ --database-url postgres://bemmoly:[email protected]:5432/bemmoly_db

  Postgres 18 is required; 17 is accepted with a warning. Without the pgvector extension everything works except semantic search, and the health page says so.

What you get, on every path

• ✓Automatic HTTPSCertificates are requested and renewed for you.
• ✓Nightly backupsKept 7 days, 4 weeks and 3 months, and verified.
• ✓One-command upgrades and rollbackA failed health check rolls back on its own; you can roll back for 7 days.
• ✓In-app updaterRelease notes, then one click to update.
• ✓All modulesEvery module ships in the one image. Turn on what you use.

Two differences: with --no-proxy you bring your own HTTPS, and on Kubernetes the Updates page gives you thehelm upgrade command instead of updating in place. On every path, keep a copy of /var/bemmoly/.env somewhere safe: it holds the key that decrypts stored credentials, and backups do not contain it.

1. 1

   Open the URL and create the first admin

   The first visit runs a short setup: the server’s health checks, then the account that owns the workspace.

   
2. 2

   Invite your team

   Paste email addresses, pick a role and a team, and Bemmoly sends the invitations through your mail server.

   
3. 3

   Connect AI if you want

   Bemmoly works fully without AI. Connect your own provider or a model on your network, or skip it; nothing is sent anywhere until you do.