Skip to main content
Filament runs two ways depending on whether you want it inside your own Go process or as a standalone service.

As a library

Filament embeds directly. Connectors self-register via blank imports, so you only pull in the ones you use:
See Embedding as a library for the full picture.

As a service, on Kubernetes

Filament runs on Kubernetes through the Helm chart. The chart deploys the server and control plane, dispatches each run as its own Job, and can provision or point at existing Postgres and NATS instances. See Kubernetes for the install steps.
Evaluating locally first? Quickstart runs the whole stack with just dev and no Kubernetes required.