Cookies ahead

Our support chat tool "Intercom" would like to collect some more data on you. See the related link for more details.

Docs

GitHub Actions runners

🏃

CI with better cardio.

External GitHub Actions runner providers offer faster builds and more flexible billing than GitHub-hosted runners.

GitHub Actions are not always the best fit. Builds can be slow and costs high compared to alternative solutions. Managed runner providers and self-hosted runner platforms fill that gap. They usually offer a GitHub-compatible runner, better hardware choices, and more flexible or affordable billing. In many cases, moving over is a small workflow change instead of a full CI migration.

Most commercial providers listed here behave as drop-in replacement for GitHub-hosted runners. Others focus on running runners inside your own cloud account or data center. The second model can be attractive when data locality, network access, or custom hardware matters more than convenience. A fully managed service is easier to adopt, while a bring-your-own-cloud setup usually gives you more control and more responsibility.

Relation to fortrabbit

For most use cases, no external CI service is required when building deployment pipelines with fortrabbit, because fortrabbit includes a built-in Git-based deployment service. Connect your GitHub repository and fortrabbit handles deployments automatically after each git push. For additional details, see the deployment intro.

In certain edge cases, you may require more control or specific tooling that is not available with fortrabbit. This is where you can consider using GitHub Actions directly, or a third party service (what this is about).

There is no platform-level integration required on the fortrabbit side to connect a GitHub Runner. These services run your CI jobs on external infrastructure. The final deployment step still happens over SSH, for example with rsync or another SSH-based workflow. Integrate the service with a deploy key - a special SSH key to connect external services.

Self-hosted DIY solutions

The most cost-effective approach is to run GitHub Actions on your own dedicated server or VPS by setting it up as a self-hosted runner. This gives you complete control over the hardware and environment while eliminating the per-minute costs of managed runner services.

Written by a human. Review, grammar checks and typo fixes by AI.

AI use & editorial processEdit on GitHub ↗