Compute Lite

Compute Lite runs NocoDB sandboxes on your own servers instead of E2B. Sandboxes run scripts, the Run script workflow step, code in NocoAI chat, and the App Builder. Compute Lite runs as one Docker container. It needs no KVM and no cloud account.

How it works

 NocoDB ──HTTP (API key)──▶ Compute Lite :8430 ──▶ Docker ──▶ sandbox containers
   │                                                              ▲
   └──HTTP/WebSocket──────▶ Compute Lite :8431 (port proxy) ───────┘

Port 8430 is the API. NocoDB creates sandboxes and runs code through it, with an API key.
Port 8431 is the proxy to the sandboxes. NocoDB reaches each sandbox at <port>-<sandbox-id>.sandbox.example.com. The proxy reads this host name to find the sandbox, so a Service name alone is not enough. A wildcard DNS name, such as *.sandbox.example.com, must resolve to Compute Lite from NocoDB. It can be an internal name.

Only NocoDB connects to Compute Lite. Browsers never do.

Requirements

Item	Requirement
License	The Compute Lite add-on, on a self-hosted Scale or Enterprise license. Without the add-on, NocoDB ignores Compute Lite. See Purchase a license.
NocoDB	The Enterprise Docker image (not the npm package). Helm is not required.
Host	Linux, amd64 or arm64, Docker 24+. On Kubernetes, privileged pods.
Memory	1 GB, plus 1 GB per chat or script sandbox and 4 GB per App Builder sandbox that run at once.
Disk	30 GB free. The sandbox images take about 20 GB.
Network	Access to Docker Hub, or a private registry.

Security

Sandboxes are containers, not virtual machines. Treat the Compute Lite host as a host that runs untrusted code.
Sandboxes cannot reach private networks (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, cloud metadata) or each other. They can reach the internet. This applies in the default embedded mode, not in host mode.

Continue to Installation.