Self-host Air Pipe as a single binary — or let us run it.

One compiled binary, no sidecars and no agents. Run it on your VM, your container platform or your laptop — the same config you'd deploy to our managed cloud, on infrastructure you control.

Why self-host

Because the data can't leave, or because you'd rather own the runtime. Your databases, your documents and your embeddings stay on your own network, and the config that describes them is a file in your repository.

Install where you already deploy

Linux, macOS, Windows or a container. Linux is the recommended production target. Binaries are published for each platform — install it, point it at a config, and it serves.

Same config, either way

Self-hosted and managed run the same declarative config, so moving between them is a deployment decision rather than a rewrite. Observability behaves identically: OpenAPI, Prometheus metrics and OpenTelemetry traces are generated either way.

What self-hosting still needs

Self-hosted mode is not disconnected by default: you register an account and generate an API key, and the binary uses it. Request units are metered separately from managed ones, with their own monthly free allowance. Air-gapped deployment is an Enterprise arrangement — talk to us rather than assuming it.

Frequently asked questions