Network Access Overview
Each sandbox has:- Outbound access: Can make HTTP/HTTPS requests to external services
- Inbound access: Receives a unique URL for external connections
- Isolated network: Each sandbox has its own network namespace
Outbound Access
By default, sandboxes can make outbound HTTP/HTTPS requests to any external service:- Python
- JavaScript/TypeScript
Common Use Cases
Fetching data from APIs:- Python
- JavaScript/TypeScript
- Python
- JavaScript/TypeScript
Inbound Access
Each sandbox gets a unique URL for inbound requests:- Python
- JavaScript/TypeScript
Hosting Web Services
You can run web servers inside sandboxes and access them via the sandbox URL:- Python
- JavaScript/TypeScript
Network Isolation
Each sandbox has its own isolated network namespace:- Separate network stack: Each sandbox has its own IP address and routing
- No inter-sandbox communication: Sandboxes cannot directly communicate with each other
- Firewall rules: Network policies can restrict access
Network isolation ensures that sandboxes cannot interfere with each other or access unauthorized resources.
Network Configuration
Default Configuration
By default, sandboxes have:- ✅ Outbound HTTP/HTTPS access enabled
- ✅ Inbound access via unique URL
- ❌ No inter-sandbox communication
- ❌ No direct IP access
Internet Access Control
You can control internet access when creating sandboxes:- Python
- JavaScript/TypeScript
Security Considerations
Outbound Requests
Outbound Requests
- All outbound requests are logged for security monitoring
- Rate limiting applies to prevent abuse
- Malicious requests are automatically blocked
Inbound Access
Inbound Access
- Each sandbox URL requires API key authentication
- URLs are unique and hard to guess
- Access can be revoked by deleting the sandbox
Network Isolation
Network Isolation
- Sandboxes cannot access internal network resources
- Each sandbox is completely isolated from others
- Network policies enforce security boundaries

