The world needs a way off GitHub Actions. For the past three weeks, we’ve been building an open-source compatibility layer that runs Actions workflows natively on @buildkite without changing them. Buildkite powers CI for repos where scale is table stakes. Pipelines are dynamically programmable and parallel by default, with every job running in its own environment. Test suites that take hours - or days - on other tools can fan out and finish in minutes. Actions uses a different model: static workflows, with sequential steps sharing a mutable workspace. We now transparently compile that model into our Buildkite pipelines, so teams can keep their existing workflows and actions while gaining Buildkite’s speed at scale, control and reliability. It’s early and there are rough edges, but it's already proving useful across our design partners. If you want to start shifting workloads, give it a go: