Buildjet CI
UnclaimedAccelerate GitHub Actions workflows with faster, more cost-effective managed runners.
Visit WebsitePaidVisit Website
TL;DR - Buildjet CI
- Accelerates GitHub Actions builds by up to 2x.
- Reduces CI/CD costs compared to GitHub-hosted runners.
- Offers a secure, isolated, and configurable runner fleet with AMD64 and ARM options.
Pricing: Paid only
Best for: Enterprises & pros
Pros & Cons
Pros
- Significantly faster build times for GitHub Actions
- Lower operational costs for CI/CD workflows
- Easy integration with existing GitHub Actions setups
- Enhanced security through isolated VMs and data protection measures
- Flexibility to choose specific hardware configurations for different jobs
Cons
- Not yet SOC2 compliant
- Does not offer custom security questionnaire responses without a fee
Key Features
Managed performance runners for GitHub ActionsSupport for AMD64 and ARM architecturesMultiple hardware configurations (2 vCPU to 32 vCPU)One-line configuration change for integrationIsolated VM environment with complete wipe after each jobOne-time token authentication for secure workflow execution20GB free cache storage per repository per weekConfigurable concurrency limits with extensions available
Pricing Plans
2 vCPU / 8 GB RAM (AMD64)
$0.004/min
2 vCPU / 8 GB RAM (ARM)
$0.008/min
4 vCPU / 16 GB RAM (AMD64)
$0.008/min
4 vCPU / 16 GB RAM (ARM)
$0.016/min
8 vCPU / 32 GB RAM (AMD64)
$0.016/min
8 vCPU / 32 GB RAM (ARM)
$0.032/min
16 vCPU / 64 GB RAM (AMD64)
$0.032/min
16 vCPU / 64 GB RAM (ARM)
$0.064/min
32 vCPU / 64 GB RAM (AMD64)
$0.048/min
32 vCPU / 64 GB RAM (ARM)
$0.128/min
About Buildjet CI
By Toolradar Team·
BuildJet provides managed performance runners specifically designed to speed up GitHub Actions workflows. By simply changing one line in a GitHub Actions configuration, users can significantly reduce build times and costs compared to standard GitHub-hosted runners. It offers a secure and isolated environment for CI/CD processes, ensuring data privacy and complete wipe after every job.
This service is ideal for developers, teams, and organizations utilizing GitHub Actions who are looking to optimize their CI/CD pipelines for speed and efficiency. It caters to projects with varying computational demands by offering a range of hardware configurations, including both AMD64 and ARM architectures, allowing users to select the most suitable runner for their specific tasks. BuildJet aims to enhance developer productivity by minimizing wait times for builds and tests.
Reviews
No reviews yet. Be the first to review Buildjet CI!
Best Buildjet CI Alternatives
Top alternatives based on features, pricing, and user needs.
glabFree
A GitLab CLI tool bringing GitLab to your terminal.
Jenkins XFree
Cloud-native CI/CD built on Kubernetes for automated software delivery.
GardenPaid
Accelerate software development by eliminating CI/CD and security wait times with a universal acceleration layer.
NXFreemium
Optimize builds, scale CI, and fix PRs faster with intelligent caching and AI-powered self-healing.
ZeaburFreemium
Your AI DevOps Engineer handling all your infrastructure needs, so you can focus on coding.
Explore More
Buildjet CI FAQ
How does BuildJet achieve faster build times compared to standard GitHub Actions runners?
BuildJet provides managed runners with higher performance hardware configurations, including options for more vCPUs and RAM, and optimized infrastructure. This allows for faster execution of build, test, and deployment jobs, often resulting in up to a 2x speed improvement over GitHub's default 2 vCPU / 8 GB RAM runners.
Can I use BuildJet for both AMD64 and ARM-based projects within my GitHub Actions workflows?
Yes, BuildJet supports both AMD64 and ARM architectures. You can specify the desired runner type in your GitHub Actions workflow YAML file using tags like `buildjet-2vcpu-ubuntu-2204` for AMD64 or `buildjet-2vcpu-ubuntu-2204-arm` for ARM, allowing you to optimize performance for different project requirements.
What happens to my code and secrets on BuildJet runners after a GitHub Actions job completes?
BuildJet ensures data security by completely wiping the virtual machine after every job. Your code and secrets are never saved on BuildJet's servers after a job is completed, and access to servers is strictly controlled and audited.
How does the concurrency limit work, and can I increase it beyond the default for my organization?
By default, accounts have a concurrency limit of 64 AMD vCPUs and 32 ARM vCPUs, representing the total vCPU capacity that can run in parallel across all active runners. If your project requires more concurrent capacity, you can purchase Concurrency Extensions, which add 100 vCPUs to your AMD or ARM capacity for an additional monthly fee.
Is there a way to manage or monitor the 20GB free cache storage provided per repository?
BuildJet automatically manages the 20GB free cache storage per repository per week. When the storage limit is reached, the system automatically clears out the oldest cache entries to make room for new ones. For larger projects requiring more than 20GB, custom solutions for expanded cache storage can be arranged by contacting BuildJet directly.
How does BuildJet integrate with my existing GitHub Actions workflows, and what is the setup process?
Integration is designed to be straightforward. After signing in with your GitHub Account and authorizing BuildJet for your organization, you simply modify the `runs-on` property in your GitHub Actions workflow YAML file to specify a BuildJet runner tag (e.g., `runs-on: buildjet-4vcpu-ubuntu-2204`). No complex installations are required.
Source: buildjet.com