BYOC (Bring Your Own Cloud)

Source

View original documentation

BYOC (Bring Your Own Cloud) allows you to deploy E2B sandboxes to your own cloud infrastructure within your VPC.

Availability:

• Currently only available for AWS
• Working on Google Cloud and Azure support
• Enterprise customers only
• Contact: enterprise@e2b.dev or book at https://e2b.dev/contact

Architecture

Data Flow:

• Sandbox templates, snapshots, and runtime logs stored within customer's BYOC VPC
• Anonymized system metrics (cluster memory/CPU) sent to E2B Cloud for observability
• All sensitive traffic (template builds, sandbox traffic, logs) goes directly from client to BYOC VPC
• Never touches E2B Cloud infrastructure

Glossary:

• BYOC VPC: Customer's Virtual Private Network (e.g., AWS account)
• E2B Cloud: Managed service providing E2B platform, observability, cluster management
• OAuth Provider: Customer-managed service providing access to cluster

BYOC Cluster Components

Orchestrator:

• Manages sandboxes and their lifecycle
• Optionally runs template builder component

Edge Controller:

• Routes traffic to sandboxes
• Exposes API for cluster management
• gRPC proxy for E2B control plane communication with orchestrators

Monitoring:

• Collects sandbox/build logs and system metrics
• Only anonymized metrics sent to E2B Cloud for observability

Storage:

• Persistent storage for sandbox templates, snapshots, runtime logs
• Container repository for template images

Onboarding Process

1. Customer reaches out to E2B
2. Customer provides dedicated AWS account and region
3. E2B receives IAM role for managing account resources
4. AWS account quota limits may need increase
5. Terraform configuration and machine images used for provisioning
6. New team created under customer's E2B account
7. SDK/CLI works same as E2B Cloud

FAQ

How is cluster monitored?

• Forwards anonymized metrics (cpu/memory) to E2B Control Plane
• Advanced observability and alerting
• No sensitive information

Can cluster auto-scale?

• Horizontal scaling: add more orchestrators and edge controllers
• V1 autoscaler cannot auto-scale orchestrator nodes (needed for sandbox spawning)
• Feature coming in next versions

Are sandboxes accessible only from private network?

• Yes, load balancer can be configured as internal
• VPC peering with customer's VPC possible
• Sandbox traffic stays in private network

How is control plane communication secured?

• TLS encryption between E2B Cloud and BYOC VPC
• VPC peering available for direct communication
• Load balancer can be private without public IP