For teams who loved Concourse's principles, not its pain points

CI/CD the way it should have been.

AutoMeer takes everything Concourse got right, declarative pipelines, container-native execution and no snowflake build environments. And fixes everything it got wrong.

Get Early Access See how we compare →

Scroll to explore

What drove you here

We know exactly why you're looking for an alternative.

You didn't give up on Concourse's philosophy. You gave up on the friction. The docs that couldn't keep up, the UI that felt frozen in 2017, the workarounds you shouldn't have needed to build. We built AutoMeer because we felt the same frustration.

Steep learning curveFully declarative pipelines are powerful, but Concourse made them unnecessarily hard to learn. Better docs and tooling make all the difference.

A UI stuck in the pastNo back button, no deep history, no discoverability. A CI tool's UI should help you, not fight you.

No real conditional logicBranching pipelines, complex triggers and conditional steps. All workarounds! It shouldn't be that hard.

Monolithic pipeline configsAs teams grow, pipeline YAML becomes a maintenance nightmare. No native way to keep things consistent across repos.

Self-hosting everythingManaging workers, servers, and container infrastructure on top of your actual work is a tax you shouldn't have to pay.

No native PR/branch buildsBuilding separate pipelines per PR is 2015 thinking. Modern CI should handle this out of the box.

What we've built

Everything you wanted Concourse to become.

AutoMeer is built on the same core principles. Declarative, container-native, no magic, but with first-class support for the workflows that Concourse forced you to hack around.

Solved

Dynamic Pipeline Generation

Generate pipelines programmatically. Keep configurations consistent across every repository and team without copying YAML by hand.

↳ Replaces the multi-pipeline PR workaround

Native

if_var & match Steps

First-class conditional logic built into the pipeline DSL. Branch on variables, match on conditions. No creative abuse of resource versioning required.

↳ if_var, match built into pipeline spec

Built-in

Webhook-Driven Pipelines

Real webhook payload integration, not just a polling trigger. GitHub, GitLab, and custom webhooks drive pipeline behaviour in real time.

↳ PR builds & branch builds natively supported

Coming soon

Pluggable Notifications

Bring your own notifier. The same extensibility model you know from Concourse resources, applied to alerts, so teams can wire up Slack, PagerDuty, or anything else.

Enterprise-ready

OAuth 2.0 & Secret Zero

Built-in OAuth 2.0 authentication and secure Secret Zero bootstrapping. Security-first, from the ground up. Not bolted on.

Compatible

All Existing Concourse Resources Work

Don't throw away your resource library. AutoMeer supports the full Concourse resource interface, your existing custom resources run without modification.

Side by side

Concourse vs AutoMeer

An honest comparison. Where we are ahead, and where we are still catching up.

Feature / Pain Point	Concourse CI	AutoMeer
Declarative pipeline model	✓ Core strength	✓ Same foundation
Conditional pipeline logic	Workarounds needed	Native if_var & match steps
Pull request / branch builds	Separate pipeline per PR	Native webhook-driven builds
Dynamic pipeline generation	Not supported	First-class feature
Webhook payload integration	Polling only	Full payload-driven support
Infrastructure management	Self-host everything	Fully managed (self-hosted on roadmap)
OAuth 2.0 auth	Limited	Built-in
Existing Concourse resources	✓ Full ecosystem	✓ All existing resources supported
Push notifications	Script externally	Pluggable notifier model (coming soon)
Community size	Established	Growing, but with active support
Documentation	Gaps in advanced topics	Comprehensive from day one

Zero ops overhead

Stop managing workers. Start shipping faster.

Concourse made YOU the infrastructure team, whether you wanted to be or not. AutoMeer is fully managed; we run the platform, you run the pipelines.

No worker nodes to provision, patch, or monitor
Automatic scaling for burst workloads
Enterprise self-hosting available for compliance requirements
Your existing S3/Backblaze artifact workflows stay intact

# pipeline.yml — looks familiar, works better

jobs:
  - name: build-and-test
    on: pull_request
    steps:
      - if_var: branch == "main"
        then:
          - task: deploy-prod
        else:
          - task: deploy-staging

# dynamic pipeline — one config, every repo

  - name: generate-pipelines
    trigger: webhook
    set_pipeline: dynamic

↳ No worker config. No server setup. Just ship.

Early access

Ready to leave the workarounds behind?

Join teams migrating from Concourse. We'll help you get your pipelines running from day one.

Thanks! We'll be in touch.

Oops! Something went wrong. Please try again.