Hey HN, I'm Garrison, founder of ComputeSDK (https://www.computesdk.com). ComputeSDK is a universal sandbox interface that lets you build, deploy, and interact with sandboxes across any provider (E2B, Daytona, Modal; AWS, Fly.io coming soon) using a single, consistent API with built-in secure tunneling.

Try it out for free here: https://www.computesdk.com/docs/getting-started/quick-start/

Today we are proud to announce the Compute CLI.

I built ComputeSDK after shipping a K8s-based sandbox product for a large enterprise client. Shortly after, when I started talking to AI app builders, I noticed a common frustration: they all ended up building integrations with multiple sandbox providers. Each integration meant rewriting their application, custom proxies, and routing.

As I talked with more customers, I realized sandbox providers and app builders had massive architectural overlap. Both were having to write their own custom terminals, file-watchers, proxies, and more to interact with their sandboxes.

At this point, I realized there was a missing piece in the development infrastructure stack: a way to decouple your application from your sandbox provider while still getting full, live interactivity.

Our original K8s architecture had three services: an API, a gateway, and a sidecar. We extracted our sidecar component and rebuilt it as the "Compute" cli, a lightweight service that installs in any sandbox and automatically creates a secure tunnel to your app. Then we wrapped it with a universal SDK that works across providers. Now you write your sandbox implementation once, and it works everywhere: from E2B, Daytona, & Modal to general cloud platforms like Railway, Fly.io, & AWS.

ComputeSDK provides a consistent interface for sandbox creation and management. It gives you instant access to terminals, file systems, real-time file watching, and a WebSocket event system from any client (server, browser, application). You can switch or add providers easily by importing the provider module and updating environment variables.

We'd love to get any feedback from the community, ideas, or experiences building similar tools.

Thanks!