Advanced options are designed for teams that need tighter runtime isolation, stronger infrastructure controls, or always-on cloud execution.
Coming soon: Local Apple Container, GCP, and AWS are not generally available yet.
Run locally with containerized isolation on Apple hardware. This can improve reproducibility by keeping runtime dependencies inside a controlled environment.
Use this option when you want local data residency with clearer process boundaries than a direct host runtime.
Deploy to Google Cloud when you want managed cloud infrastructure and scalable compute.
vellum hatch --remote gcpConfirm IAM permissions and network boundaries before production rollout.
Deploy to AWS when your organization already standardizes on AWS identity, networking, and observability tools.
vellum hatch --remote awsApply least-privilege IAM policies and restrict inbound access to minimize risk.
| Option | Best for | Requirements | Tradeoff |
|---|---|---|---|
| Local Apple Container (Coming soon) | Local isolation and reproducible runtime setup | Container runtime on Apple hardware | Extra local setup complexity |
| GCP (Coming soon) | Cloud-hosted assistants on Google Cloud | GCP project, auth, and network configuration | Cloud cost and operations ownership |
| AWS (Coming soon) | Cloud-hosted assistants in AWS environments | AWS account, IAM setup, and networking | Cloud cost and operations ownership |