coming soon // early access

Dev containers in Kubernetes. Indistinguishable from local.

Point your IDE at a devcontainer.json. Fifteen seconds later, you're coding in the cloud.

terminal

❯ helm install elmsfire ./charts/elmsfire

⚙ provisioning service deployed

⚙ auth gateway configured

✓ ready in 47s

❯ elmsfire open --ide code myproject

pulling image... (3s)

✓ workspace ready — VS Code connected

Features

Built for developers who care about feel

Local input prediction and protocol optimization. Indistinguishable from local.

VS Code, JetBrains, or Zed. All extensions, themes, keybindings. No browser IDE.

No Terraform. No platform team bottleneck. Drop a config in your repo and go.

Aggressive image pre-warming and layer caching. Warm workspaces in under 15 seconds.

Fewer than 10 config values. Zero to running in under an hour.

Code never leaves your VPC. SSO/OIDC. Audit logs. Image policies.

Continuous background sync. Lose connectivity? Automatic local failover.

elmsfire migrate gitpod converts .gitpod.yml to devcontainer.json. Minutes, not days.

How it works

Clone or open any repo with a devcontainer.json. Works with VS Code, JetBrains, Zed, or any SSH-capable IDE.

$ git clone myproject && code myproject

Elmsfire detects your dev container config and prompts you. One click to launch in the cloud.

→ "Open in Cloud Dev Container?" → Yes

15 seconds later, you’re in a container on your company’s Kubernetes cluster. Same IDE, same extensions, same everything.

✓ workspace ready — connected via SSH

Comparison

We're building the simplest way to run dev containers in Kubernetes. Join the waitlist to be first in line when we launch.