Latchyard Get notified

Every feature on your own servers

Self-hosted Latchyard runs the same binary, UI and login code as Cloud. The two differ only in configuration, so no feature is held back for hosted customers.

There is no release yet. The install guide arrives with the first release. Get notified when it ships.

Three ways to install, in order of support

  1. Primary docker compose The app, a separate runner for user code, PostgreSQL, a migration job and a backup service. Optional profiles add a Caddy proxy, extra workers, observability and error tracking.
  2. Second Single binary The latchyard binary with latchyard-runner next to it, under systemd, pointed at your PostgreSQL.
  3. Third Helm chart One Helm chart for Kubernetes. There is no Kubernetes operator.

Small enough for one small server

  • 1 vCPU and 1 GB The default compose stack, with the app, an idle runner supervisor, PostgreSQL and the backup service, fits in 1 vCPU and 1 GB. CI measures it. With the Python tier enabled it needs more.
  • PostgreSQL is the only database No Redis, Kafka, NATS or ClickHouse to run beside it.
  • Backups built in latchyard backup, restore, doctor and upgrade --check ship with the binary. The master key is backed up separately from the data, and backup refuses to write it to its own target.
  • One node The first release has no self-hosted high availability. With WAL archiving to an off-host target, the recovery point is about 2 minutes of commits.

You decide what leaves your server

  • Telemetry is opt-in The onboarding wizard asks, and nothing is sent until the admin answers. DO_NOT_TRACK=1 is honoured, and latchyard telemetry preview prints the exact next payload.
  • A signed security-notice feed Your instance pulls a signed feed of releases and advisories from latchyard.com. It works with telemetry off.
  • Notices, never automatic updates A new release or advisory shows an admin banner and emails the instance admins. A self-hosted instance never installs an update by itself.
  • Five years of security fixes The declared support period is five years. Fixes ship in the latest release, and upgrading is free and needs no costly change to your environment.

Get notified when the first release ships

Leave your address and we email you when the first release is out.