Moving from Concourse, without rewriting your pipelines.
Automeer takes everything Concourse got right, declarative pipelines, container-native execution and no snowflake build environments. And fixes everything it got wrong.
What actually has to change
An honest inventory. Most of a Concourse estate moves as-is; the parts that do not are listed here rather than discovered later.
Carries over unchanged
- Pipeline YAML. It is standard Concourse configuration. The same files you set today, set here.
- Custom resource types. Automeer implements the full Concourse resource interface, so your existing resources run without modification.
Needs editing
- Credentials. Static credentials become references. Pipelines authenticate to your APIs through OAuth 2.0 rather than carrying secrets.
- Worker assumptions. Anything that pins work to a named worker, or tunes worker counts, comes out. Concurrency becomes a pricing decision instead of an infrastructure one.
Not supported yet
- Self-hosting. Managed only for now; enterprise self-hosting is on the roadmap.
- Pluggable notifications. Planned, and until it lands you keep scripting them.
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.
Dynamic Pipeline Generation
Pipelines will be generated programmatically. Keep configurations consistent across every repository and team without copying YAML by hand.
↳ Will replace the multi-pipeline PR workaround
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
Webhook-Driven Pipelines
Real webhook payload integration, not just a polling trigger.
↳ Builds triggered through webhooks receive the payload and can be used to create real-time, responsive workflows.
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.
OAuth 2.0 & Secret Zero
Built-in OAuth 2.0 authentication and authenticating pipelines directly to the API's you use. Security-first, from the ground up. Not bolted on.
↳ No need for static credentials
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.
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 conditional logic through if_var & match steps |
| Pull request / branch builds | Separate pipeline per PR | Native webhook-driven builds |
| Dynamic pipeline generation | Not supported | In progress |
| 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 (planned) |
| Community size | Established | Growing, but with active support |
| Documentation | Gaps in advanced topics | Comprehensive from day one |
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.
- 01 Steep learning curveFully declarative pipelines are powerful, but Concourse made them unnecessarily hard to learn. Better docs and tooling make all the difference.
- 02 A UI stuck in the pastNo back button, no deep history, no discoverability. We're launching with a very similar UI, we get it. A modern, discoverable UI is on our roadmap.
- 03 No real conditional logicBranching pipelines, complex triggers and conditional steps. All workarounds! It shouldn't be that hard.
- 04 Monolithic pipeline configsAs teams grow, pipeline YAML becomes a maintenance nightmare. No native way to keep things consistent across repos.
- 05 Self-hosting everythingManaging workers, servers, and container infrastructure on top of your actual work is a tax you shouldn't have to pay.
- 06 No native PR/branch buildsBuilding separate pipelines per PR is 2015 thinking. Modern CI should handle this out of the box.
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 is on the roadmap
# Looks familiar, works better.
webhooks:
- name: my-webhook
jobs:
- name: triggered-by-webhook
# First-class support for triggering via webhooks
webhooks: [my-webhook]
plan:
# Conditional logic built in
- if_var: ((.webhooks:my-webhook))
when_exists:
do: [...]
when_missing:
do: [...]
Ready to leave the workarounds behind?
Join teams migrating from Concourse.
Thanks. We will be in touch.
Something went wrong. Please try again.
We respect your privacy. No spam, ever.