Your region. Our ops. Zero maintenance.
Single-tenant WarpBuild infrastructure deployed in your preferred AWS or GCP region. Private networking. Zero egress. Zero maintenance.
How it works
We provision dedicated infrastructure in your chosen region. You configure VPC peering to your existing infrastructure. Runners access your internal services directly - no public internet, no egress fees, no hassle.
Why Dedicated Cloud?
The security of self-hosted. The simplicity of managed. The best of both.
Zero Egress Costs
Deploy in the same region as your infrastructure. Artifacts, dependencies, and data stay local.
- Same-region deployment with your services
- S3/GCS buckets accessible without egress
- ECR/GAR pulls without cross-region fees
- Typical savings: $10k-100k/month
Zero Operation Overhead
WarpBuild manages everything. Patching, scaling, monitoring. You just run jobs.
- Fully managed by WarpBuild
- Automatic security patching
- 24/7 monitoring and alerting
- Capacity planning handled
Private Networking
VPC peering and PrivateLink. Your network, your rules.
- VPC peering to your infrastructure
- PrivateLink for AWS services
- Security group integration
Simplified IAM
No cross-account trust policies. Runners assume roles in your existing AWS/GCP accounts seamlessly.
- Direct IAM role assumption
- No complex trust relationships
- Works with your existing policies
Dedicated Cloud vs alternatives
Self-hosted (ARC)
- •Kubernetes expertise required
- •Security patching burden
- •Scaling complexity
- •On-call overhead
BYOC
- •You manage cloud costs
- •IAM setup complexity
- •Some ops overhead
- •Multi-account management
Dedicated Cloud
- Zero ops burden
- Simple IAM integration
- Predictable pricing
- WarpBuild manages all
Technical specifications
Compute
- Instance types
- All x86-64 and arm64
- High-performance caching
- Enabled
- Instant Job Start
- <10s
- Concurrency
- Unlimited
Networking
- VPC peering
- Supported
- PrivateLink
- AWS supported
- Custom rules
- Full traffic control
- Egress
- Your region, no costs
Storage & Cache
- Cache backend
- S3/GCS in your region
- Artifact storage
- Configurable
- Warm pools
- Included
- Snapshots
- Available
Security
- Ephemeral runners
- No code access
- Zero data retention
- Supported
- SSO/SCIM
- Included
- SOC2 Type II
- Certified
Available regions
Deploy where your infrastructure lives. Any AWS or GCP region.
AWS
GCP
Predictable pricing
Volume-based pricing with committed use discounts. No surprise cloud bills - we handle the infrastructure costs. You pay one predictable fee.
FAQ
GitHub-Hosted vs Self-Hosted Runners
GitHub operates GitHub-hosted runners. With self-hosted runners, you or a managed provider supply the machines registered with GitHub. WarpBuild uses this integration while managing the runner fleet, so workflows remain on GitHub Actions.
How does WarpBuild isolate runner workloads?
Each ordinary runner runs in its own ephemeral virtual machine, created on demand and destroyed after the build. Its dedicated encrypted storage volume is destroyed too. Deliberately persisted caches and snapshots have separate lifecycle rules.
Can GitHub Actions Runners Run in My Own Cloud Account?
Yes. WarpBuild BYOC runs your GitHub Actions runners as ordinary virtual machines inside your own AWS account, GCP project, or Azure subscription, so your cloud provider bills the compute directly and WarpBuild charges $0.002 per runner minute on top.
Where can I request WarpBuild’s SOC 2 report?
Request security documentation through the WarpBuild Trust Center. The security page identifies SOC 2 Type 2 coverage for Security, Availability, and Confidentiality; review the report scope against your own requirements.