Home Technology Show HN: TakoVM – Isolated model and tool execution used...
Technology

Show HN: TakoVM – Isolated model and tool execution used by enterprises

Key Points

Run untrusted Python safely. Job queues and Docker isolation built-in. Run AI-generated code in isolated Docker containers with optional gVisor sandboxing.

Run untrusted Python safely. Job queues and Docker isolation built-in. Used by enterprises. Run AI-generated code in isolated Docker containers with optional gVisor sandboxing. Job queues, retries, and execution history included. Documentation · Quick Start · API Reference # Install (requires Docker + Python 3.10+) pip install "tako-vm[server]" tako-vm setup # pull the executor Docker image tako-vm server # start server (auto-starts PostgreSQL via Docker) # Execute code curl -X POST http://localhost:8000/execute \ -H "Content-Type: application/json" \ -d '{"code": "print(1 + 1)"}' Sandbox solutions like e2b and microsandbox give you isolated code execution—but that's it. You still need to build: | You build | With sandbox-only | With Tako VM | |---|---|---| | Job queue | Redis + Celery/Bull | Built-in | | Execution history | Postgres + schema | PostgreSQL included | | Retry logic | Custom code | Automatic | | Idempotency | Deduplication logic | idempotency_key | | Replay/debugging | Custom tooling | Rerun/fork API | Tako VM is the complete package: - Job queue + workers - Async execution with worker pool, no Redis/Celery setup - Execution history - Every job persisted with stdout, stderr, timing, artifacts - Replay to debug - Rerun past jobs with exact same code and inputs - Docker isolation - Each job in its own container with seccomp filtering - Network isolation - No network by default, optional allowlist per job type - Self-hosted - Your machine, offline-capable, zero per-execution cost tako-vm setup # Pull executor image and verify Docker tako-vm server # Start the API server tako-vm server --port 9000 # Custom port tako-vm dev up # Start local PostgreSQL for development tako-vm dev up --with-server # Start PostgreSQL + API server tako-vm dev status # Check local PostgreSQL status tako-vm dev down # Stop local PostgreSQL tako-vm config # Show current configuration tako-vm config --json # Output as JSON tako-vm validate # Validate current config tako-vm validate my.yaml # Validate specific file tako-vm status # Check server health tako-vm version # Show version tako-vm --config my.yaml server # Use specific config file | Topic | Link | |---|---| | Installation | docs/getting-started/installation.md | | Quick Start | docs/getting-started/quickstart.md | | Configuration | docs/getting-started/configuration.md | | REST API | docs/api/rest.md | | Python SDK | docs/api/sdk.md | | Job Types & Environments | docs/guide/environments.md | | Security | docs/deployment/security.md | | Deployment | docs/deployment/how-to-deploy.md | | Config Reference | tako_vm.yaml.example | Apache License 2.0
Docker (PERSON) -X POST http://localhost:8000 (ORG) Sandbox (LOCATION) microsandbox (ORG) Tako VM (ORG) API (ORG) tako-vm (ORG) Docker tako-vm (PERSON) tako-vm --config my.yaml (PERSON) Python SDK (ORG) Job Types & Environments (ORG)
Originally published by Hacker News Read original →