What do Lovable, Anything, Bolt.new, v0, Base44, Macaly, Orchids, cto.new all have in common (besides being fun to use)?
They need secure sandboxes to run their users’ AI-generated code.
Sounds simple enough, right?
Well, these sandboxes need to be created instantaneously, by the thousands, with a secure connection to the user’s browser, and with smooth bi-directional communication. Most AI builder tools are not going to use their precious time building that kind of robust sandbox infrastructure themselves, and they don’t really need to.
There are platforms that are built for this exact purpose: E2B, Daytona, Modal, Runloop, Blaxel, CodeSandbox to name a few. These sandbox providers handle the complicated hosting, securing, creating, proxying, and reliability of sandboxes. So, most AI builder tools will choose one of these providers and build their application on top of their service, so that they can focus on building their core application and giving users the thrill of building with AI.
But not all sandbox providers are created equal. Critical features on one sandbox provider may not be available on another. The cold start time may be significantly faster on another provider. The cost of one provider might be become significantly more expensive than the others. What options does an AI builder company have when one of these becomes a limiting factor to their revenue or profit?
They have a few options that aren’t ideal:
- They can build their own sandbox infrastructure (this is the least reasonable).
- They can accept their current provider’s lack of features.
- They can try to negotiate a discount with their sandbox provider.
- They can pass the cost on to their customers and increase prices.
- They can spend months rebuilding their application on a different provider (although, they might have to do this again in the future).
This is the core problem that ComputeSDK solves for apps using ephemeral sandboxes. If you are an AI app builder, you aren’t stuck with your sandbox provider, you don’t have to live with a lack of features, and you don’t have to spend months rebuilding your application on another provider.
With ComputeSDK, you can add or change sandbox providers overnight.
Is reliability your issue? Add a new provider as a fallback.
Is cost your issue? You can shop around with confidence.
Are you missing sandbox features? Use our lightweight daemon to get the same set of features across any provider.
And not just sandbox providers, any cloud provider. The Compute daemon can run in any sandbox, container, or just bare metal. You can move your existing sandbox infrastructure to any cloud provider (Railway, AWS, GCP, etc), and we would be thrilled to help you.
Here’s how to start:
- Sign up and use one of our open-source sandbox provider packages and begin managing your sandboxes.
- Reach out on X or [email protected].
- Schedule a meeting with us, we are more than happy to discuss implementation.
Thanks for reading!
-Garrison