Skip to main content
Glama

DevEx is an open-source platform to spin up cloud-based development environments (REPLs) that work like your local setup β€” but in the browser, anywhere, anytime.

Built for flexibility, you can code in your preferred stack, connect over SSH, or run sessions with AI agents via our MCP server. We also support sandboxing AI-generated code securely, letting you test real changes in isolated environments.

Unlike Gitpod or E2B, DevEx is lightweight, self-hostable, and production-grade out of the box β€” with a developer-first CLI, seamless AI integration, and Kubernetes-native design for infinite scale.

πŸ“£ Want to add your own REPL template? It's easy! πŸ‘‰ Read the Contributing Guide to get started.


✨ Features

  • πŸ” GitHub OAuth authentication

  • πŸͺ„ Create, Start, Stop, Delete REPLs via Core API

  • πŸ’Ύ S3-backed file persistence

  • πŸ“¦ Kubernetes Deployments per REPL (Dynamic)

  • πŸ“‘ WebSocket-based Editor & Terminal

  • 🧹 Ephemeral containers for cleanup and sync

  • πŸ”’ HTTPS & TLS via Let's Encrypt & Cert Manager

  • 🎨 Beautiful Next.js + Tailwind frontend


Related MCP server: GibsonAI

βš™οΈ How It Works

graph TB User[πŸ‘€ User] --> Web[🌐 Web Frontend<br/>React/Next.js Application] Web --> Core[πŸ”§ Core Backend<br/>β€’ User Authentication<br/>β€’ Repl Management<br/>β€’ S3 Integration<br/>β€’ K8s Orchestration] Core --> S3[(πŸ—„οΈ S3 Storage<br/>username/repl-id/<br/>β”œβ”€β”€ templates/<br/>└── user-files/)] subgraph K8sCluster["☸️ Kubernetes Cluster"] direction TB IngressController[πŸšͺ Ingress NGINX Controller<br/>Traffic Routing] CertManager[πŸ”’ Cert Manager<br/>TLS Certificate Management] subgraph ReplResources["πŸ“¦ Per-Repl Resources"] Deployment[πŸš€ Deployment<br/>Repl Container Instance] Service[πŸ”— Service<br/>Internal Network Access] Ingress[🌍 Ingress<br/>External Access Route] end subgraph Pod["🏠 Repl Pod"] MainContainer[🐳 Runner Container<br/>β€’ WebSocket Server<br/>β€’ File Operations<br/>β€’ PTY/Terminal Access<br/>β€’ Code Execution] EphemeralContainer[⚑ Ephemeral Container<br/>File Sync Back to S3<br/>πŸ”„ Cleanup Process] end Deployment --> Pod Service --> Pod Ingress --> Service IngressController --> Ingress end Core --> K8sCluster Core -.->|Create Resources<br/>Deploy β†’ Service β†’ Ingress| ReplResources Web -.->|πŸ”Œ WebSocket Connection<br/>β€’ File Management<br/>β€’ Terminal Access<br/>β€’ Real-time Collaboration| MainContainer Core -.->|πŸ“ Copy Template<br/>to user directory| S3 EphemeralContainer -.->|πŸ’Ύ Sync Files Back<br/>Before Cleanup| S3 MainContainer -.->|πŸ“‚ Load Files<br/>on Session Start| S3

πŸŒ€ Session Lifecycle

sequenceDiagram participant U as User participant W as Web Frontend participant C as Core Service participant K as Kubernetes participant S as S3 Storage participant R as Runner Container U->>W: Create New Repl W->>C: POST /repl/create C->>S: Create user directory<br/>Copy template files U->>W: Start Session W->>C: POST /repl/start C->>K: Create Deployment<br/>Service & Ingress K->>R: Initialize Container R->>S: Download files R->>W: WebSocket Connection Note over U,R: Development Session Active U->>R: File operations via WebSocket R->>R: Real-time file editing U->>W: Close Session W->>C: POST /repl/stop C->>K: Inject Ephemeral Container K->>S: Upload modified files C->>K: Delete Resources

πŸ”© Key Components

apps/web/ – Frontend

  • Built with Next.js + Tailwind CSS

  • GitHub OAuth login

  • GUI for File Tree, Editor, Terminal

  • WebSocket hooks to interact with Runner

apps/core/ – Backend API

  • Written in Go

  • Handles user auth, S3 ops, Kubernetes deployments, cleanup

  • Redis for REPL session state

  • πŸ“„ See apps/core/README.md for detailed architecture & deployment steps

apps/runner/ – REPL Runtime Container

  • Lightweight Go server

  • WebSocket API for:

    • File tree and file content access

    • Terminal (PTY) sessions

  • πŸ“„ See apps/runner/README.md for event list and package internals

infra/k8s/ – Kubernetes Bootstrap & TLS

  • Contains:

    • Ingress-NGINX setup

    • cert-manager + Let’s Encrypt for auto TLS

  • πŸ“„ See infra/k8s/README.md for full setup instructions

templates/

  • Base folders (e.g. Node.js, Python) copied on REPL creation

  • Language-specific dockerized scaffolds

  • πŸ“¦ Want to add your own template? See the Contribution Guide


🧱 Infrastructure

  • ☸️ Kubernetes cluster for REPL pods

  • πŸ”’ Cert Manager + Let’s Encrypt for TLS

  • πŸ—ƒοΈ S3-compatible storage for persistence

  • 🐳 Docker images for runtime environments

  • βš™οΈ Redis for in-memory session tracking


πŸ“¦ Deployment Flow

  1. User logs in and creates a REPL

  2. apps/core/ copies a template into username/repl-id/ on S3

  3. apps/core/ deploys a pod, service, ingress in Kubernetes

  4. apps/runner/ connects via WebSocket and serves FS + Terminal

  5. On session end:

    • Ephemeral container uploads updated files to S3

    • All K8s resources are cleaned up


πŸ’» Tech Stack

Layer

Stack

Frontend

Next.js, Tailwind, WebSockets

Backend

GoLang (Echo/Fiber), Redis, S3 SDK

Runner

GoLang + PTY + WebSocket

Orchestration

Kubernetes, Docker, Docker Swarm

Networking

Ingress NGINX + cert-manager

Auth

GitHub OAuth


πŸ“„ Per-Component Docs

πŸ“š For deeper implementation details:


🧠 Why I Built This

β€œThis project is my deep dive into Cloud Infrastructure, DevOps, and FullStack Engineering β€” wrapped in a real-world application.” β€” Parth Kapoor


🌐 Demo & Links


🀝 Contributing

This project is under active development. Want to contribute a template, fix, or feature? Start here πŸ‘‰ CONTRIBUTING.md

Pull requests, suggestions, and feedback are always welcome!


πŸ“œ License

Licensed under the MIT License

-
security - not tested
A
license - permissive license
-
quality - not tested

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ParthKapoor-dev/devex'

If you have feedback or need assistance with the MCP directory API, please join our Discord server