Problem
In self-hosted Kubernetes deployments, the Function block shows:
"JavaScript code with import statements requires E2B to be enabled.
Please remove the import statements, or contact your administrator to enable E2B"
E2B is an external third-party cloud service. Self-hosted users should not
be forced to depend on an external paid service for basic code execution.
Feature Request
Add a local sandbox execution option for self-hosted instances — for example:
- Spin up an isolated Docker/Kubernetes Job to execute the Function block code
- Use Node.js child_process with --experimental-vm-modules for JS imports
- Use a restricted Python container for Python execution
This would allow self-hosted users to use JavaScript imports and Python
in Function blocks without needing an E2B account or external dependency.
Why This Matters
- Self-hosted users want full data privacy — no code leaving the cluster
- E2B is a paid external service — adds cost and external dependency
- Simple use cases (import lodash, import axios) don't need a full microVM
Alternatives Considered
- E2B self-hosting via Terraform — too complex, requires AWS/GCP infra
- Using fetch() only — limits what Function blocks can do
References
Problem
In self-hosted Kubernetes deployments, the Function block shows:
E2B is an external third-party cloud service. Self-hosted users should not
be forced to depend on an external paid service for basic code execution.
Feature Request
Add a local sandbox execution option for self-hosted instances — for example:
This would allow self-hosted users to use JavaScript imports and Python
in Function blocks without needing an E2B account or external dependency.
Why This Matters
Alternatives Considered
References