> For the complete documentation index, see [llms.txt](https://docs.computesdk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.computesdk.com/providers.md). # Providers - [AWS Bedrock AgentCore](https://docs.computesdk.com/providers/agentcore.md): Install and use the AWS Bedrock AgentCore provider for ComputeSDK with AWS credentials, regional config, and session-based sandboxes. - [Agentuity](https://docs.computesdk.com/providers/agentuity.md): Use Agentuity with ComputeSDK to create sandboxes, authenticate with an SDK key, and configure runtime, region, and timeout settings. - [Archil](https://docs.computesdk.com/providers/archil.md): Use Archil with ComputeSDK to run commands against an existing disk with API key auth, region config, and exec-only container sessions. - [Beam](https://docs.computesdk.com/providers/beam.md): Use Beam with ComputeSDK to create sandboxes with token and workspace authentication, then run commands with configurable gateway and timeout settings. - [Blaxel](https://docs.computesdk.com/providers/blaxel.md): Use Blaxel with ComputeSDK to create sandboxes with API key and workspace authentication, and configure image, region, memory, and exposed ports. - [Cloud Run](https://docs.computesdk.com/providers/cloud-run.md): Use the Google Cloud Run provider for ComputeSDK to run sandboxed commands in remote or direct mode, with ephemeral or stateful sandboxes, gateway auth, and sandbox CLI configuration. - [Cloudflare](https://docs.computesdk.com/providers/cloudflare.md): Install, configure, and use the Cloudflare provider for ComputeSDK to run sandboxes on Cloudflare's edge network. - [CodeSandbox](https://docs.computesdk.com/providers/codesandbox.md): Install and use the CodeSandbox provider for ComputeSDK to create sandboxes and run commands in CodeSandbox environments. - [Collimate](https://docs.computesdk.com/providers/collimate.md): Install and use the Collimate provider for ComputeSDK, including the required template ID for creating and running sandboxes. - [CreateOS](https://docs.computesdk.com/providers/createos-sandbox.md): CreateOS provider for ComputeSDK — NodeOps VM sandboxes with pause/resume/fork snapshots. A thin adapter over the official @nodeops-createos/sandbox package. - [Daytona](https://docs.computesdk.com/providers/daytona.md): Install and use the Daytona provider for ComputeSDK to create sandboxes and run commands in Daytona development workspaces. - [Declaw](https://docs.computesdk.com/providers/declaw.md): Declaw runs Firecracker microVMs with a built-in security stack: PII scanning, prompt-injection defense, TLS-intercepting egress proxy, and per-sandbox network policies. - [Docker](https://docs.computesdk.com/providers/docker.md): Docker provider for ComputeSDK — local containerized sandboxes (Python or Node.js) for development and testing. - [E2B](https://docs.computesdk.com/providers/e2b.md): Set up the E2B provider for ComputeSDK, configure your API key, and create sandboxes to run commands. - [Freestyle](https://docs.computesdk.com/providers/freestyle.md): Set up the Freestyle provider for ComputeSDK, configure your API key, and create sandboxes to run commands. - [HopX](https://docs.computesdk.com/providers/hopx.md): Set up the HopX provider for ComputeSDK, configure your API key, and create sandboxes to run commands. - [Isorun](https://docs.computesdk.com/providers/isorun.md): Isorun provider for ComputeSDK — isolated Linux VM sandboxes for running untrusted and AI-generated code, billed by the second. - [Just Bash](https://docs.computesdk.com/providers/just-bash.md): just-bash provider for ComputeSDK — local sandboxed bash execution with a virtual filesystem. No external services, containers, or authentication required. - [Kubernetes](https://docs.computesdk.com/providers/k8s.md): Kubernetes provider for ComputeSDK — run each sandbox as a Pod in your cluster and execute commands via pods/exec. - [Leap0](https://docs.computesdk.com/providers/leap0.md): Leap0 provider for ComputeSDK - enterprise-grade cloud sandboxes for AI agents with full filesystem, git, process, and desktop support. - [Lelantos](https://docs.computesdk.com/providers/lelantos.md): Lelantos provider for ComputeSDK — execute code in secure, EU-native Firecracker microVM sandboxes. - [Lightning](https://docs.computesdk.com/providers/lightning.md): Lightning AI provider for ComputeSDK — create and manage Lightning AI cloud sandboxes: run shell commands, read/write files, and manage the sandbox lifecycle. - [Modal](https://docs.computesdk.com/providers/modal.md): Set up the Modal provider for ComputeSDK, configure your credentials, and create sandboxes to run commands with optional GPU support. - [Namespace](https://docs.computesdk.com/providers/namespace.md): Namespace provider for ComputeSDK - Deploy and manage containerized sandboxes on Namespace's cloud infrastructure. - [Northflank](https://docs.computesdk.com/providers/northflank.md): Set up the Northflank provider for ComputeSDK, pass your project credentials, and create deployment-backed sandboxes to run commands and expose ports. - [Quilt](https://docs.computesdk.com/providers/quilt.md): Quilt provider for ComputeSDK — tenant-scoped Linux sandboxes with exec, published HTTP/WebSocket services, shell-backed filesystem operations, and snapshots. - [Railway](https://docs.computesdk.com/providers/railway.md): Railway provider for ComputeSDK — run commands in Railway Sandboxes, ephemeral compute environments backed by the Railway platform. - [Runloop](https://docs.computesdk.com/providers/runloop.md): Set up the Runloop provider for ComputeSDK, configure your API key, and create sandboxes to run commands. - [Secure Exec](https://docs.computesdk.com/providers/secure-exec.md): Secure execution provider for ComputeSDK — a local, isolated sandbox using secure-exec's V8 isolates, with an in-memory filesystem. No remote service or credentials required. - [Sprites](https://docs.computesdk.com/providers/sprites.md): Set up the Sprites provider for ComputeSDK, configure your token, and create cloud sandboxes to run commands and expose apps. - [Superserve](https://docs.computesdk.com/providers/superserve.md): Superserve provides sandbox infrastructure to run code in isolated cloud environments powered by Firecracker MicroVMs. - [Tenki](https://docs.computesdk.com/providers/tenki.md): Tenki Cloud provider for ComputeSDK - microVM sandboxes with native filesystem, preview URLs, snapshots, and SSH. - [Tensorlake](https://docs.computesdk.com/providers/tensorlake.md): Tensorlake provider for ComputeSDK - Stateful MicroVM sandboxes for agentic applications and LLM-generated code execution. - [Upstash](https://docs.computesdk.com/providers/upstash.md): Set up the Upstash provider for ComputeSDK, configure your API key, and create default or ephemeral boxes to run commands. - [Vercel](https://docs.computesdk.com/providers/vercel.md): Set up the Vercel provider for ComputeSDK, configure project credentials or OIDC auth, and create sandboxes to run commands. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.computesdk.com/providers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.