Technology · Agentic → Code Sandbox · Open Source · wiki:deep
Jupyter Enterprise Gateway
Jupyter Enterprise Gateway is a web server that gives headless, enterprise access to Jupyter kernels — including remote kernels on distributed clusters (Apache Spark on YARN, IBM Spectrum Conductor, Kubernetes, Docker Swarm, or local to the gateway). It extends Jupyter Kernel Gateway’s websocket mode with multi-tenant remote launch, secure client→gateway→kernel paths, and persistent kernel sessions. Out of the box it supports IPython (Python), IRkernel (R), and Apache Toree (Scala).
It does not manage fleets of Notebook servers — use JupyterHub for that. Install via pip install jupyter_enterprise_gateway and run jupyter enterprisegateway.
Why it matters here
Some agent/analysis paths need governed notebook compute on a cluster, not a disposable cloud micro-VM. Enterprise Gateway is the Code Sandbox pick when isolation means resource-manager placement and shared Spark/K8s kernels behind a gateway. Prefer e2b / Daytona when the agent needs programmatic sandboxes for arbitrary code/shell without a Jupyter protocol.
How it works
Clients talk to the Enterprise Gateway; the gateway’s process-proxy/launcher framework starts kernels locally, round-robin on nodes, or via a configured resource manager. Sessions can persist; communication is secured end-to-end through the gateway.
- Deploy Enterprise Gateway in the cluster network.
- Notebook/agent clients open websocket sessions to the gateway.
- Gateway launches remote kernels under the chosen resource manager.
- Code executes on the remote kernel; results return through the gateway — not as unrestricted host shell.
Related: daytona · e2b · topics/06-self-coding
Scroll inside the canvas to pan
When to reach for it
- Use when: you need multi-tenant remote Jupyter kernels on Spark/K8s/Swarm with enterprise gateway controls.
- Skip when: you need agent cloud sandboxes for arbitrary commands (e2b, daytona), or multi-user Notebook server orchestration alone (JupyterHub).
- Prefer instead: e2b for SDK sandboxes; JupyterHub alongside EG when you also need notebook server farms.
Limits
- Jupyter-protocol shaped: not a general Docker sandbox API for non-kernel agents.
- Ops weight: cluster resource managers and network paths are real SRE cost.
- Not JupyterHub: confusing the two leads to the wrong architecture.
- Not the ledger: kernel output is analysis evidence, not company authority.
Linked from
Catalog backlinks — what points here (wiki “what links here”).
Features
Stacks
Peers
What we checked
Claims below are backed by science sources on disk.
Remote kernels / gateway role
jupyter-server/enterprise_gateway · MODERATE
“Sandbox — A fast, secure Linux VM created on demand for your agent, which you can pause and resume as needed”
Docs / operators surface
Enterprise Gateway documentation · MODERATE
“E2B provides isolated sandboxes that let agents safely execute code, process data, and run tools.”
Contrast vs agent sandboxes
E2B contrast · MODERATE
“Open-source, secure environment with real-world tools for enterprise-grade agents.”
In this research stack
Features and peers linked from the catalog map — not a second product surface.
Features it supports
Same cell
Stack
Document management
No DM vendor crosswalk edges yet.
Source
Primary repo github.com/jupyter-server/enterprise_gateway · Open Source
technologies/jupyter-enterprise-gateway/README.md
Research inventory
9 tags · 7 out · 8 in · 3 artifacts · 1 gaps · 26 corpus docs
Catalog tags
- landscape.layer
- Agentic
- landscape.subcategory
- Code Sandbox
- license_tag
- Open Source
- maps.dm
- absent
- maps.features
- 5
- one_liner
- Agentic
- review.depth
- science
- slug
- jupyter-enterprise-gateway
- title
- Jupyter Enterprise Gateway
Artifacts
- dm_map · absent
- features_map · present · technologies/jupyter-enterprise-gateway/features.md
- readme · present · technologies/jupyter-enterprise-gateway/README.md
Out · alternative_to
Out · maps_to
- browser-computer-usefeature
- job-codingfeature
- r2-06-self-codingfeature
- sandboxing-isolationfeature
- wt-tools-actionsfeature
In · alternative_to
In · in_stack
- agentic-code-sandboxstack · alternative_slot
In · maps_to
- browser-computer-usefeature
- job-codingfeature
- r2-06-self-codingfeature
- sandboxing-isolationfeature
- wt-tools-actionsfeature
Corpus tags
- category
- Agentic → Code Sandbox
- dedication
- open-source
- feature
- browser-computer-usejob-codingr2-06-self-codingsandboxing-isolationwt-tools-actions
- kind
- map_edgetech_featurestech_quotetech_readmetech_science_sourcetech_section
- needs_deepen
- false
- quality
- ok
- section
- EvidenceFeatures mapGitHub mapHow it worksLimits & failure modesLinksScientific notesWhat it isWhen to use / skipWhy it matters here
- slug
- jupyter-enterprise-gateway
- source_id
- e2b-contrastjeg-docsjeg-github
- technology
- jupyter-enterprise-gateway
Corpus documents (26)
map_edge · 5
- jupyter-enterprise-gateway → browser-computer-use
- jupyter-enterprise-gateway → job-coding
- jupyter-enterprise-gateway → r2-06-self-coding
- jupyter-enterprise-gateway → sandboxing-isolation
- jupyter-enterprise-gateway → wt-tools-actions
tech_features · 1
- Jupyter Enterprise Gateway · features
tech_quote · 6
- Jupyter Enterprise Gateway · e2b-contrast
- Jupyter Enterprise Gateway · e2b-contrast
- Jupyter Enterprise Gateway · jeg-docs
- Jupyter Enterprise Gateway · jeg-docs
- Jupyter Enterprise Gateway · jeg-github
- Jupyter Enterprise Gateway · jeg-github
tech_readme · 1
- Jupyter Enterprise Gateway
tech_science_source · 3
- Jupyter Enterprise Gateway · e2b-contrast
- Jupyter Enterprise Gateway · jeg-docs
- Jupyter Enterprise Gateway · jeg-github
tech_section · 10
- Jupyter Enterprise Gateway · Evidence
- Jupyter Enterprise Gateway · Features map
- Jupyter Enterprise Gateway · GitHub map
- Jupyter Enterprise Gateway · How it works
- Jupyter Enterprise Gateway · Limits & failure modes
- Jupyter Enterprise Gateway · Links
- Jupyter Enterprise Gateway · Scientific notes
- Jupyter Enterprise Gateway · What it is
- … +2 more