Architecture: Which code sandbox service to use for Vitto — E2B vs self-ho...

Documentation for Sessions

🏗️ Architecture: Which code sandbox service to use for Vitto — E2B vs self-ho...

Date: 2026-02-20
Time: 00:38:32 UTC
Session: gspace1-125.132
Agent: angular
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

Which code sandbox service to use for Vitto — E2B vs self-hosted Docker vs isolated-vm?

Task: Session 125: Code sandbox decision

🎯 Decision Made

Chosen:

E2B managed service (free tier $100 credits)

Options Considered:

E2B managed service (free tier $100 credits)
Self-hosted Docker containers
V8 isolated-vm (JavaScript only)

💭 Reasoning

E2B provides Firecracker microVMs with full Linux isolation (~150ms boot), multi-language support (JS/TS/Python/bash), and $0 cost on free tier (thousands of executions). Docker is incompatible with Railway (no Docker-in-Docker). isolated-vm is JS-only. E2B is used by Cursor, Perplexity, Manus — proven at scale. Free tier sufficient for months. Pro ($150/mo) only needed at high volume.

📁 Files Involved

apis/backend-vitto-api/src/app/engine/sandbox.service.ts

🔗 Related

Decision ID: dev_1771547912862_74mh6pb
Session: 125
Workspace: gspace1

Auto-generated by MCP Smart Consolidation