About FlareRunner
FlareRunner is built entirely on Cloudflare infrastructure. It brings managed compute to GitHub Actions while keeping runner operations out of repository workflow files.
Why we are building it
Self-hosted runners give teams control, but they also create infrastructure to patch, secure, scale, and troubleshoot. FlareRunner absorbs that work on Cloudflare, so repository workflows describe what to run—not how to operate a runner fleet.
How it fits
GitHub continues to define workflows and permissions. FlareRunner supplies fresh Linux runners, live and retained logs, usage details, and clear controls for compatible jobs. Our goal is for FlareRunner to become the fast, complete interface you use to monitor and troubleshoot every run.
What matters to us
We are designing for secure isolation, predictable cost, useful failure messages, and a migration that teams can review before changing anything.
Where the product is today
FlareRunner is being built as a focused private preview for small engineering teams running Linux CI in private GitHub repositories. The FAQ covers the current product boundaries in more detail.
How to contact us
Email hello@flarerunner.com, or use the Feedback button while signed in to FlareRunner.
About Jon Stevens
Jon has been on the internet since 1991 and has spent more than 30 years building companies and developer solutions. Earlier in his career, he co-founded the Java effort at the Apache Software Foundation and helped open-source Apache Tomcat. His work has focused on making complex infrastructure fast, understandable, and dependable for the people using it.
Jon founded FlareRunner after seeing a gap for reliable GitHub Actions runners built entirely on Cloudflare infrastructure. He also wanted the interface around those jobs to be exceptional: real-time, ultra-fast, and optimized for following live and retained logs.