Skip to content
TAIP

Products / For AI builders

ConsoleX

Available

Log in, get a governed Kubernetes workspace. No kubectl, no tickets.

ConsoleX gives every user on a shared Kubernetes cluster a curated, web-based workspace: a private namespace, a ResourceQuota, a default-deny NetworkPolicy, and full self-service over their own workloads, storage, configuration, and networking. Quota templates propagate live, and a dual reconciliation loop — event-driven watches plus periodic full sync — repairs any drift within seconds. Power users graduate to kubectl with a generated per-user OIDC kubeconfig.

All products

Specification

Version
v1.6.5 — generally available
Surface
Pods · Deployments · Jobs · CronJobs · PVCs · Services · HTTPRoutes · ConfigMaps · NetworkPolicies · YAML
Identity
OIDC SSO · back-channel logout · per-user kubeconfig
Reconcile
Event-driven watches + periodic full sync — drift repaired in seconds
Scheduling
Kueue queues · hold / resume / cancel · GPU-hours & cost per namespace
Languages
English · 简体中文 (UI and docs)

Proof, not promises

See it in one block.

No proprietary SDKs, no rewrites — ConsoleX meets your tools where they already are.

first login, fully provisioned 
# alice signs in with SSO — ConsoleX provisions her workspace
namespace      cx-alice                          created
resourcequota  gpu-small (8 CPU · 32Gi · 1 GPU)  applied
networkpolicy  default-deny                      enforced
rolebinding    alice → admin of cx-alice         granted
# drift is repaired within seconds — watches + periodic sync▌

No manual provisioning, no custom RBAC. Admins define a quota template once; ConsoleX enforces it forever.

Capabilities

What ConsoleX gives you

01

Per-user workspace, automatically

On first OIDC login, ConsoleX creates a namespace, applies a quota template, and grants the user admin of their own namespace — no manual provisioning, no tickets, no custom RBAC.

02

Run workloads from the browser

List, create, scale, restart, and debug Pods, Deployments, StatefulSets, Jobs, and CronJobs. Stream logs. Open an in-browser shell. Browse PVC files. Reach in-pod web UIs through a transparent HTTP proxy — no Service, no port-forward.

03

Quotas that hold

Quota templates propagate live to every linked workspace. Event-driven watches plus a periodic full sync repair drift in ResourceQuotas and NetworkPolicies within seconds — even after accidental deletion.

04

Built to integrate

OIDC SSO with back-channel logout. Namespace sharing for collaboration. Grafana deep-links on every namespace and pod page. An append-only audit log records every mutating action, and an internal API gives DevSpace, TrainX, and InferX tenant context — there is no second way to be a tenant.

How it works

From login to workload in three steps.

  1. Step 01

    Sign in with SSO

    Users authenticate against your OIDC provider. Group membership decides what they can do.

  2. Step 02

    Workspace appears

    ConsoleX provisions a namespace, applies the quota template, and grants the user admin of their own space.

  3. Step 03

    Self-serve everything

    Run pods, mount PVCs, expose services, edit YAML — within quota, within policy, no kubectl required.

Who it's for

Built for these teams

  • Researchers and engineers on shared GPU clusters
  • Platform teams replacing kubectl-everywhere with safe self-service
  • Admins who want quotas and policy without writing custom RBAC

Pairs well with

Other builder products

DevSpace

 Available

Jupyter or VS Code on a GPU in seconds. Idle environments shut themselves down.

Single-click Jupyter, Marimo, Streamlit, Gradio, and VS Code environments — GPU-ready, isolated per user behind a per-pod auth proxy, with SSH access and idle shutdown by default.

Learn more

TrainX

 Available

Admins write the template. Users fill a form. Kubernetes runs the job.

Self-describing training templates render straight into UI forms — with live quota checks, streaming logs, parsed progress bars, and one-click TensorBoard.

Learn more

ModelSphere

 Available

Your own Hugging Face Hub. Change one env var — every client just works.

A self-hosted, HF-compatible model and dataset registry: transformers, datasets, huggingface-cli, and git-lfs work unchanged — plus a browsable Hub UI with model cards, file viewer, and commit history, OIDC, audit, quotas, and pull-through caching of the public Hub.

Learn more