bochka vs E2E Networks
E2E Networks is an Indian cloud that rents VMs, called nodes, and GPUs. bochka is built for AI agents: every sandbox is a full VM with coding agents, a 60fps desktop and a disk that snapshots every minute and stops for free.
Where bochka stands out
Coding agents you drive from outside
bochka ships Claude Code, Codex, OpenCode and other agents inside each sandbox, and you drive them from outside with a prompt, steer and events API. Its credentials proxy keeps real AI keys out of the sandbox and can switch to another account when one runs out of credits. An E2E node is a plain VM: you install the agent, pass it keys and write the code that starts and watches it.
A disk that saves every minute and stops for free
A bochka sandbox saves its disk every minute and on stop, and a stopped sandbox costs nothing until you start it again. On E2E only E1 nodes can be stopped. A powered-off C3 or SDC3 node keeps billing compute, and its snapshots are taken on demand or on a schedule you set.
A desktop and browser ready for computer use
Every bochka sandbox has a 60fps desktop and Chromium, with computer use and browser control, and you can embed the stream in your app. E2E nodes have no desktop; its own guide has you install xrdp and a desktop like XFCE by hand.
The companies and products
bochka
bochka.xyz runs sandboxes for AI agents: each one is a full Linux VM with its own kernel.
You start a machine with one command or one API call, then SSH in, run Docker, open a desktop, or let a built-in agent (Claude Code, Codex, OpenCode and others) work in it. The disk stays between sessions, and a stopped sandbox costs nothing.
- Isolation
- Full VM per sandbox, own kernel
- Regions
- EU: Germany, Finland, France
E2E Networks
E2E Networks is a listed Indian cloud provider that rents Linux and Windows VMs, GPUs and an AI platform called TIR.
You create nodes (VMs) from a console or a REST API, pick a family such as C3 (shared, compute-optimized), SDC3 (dedicated vCPUs) or E1 (low cost, the only family that can be stopped), and manage disks, images, security groups and load balancers yourself. It is a general cloud, not an agent sandbox: there is no sandbox SDK, desktop or agent tooling, so you build that layer. It is aimed at Indian companies and AI teams that want GPUs and data kept in India.
- Region
- India
Which use cases each one fits
For each use case, Battleships prices every sandbox provider on the same workload and sorts them from the cheapest monthly bill up. “3rd cheapest of 367” means 2 of the other 366 providers run that workload, with every feature it needs, for less. “With limits” means the provider runs it but misses something, so it is listed after every full match. Open a use case for its whole ranking and what each provider misses.
| Use case and its workload | bochka: price rank | E2E Networks: price rank |
|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month E2E gives you a VM with Docker, but the agent, its API and saving work between runs are yours to build, so it is a compromise. | 3rd cheapest of 367 $634 a month | 99th of 367, with limits $875 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB An assistant that sleeps between tasks keeps paying for compute on a C3 node, because only E1 nodes can be stopped. | 5th cheapest of 366 $657 a month | 187th of 366, with limits $1,706 a month |
| Code interpreter bursts 100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month | 186th of 345, with limits $2,000 a month | 191st of 345, with limits $3,349 a month |
| Sandboxes for your users 300 at once · 2 vCPU / 4 GB · 30,000 sessions of 23 min a month E2E does not publish how many nodes an account can run at once, so 300 sandboxes for your users is not confirmed. | Cheapest of 361 $209 a month | 67th of 361, with limits $575 a month |
| RL rollouts 1,000 at once · 2 vCPU / 4 GB · 1,000,000 sessions of 3 min a month | 34th of 360, with limits $2,000 a month | 40th of 360, with limits $2,450 a month |
| Agent evals 250 at once · 4 vCPU / 8 GB · 15,000 sessions of 20 min a month | 10th cheapest of 364 $200 a month | 100th of 364, with limits $245 a month |
| CI runners 40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month Both fit: a CI job is a plain Linux VM with Docker, which is what E2E sells. | 4th cheapest of 377 $86 a month | 16th cheapest of 377 $227 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB Both fit: a dev box that runs all month is a normal cloud VM job. | 18th cheapest of 368 $26 a month | 26th cheapest of 368 $36 a month |
| Computer-use agents 50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month E2E nodes ship with no desktop, and its guide has you install xrdp and XFCE yourself, while bochka streams a 60fps desktop with computer use. | 6th cheapest of 369 $200 a month | 112th of 369, with limits $245 a month |
| Browser-use agents 50 at once · 2 vCPU / 4 GB · 30,000 sessions of 10 min a month bochka ships Chromium and browser control in every sandbox; on E2E you install and run the browser yourself. | 7th cheapest of 367 $200 a month | 213th of 367, with limits $245 a month |
| Scraping & bots (startup scale) 50 at once · 1 vCPU / 2 GB · 100,000 sessions of 3 min a month | 6th cheapest of 346 $90 a month | 248th of 346, with limits $268 a month |
| Mass scraping & bots (undetectable) 1,000 at once · 1 vCPU / 2 GB · 3,000,000 sessions of 2 min a month | 71st of 338, with limits $1,800 a month | 162nd of 338, with limits $5,362 a month |
| Parallel red teaming 200 at once · 2 vCPU / 4 GB · 5,000 sessions of 30 min a month | 2nd cheapest of 360 $200 a month | 154th of 360, with limits $124 a month |
| GPU eval jobs 10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month Only E2E fits: it rents Nvidia GPUs from L4 to B200, billed per minute, and bochka has no GPUs. | Can't run it | Can't run it |
| macOS agents 5 at once · 4 vCPU / 8 GB · 1,000 sessions of 20 min a month | Can't run it | Can't run it |
Key features
| Feature | bochka | E2E Networks |
|---|---|---|
| What you get | A sandbox API for agents: create, fork, stop and drive VMs from code | General cloud nodes (VMs), disks, images and load balancers from a console or REST API |
| Isolation | Every sandbox is a full VM with its own kernel | Every node is a full VM |
| CPU | Dedicated AMD Ryzen 9 9950X (Zen 5) hosts; 26.69 runs/s in a public Node.js benchmark at 4 vCPU / 8 GB | C3 is a shared family; SDC3 has dedicated vCPUs; no public benchmark result |
| Docker and nested virtualization | Docker, root, systemd and /dev/kvm on every machine | Docker runs inside nodes and you log in over SSH; nested virtualization is not documented |
| Stopping and files | Snapshots every minute and on stop; a stopped sandbox costs nothing | Only E1 nodes can be stopped; a powered-off C3 or SDC3 node keeps billing compute; snapshots are on demand or scheduled |
| Cloning a machine | Fork a running sandbox in one call | Save an image from a node, then launch new nodes from it |
| Desktop and computer use | 60fps desktop and Chromium, computer use and browser control, embeddable stream | No desktop out of the box; the guide installs xrdp and XFCE by hand |
| Coding agents | Claude Code, Codex, OpenCode and more preinstalled, with a prompt, steer and events API | None; you install and run agents yourself |
| Keeping keys out of the sandbox | AI credentials proxy for model providers and any HTTPS API you register; switch a credential to another account when credits run out | A Vault-compatible secret store that the VM reads secrets from |
| Reaching the machine | HTTPS URLs for up to 50 ports, token-protected; raw TCP; dedicated IPv6 or IPv4 | Public IPv4 per node (not by default on E1); load balancers with HTTPS; SSH |
| Network rules | Open internet on every plan; no provider-side allowlist | Security groups with inbound and outbound rules by protocol, port and IP range |
| GPUs | None | Nvidia L4 up to B200, hourly rates billed per minute |
| Windows | No Windows guests; Wine for Windows apps | Windows Server nodes in E1 sizes, with RDP |
| Regions | EU only: Germany, Finland, France | India |
| Compliance and transparency | SOC 2 is in progress. We're open about where we stand: live status and data retention policy. | SOC 2 |
Every feature Battleships tracks (43)
| Feature | bochka | E2E Networks |
|---|---|---|
| Full VM (own kernel) | Yes | Yes |
| Docker inside | Yes | Yes |
| Nested virtualization | Yes | Not published |
| Root | Yes | Not published |
| Systemd | Yes | Not published |
| Desktop GUI | Yes | No |
| Browser | Yes | No |
| Computer-use API | Yes | No |
| SSH | Yes | Yes |
| Persistent disk | Yes | Yes |
| Pause/resume | Yes | Yes |
| Automatic snapshots | Yes | No |
| Fork/clone | Yes | Yes |
| Live fork (no pause) | Yes | Yes |
| Memory fork | No | No |
| Custom image (Docker or snapshot) | Yes | Yes |
| ≥24 h sessions | Yes | Yes |
| Idle auto-stop | No | No |
| Wake on request | No | No |
| HTTPS preview URLs | Yes | Yes |
| Raw TCP inbound | Yes | Not published |
| Public IPv4 | No | Yes |
| Egress allowlist | No | Yes |
| Secret proxy | Yes | No |
| Secret proxy for any API | Yes | No |
| Preinstalled agents | Yes | No |
| Agent harness API | Yes | No |
| MCP server | No | No |
| GPU | No | Yes |
| Windows | No | Yes |
| Arm64 | No | No |
| Self-hosting | No | No |
| BYOC | No | No |
| Open source | No | No |
| Scoped API keys | Yes | Not published |
| Spend limits | Yes | Not published |
| Usage per sandbox (API) | Yes | Yes |
| Audit logs | No | Not published |
| SSO | No | Yes |
| SOC 2 | No | Yes |
| HIPAA | No | No |
| EU data residency | Yes | No |
| Zero data retention | Yes | Not published |
Performance
There is no comparable measurement: E2E Networks was not in StarSling's public sandbox benchmark, where bochka did 26.69 Node.js build-and-test runs per second at 4 vCPU / 8 GB. The C3 shape we price is a shared family; E2E's SDC3 family has dedicated vCPUs.
Node.js build-and-test loop at 4 vCPU / 8 GB, higher is better. Measured with the open hpc-sandbox-benchmarks suite. E2E Networks has no published run in this suite yet, so there is no like-for-like number to compare.
Pricing in five scenarios
Each bill is priced from the providers' public price lists by the open Battleships engine, with the cheapest plan that runs the scenario.
| Scenario | bochka, a month | E2E Networks, a month |
|---|---|---|
| One coding agent, workdays 4 vCPU / 8 GB, 50 GB disk, 8 hours a day, 22 days a month, files kept between days | $20 · $20/mo | $9 · Pay as you go |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $26 · $20/mo | $36 · Pay as you go |
| 50 agents in parallel 50 machines of 4 vCPU / 8 GB at once, 8-hour sessions, 1,100 sessions a month, Docker inside | $317 · $20/mo × 3 seats | $431 · Pay as you go |
| Sandboxes for your users 2 vCPU / 4 GB, 30,000 sessions of 10 minutes a month, up to 300 at once | $200 · $100/mo × 2 seats | $245 · Pay as you go · with limits |
| 1,000 short jobs at once 2 vCPU / 4 GB, 1,000 at once, 3 minutes each, 200,000 jobs a month | $2,000 · $2000/mo · with limits | $490 · Pay as you go · with limits |
bochka: You pick a monthly plan from $20, and all of it becomes usage credit spent per second on running sandboxes. A stopped sandbox costs nothing and keeps its disk.
E2E Networks: E2E lists an hourly rate per node size, $0.049 an hour for the C3 shape with 4 vCPU and 8 GB, before taxes, with disks, IPs, snapshots and backups billed on top. C3 nodes cannot be stopped, so the workday price assumes you delete the node after work and launch it again from a saved image; committed terms are paid up front.
Limits in those scenarios
E2E does not publish how many nodes an account can run at once, so 300 sandboxes for your users and 1,000 short jobs at once are not confirmed there, and the typical published limit elsewhere is 50. E2E also does not publish an egress price, and the C3 shape has shared vCPUs that can slow under heavy, sustained load. On bochka the limit is a sandbox count (100 to 2,000 by plan) plus starts per minute, so the 1,000-job burst gets queued and needs more starts per day than the $2,000 plan allows.
| Scenario | bochka | E2E Networks |
|---|---|---|
| One coding agent, workdays | None that bite |
|
| One agent that never stops | None that bite |
|
| 50 agents in parallel | None that bite |
|
| Sandboxes for your users | None that bite |
|
| 1,000 short jobs at once |
|
|
Which one should you use?
Use E2E Networks when
you need GPUs, Windows Server, very large VMs, or data that stays in India, and you are ready to build the sandbox layer yourself.
- GPUs billed per minute. Useful if your agents train, fine-tune or serve models: E2E rents Nvidia GPUs from L4 to B200, billed per minute.
- Windows Server and big machines. Useful if you need Windows Server, or one very large VM with up to 120 dedicated vCPUs.
- Data in India, with network rules. Useful if your data must stay in India, or you need outbound rules by port and IP range.
Use bochka when
you run AI agents: full VMs with coding agents, a desktop and a credentials proxy built in, that snapshot every minute and stop for free between tasks.
- Coding agents you drive from outside. On E2E your team writes and runs the control layer: starting agents, sending prompts, streaming events and keeping keys safe. Real keys also sit inside a machine that runs code an agent wrote.
- A disk that saves every minute and stops for free. Agents sit idle between tasks. On a C3 node you either pay for compute while it waits, or delete it and rebuild from a saved image, which takes setup code and loses work since the last image.
- A desktop and browser ready for computer use. A computer-use agent needs a screen, a browser and a way to click and type. On E2E you build that image, keep it patched and add your own control layer before the agent can do anything.
Questions people ask
Is bochka cheaper than E2E Networks?
It depends on the scenario. One agent running all month comes to $26 a month on bochka and $36 on E2E, and 50 agents in parallel come to $317 versus $431. One agent on workdays is $20 on bochka and $9 on E2E, but only if you delete and rebuild the node every day, and 1,000 short jobs at once fits neither without higher limits.
Is E2E Networks a sandbox for AI agents?
No. E2E is a general cloud that rents VMs, GPUs, storage and networking. You can run an agent on a node, but the sandbox API, agent tooling, desktop and key handling are yours to build. bochka is built for that job.
Can I stop an E2E node and stop paying?
Only E1 nodes have a Stop action that pauses compute billing. Powering off a C3, SDC3 or other node does not stop node billing, and disks, IPs and snapshots keep billing too. A stopped bochka sandbox costs nothing and keeps its disk.
Does bochka have GPUs or Windows like E2E Networks?
No. bochka has no GPUs and no Windows guests; it runs Linux VMs on dedicated AMD Ryzen 9 9950X (Zen 5) hosts and has Wine docs for Windows apps. If you need GPUs or Windows Server, E2E has both.
Where does my data run?
bochka runs only in the EU (Germany, Finland and France), with EU data residency and a zero data retention option. E2E runs its cloud in India.
Is bochka SOC 2 compliant?
SOC 2 is in progress. We're open about where we stand: live status at status.bochka.xyz and our data retention policy at docs.bochka.xyz/data-retention. E2E lists SOC 2, several ISO certifications and PCI DSS on its certifications page.
Start a sandbox
Install the CLI, then run bochka new.
Product preview