- Scenarios where alternatives are better
- If a stable, long-term managed SaaS is required
- The vendor has announced a sunset of the cloud offering; managed alternatives or self-hosted open-source projects may provide stronger continuity guarantees.
- If enterprise procurement mandates formal compliance documentation
- Lack of publicly documented SOC 2/ISO/HIPAA/PCI posture is a potential procurement blocker.
- If agents require stateful sandboxes
- The platform does not preserve sandbox state across redeploys; alternatives that support durable session state or explicit persistence patterns are more appropriate.
- If maximum runtime control and bespoke networking or data residency are required
- Teams able to invest in building on primitives will retain full control over networking, VPC, and residency.
- Recommended vendor inquiries during evaluation because of the sunset
- Request a timeline for shutdown and deprecation milestones
- Ask for a clear migration path and tooling for exporting agent code and configuration
- Confirm which components will be open-sourced and the expected maintenance or community governance model
- Current limitations acknowledged by the vendor
- The vendor has stated that the cloud service is sunsetting, which is the most significant limitation for new adopters.
- Sandbox provider selection and other controls were indicated as roadmap items at the time of documentation and may not have been available in the cloud offering.
- Technical limitations highlighted in docs
- Redeploy destroys prior sandbox state and does not preserve files or data in the sandbox.
- Deployments may fail due to dependency installation errors that arise during in-sandbox package installation.
- Roadmap / future work
- Past roadmap items included better tracing, higher concurrency limits, and persistent sandboxes; these should be treated as historical intent rather than current guarantees given the vendor's cloud sunset.