Crow CI
Get started
§ FeaturesCrow CI

Build. Test. Ship. On your own terms.

Crow is a container-native CI/CD server. Pipelines live in your repositories, steps run wherever you put an agent, and nothing leaves your infrastructure unless you send it.

forge types on one server
6
execution backends
6
MB of server memory
<200
databases, SQLite to Postgres
3
§ 01PipelinesDocs →

Every step, in plain sight.

Workflows, steps and live logs side by side. Restart a single workflow, cancel one leg of a matrix, or trigger a run by hand with extra variables.

  • DAG view of how steps depend on each other
  • Manual, cron, push, tag, release and pull request events
  • Deployments limited to a forge team
A Crow pipeline with workflows, steps and the log of the selected step
§ 02MetricsDocs →

Know where the minutes go.

Build times, workflows per agent, busiest repositories. Filter by owner, repository and time range, or build your own chart.

  • Overview, charts and a chart builder
  • Instance-wide view for admins
  • History can outlive removed repositories and orgs
The Crow metrics view with a bar chart of workflows by agent
§ 03AgentsDocs →

Agents you can reason about.

See every agent, its labels, its backend and how much capacity it has left. Pick how work is spread across them.

  • Least-loaded, pack, round-robin or random scheduling
  • Global, org and user agents, plus agents shared by several orgs
  • Autoscaler starts cloud agents only when static ones are busy
The Crow agent list with labels, versions and workflow capacity
§ 04SecretsDocs →

Secrets stay encrypted and where they belong.

Secrets, registry credentials and OAuth tokens are encrypted at rest with Google Tink. Store them per repository, organisation or instance, or read them from an external secret store, and limit each one to the images and events that may see it.

  • Encryption at rest with key rotation
  • Repo, org and global scopes
  • Image and event filters per secret
  • Registry credentials for private images
The repository secrets settings in Crow
§ 05 BackendsPick one per agent

Six backends. One pipeline format.

Run steps in containers, as Kubernetes pods, in a throwaway Windows or macOS VM, or straight on the host. Your YAML stays the same; agent labels decide where a workflow lands.

§ Get startedDocker Compose, Helm, binaries

Ready when your pipelines are.

The quickstart takes you from an empty host to a green pipeline with Docker Compose. Helm charts and plain binaries are there when you outgrow it.