Basic
Start with the simplest configuration:Advanced compute settings
You can increase CPU, memory, or assign a GPU - depending on your use case:Customize your environment
See the Images section for more information on how to customize the runtime.Persistent Storage
Beam supports two types of persistent storage: fast distributed volumes and cloud buckets you already manage.Distributed Storage Volumes
Mount fast storage volumes to persist files between sessions:- Are working on a project that spans multiple sessions
- Need to share data between different sandbox instances
- Want to keep work safe even if sandbox crashes
Cloud Buckets
For large datasets or team sharing, you can use your own buckets:- Sensitive data
- Connecting existing object storage
- Long-term data storage in your own infrastructure
Session Management
Timeout Configuration
Set timeouts to control costs:Manual vs Automatic Termination
- Long-running training jobs
- Collaborative development sessions
- When you need to pause and resume work
Environment Variables and Secrets
Environment Variables
Pass configuration to your applications:- Keeping sensitive data out of your code
- Configuring applications for different environments
- Sharing configuration across team members
Secrets Management
You can attach secrets to your sandbox using Beam’s secret management system - they will be exposed as environment variables inside the Sandbox:- Database passwords
- API keys and tokens
- Private keys and certificates
Best Practices
Start Small, Scale Up
Common Mistakes
Over-provisioning
Including Unnecessary Packages
Long Timeouts for Short Tasks
What’s Next?
Now that you understand configuration, let’s put it to work:- Process Management: Run code and commands in your configured environment
- File System Operations: Upload, download, and manage files
- Networking: Deploy web services and expose them to the internet
- Examples: See real-world configurations in action