Skip to content
TAIP

Products / For AI builders

DevSpace

Available

Managed AI development environments on Kubernetes

DevSpace turns a Kubernetes cluster into a self-service development platform for AI and data science teams. Users pick a template, pick hardware, and get an isolated environment with persistent storage and the right libraries. Platform teams get multi-tenant isolation, per-environment auth, idle shutdown, and live resource visibility — without per-IDE bespoke plumbing.

Boot
Seconds
IDEs
Jupyter · VS Code · Marimo · Streamlit · Gradio
Idle
Auto stop or delete

Capabilities

What DevSpace gives you

01

Notebook, IDE, app — same plane

Jupyter, Marimo, Streamlit, Gradio, VS Code Server out of the box. Add any new IDE through an EnvironmentTemplate CRD — no code changes, no controller redeploy.

02

Isolated by default

Each environment runs as its own StatefulSet with an oauth2-proxy sidecar. Only the owner can reach the IDE — even if someone else discovers the URL. NetworkPolicy locks the rest down.

03

Idle shutdown that frees GPUs

An activity sidecar polls the IDE; when it goes quiet for the configured window, DevSpace either scales to zero (state preserved) or deletes — operator's choice per template.

04

Web terminal and SSH

Open a shell in the browser, or upload an SSH key and use `ssh user@bastion` from your editor of choice. SCP, port forwarding, and SFTP work out of the box.

How it works

From template to running IDE in seconds.

  1. Step 01

    Pick a template

    Jupyter, Marimo, Streamlit, Gradio, or VS Code — and any custom EnvironmentTemplate the platform team has authored.

  2. Step 02

    Get an isolated environment

    DevSpace boots a StatefulSet with your storage, libraries, and an oauth2-proxy sidecar. Only you can reach it.

  3. Step 03

    Idle = scale to zero

    When the IDE goes quiet, DevSpace stops it — state preserved — or deletes it. GPUs go back to the pool automatically.

Who it's for

Built for these teams

  • Data scientists prototyping on GPUs
  • Research teams sharing finite hardware
  • Platform teams done supporting one-off notebook servers