Rannable.io

Effortless Self-Hosted GitHub Runners.

Simple, secure, and scalable solutions for automated build servers.

Hassle-Free Maintenance ━ Forget the headache of keeping build servers up-to-date. We manage it all for you, ensuring each server is equipped with the latest security patches and releases.
Just-In-Time Runners ━ Our runners are instantiated only when needed and disposed of after a single use. This maximizes security and minimizes issues related to long-running jobs such as disk space and permission conflicts.
Scalable Solutions ━ Automatically scales with your demands, ensuring you have the build resources as and when you need them.
#_

Build to enhance your experience.

Features.

ARM Compatibility

Full support for deploying ARM instances, broadening your deployment capabilities.

Standby Servers

Maintain high availability with standby servers that are provisioned during peak activity and decommissioned during idle periods.

VM-Management

Automated VM lifecycle handling—from creation at the start of a workflow to removal upon completion. We act as an orchestrator, keeping your images secure and up-to-date.

Cost Optimization

Utilize spot instances to make your build minutes up to 8 times cheaper than standard GitHub instances.

Your Cloud, Your Control

Set up and manage build servers directly within your own cloud environment, giving you complete control.

Ephemeral Machines

Each build server is used only once, enhancing security and reducing maintenance hassles associated with long-term server usage.

Always know what you’ll pay, transparent pricing for everyone.

Light

Start small and scale as you grow.

€19

  • 1 runner configurations
  • Up to 5 concurrent workers
  • ARM based runners
Get started

Medium

Multiple runners for multiple workflows.

€49

  • 3 runner configurations
  • Up to 10 concurrent workers
  • ARM based runners
Get started

Max

For even the biggest enterprise companies.

€99

  • Unlimited runner configurations
  • Unlimited concurrent workers
  • ARM based runners
  • Analytics support
Get started

Frequently asked questions

Answers to commonly asked questions about our platform

At this moment we only support Azure, but new cloud providers will be added shortly. You can always reach out to us on Slack to have the latest status update on this.
We utilize Just in Time runners, ensuring each runner is used only once per job to enhance security and prevent build server issues, while leveraging Azure Spot instances to significantly lower operating costs.
In our testing this works quite good. As Github Workflows are mostly short lived, they have a good fit for Azure Spot Instances. In rare cases the build is not completed because Azure takes the server back. In that case you can restart the build from the Github Actions page, and a new server will spawned to process the job.
We aim to reduce the start-up time of the servers as best as possible. In practice we see an average of 2 minutes delay until your job starts. This can be overcome by the Overprovisioning feature. When activity is detected you can configure a number of servers that are spawned extra to pick up the following jobs that are created. The next jobs that are scheduled are picked up immediately by the stand-by servers, and in the mean while new servers are spawned for the following jobs. If no activity is detected in the last 30 minutes, the extra servers are deleted again.

Intuit Mailchimp