The full Runloop platform, inside your cloud account
Deploy to VPC gives you the complete platform -- devboxes, blueprints, snapshots, benchmarking, Credential Gateway, MCP Hub, and all orchestration services -- running as a single-tenant deployment inside your own cloud account. Your data never traverses networks you do not control. Every resource is provisioned declaratively using Pulumi IaC, and delivery is managed through ArgoCD with cryptographically signed artifacts.
```python
import runloop
# Same SDK, same API -- whether hosted or deployed to your VPC
devbox = runloop.devboxes.create(
blueprint_id="secure-agent-env",
metadata={"deployment": "customer-vpc"}
)
# Your infrastructure, Runloop's platform
job = runloop.benchmark_jobs.create(
name="internal-eval-q1",
scenarios=proprietary_scenarios,
config={"concurrency": 100}
)
``````typescript
import Runloop from 'runloop';
// Same SDK, same API -- whether hosted or deployed to your VPC
const devbox = await runloop.devboxes.create({
blueprintId: 'secure-agent-env',
metadata: { deployment: 'customer-vpc' }
});
// Your infrastructure, Runloop's platform
const job = await runloop.benchmarkJobs.create({
name: 'internal-eval-q1',
scenarios: proprietaryScenarios,
config: { concurrency: 100 }
});
``````bash
# Same CLI, same commands -- whether hosted or deployed to your VPC
runloop devbox create --blueprint secure-agent-env \
--metadata '{"deployment": "customer-vpc"}'
# Run evaluations inside your boundary
runloop benchmark run \
--name "internal-eval-q1" \
--scenarios ./proprietary-scenarios.yaml \
--concurrency 100
```Everything in the hosted platform, inside your boundary
Four infrastructure guarantees from the [Runloop Platform](/product) for enterprise compliance.
Devbox lifecycle, Credential Gateway, MCP Hub, and benchmark orchestration with comparative analysis. The deployment model changes; the platform does not
Pulumi IaC for all cloud resources. ArgoCD for continuous delivery with Cosign/Sigstore signed artifacts. Full state file available for customer review.
Customer-managed encryption keys via KMS. Network egress rules under your control. Audit logs to your SIEM. IAM following your organizational standards.
BenchmarkJobDef templates for repeatable evaluation inside your VPC. Credential Gateway and MCP Hub operate within your network. No other BYOC includes evaluation.
Your code does not change when deployment model does
A VPC deployment exposes the same API surface as the hosted platform. Engineering teams that have built against Runloop's multi-tenant environment can point their SDK at the VPC endpoint and continue operating without code changes or SDK forks. Devbox creation, blueprint management, snapshot operations, benchmark orchestration, Credential Gateway configuration, and MCP Hub setup all use identical API contracts. This matters because deployment model decisions are often made by security and infrastructure teams, not by the engineering teams building on the platform.
Isolation enforced by architecture, not policy
Runloop recommends deploying into an isolated, dedicated cloud account within your existing organizational hierarchy. In an isolated account, there is no network path, no IAM trust, and no resource visibility between the Runloop environment and your production workloads until someone deliberately creates one. For cross-environment connectivity -- when agents need to reach a production database or internal API -- the recommended approach is Private Link to expose a single service as a private endpoint without granting broader network access.
From account provisioning to steady-state operations
Four phases from initial setup to production deployment.
Provision a dedicated cloud account. Create a scoped IAM role (runloop-setup) with CloudFormation, Terraform, or ARM template. Purpose-built for provisioning, designed to be disabled after use.
Execute Pulumi to provision managed Kubernetes, PostgreSQL, object storage, private registry, VPC with private subnets, IAM with workload identity, KMS, and audit logging. Full state file for review.
ArgoCD deploys from signed Helm charts in your private registry. Artifacts built in Runloop CI, signed with Cosign/Sigstore, pushed to your registry. Continuous reconciliation of desired vs. actual state
Review all provisioned resources. Verify IAM, network boundaries, and API action trail. Disable the provisioning role. Steady-state access: K8s RBAC + workload identity only. No standing admin access.
What separates Runloop's BYOC from alternatives
Four capabilities no competing BYOC deployment provides.
Benchmark orchestration, BenchmarkJobDef templates, and comparative analysis -- all within the customer's compliance boundary. No other BYOC ships evaluation.
Runs entirely within the customer's VPC. Real credentials never leave the network boundary. No competing BYOC provides an equivalent credential isolation mechanism.
Many BYOC offerings provide sandboxed environments without integrated capabilities. Runloop deploys the complete stack: devboxes, blueprints, snapshots, orchestration, and security.
VPC deployment questions
Common questions about deploying Runloop inside your cloud boundary.
