About · open source

A platform you can own, read and change

Falak started from a simple frustration: the best deploy experiences lived on other people’s clouds, and self-hosting meant gluing five tools together. Falak puts that experience on your own servers.

Why

Principles

  • Your infrastructure, your data

    Apps, databases, secrets and telemetry stay on machines you control. Falak never needs to be reachable from anywhere but your servers and your team.

  • Calm by default

    A Railway-style canvas, one primary action per screen, live status without refreshing, and destructive actions that ask you to type the name.

  • Small moving parts

    One Go agent per server instead of five daemons; one Compose stack for the control plane; updates that roll themselves back.

  • Honest about limits

    Known limits are written down in the repository, and our comparison pages say where other tools are better.

The repository

What’s inside

One repository, several parts, clear contracts between them.

Architecture: you use the browser, the falak CLI or the REST API against one Falak host (edge, control plane, agent API, queues, Postgres, Valkey, builder, and an optional Loki, Tempo, VictoriaMetrics and Grafana stack). Each managed server runs falak-agent, which dials out to the Falak host over mTLS for commands and sends logs, metrics and traces over OTLP.

Get involved

Try the local simulation (make up, then make e2e-deploy), report bugs, suggest features or send a pull request.

Your servers are waiting.

One command installs Falak on a fresh Ubuntu or Debian host. Connect servers, push code, watch it go live.

curl -fsSL https://falak.sh/install.sh | sudo bash -s -- --domain falak.example.com --email you@example.com