Persistent
Local environments pick up right where you left off. Cloud environments never stopped: kick off a job, close the laptop, and it's done when you sit back down.
Now in private beta
AI agents outgrow a laptop fast, and the usual workarounds are all plumbing. Declare a workstation in one file and Ringleader runs it anywhere, makes it feel local, and keeps every developer and agent on the same governed footing.
Declare the machine, the tools, and the AI agent your project needs, then apply the file. Ringleader builds the same workstation every time, on your laptop or in your cloud. Share the file with a teammate and they’re up and running in minutes. Give an agent exactly the right tools and access, and nothing else.
# my-workstation.yaml
apiVersion: workstations.ringleader.dev/v1
kind: Workstation
metadata:
name: my-workstation
spec:
image:
os: linux
distribution: debian
packages:
- git
- curl
devtools:
- name: nodejs
- name: claude-code
- name: vscode-web
ports:
- 8080"Works on my machine" is the most expensive sentence in software. Ringleader makes the environment itself persistent, reproducible, and shareable, for people and agents alike.
Local environments pick up right where you left off. Cloud environments never stopped: kick off a job, close the laptop, and it's done when you sit back down.
Every environment is defined in code, so it rebuilds identically on any machine: yours, a teammate's, or an agent's.
Agents get a real, first-class environment with the same guarantees a human developer has. No ephemeral sandboxes, no drift.
Hand your environment's definition to a colleague or an AI agent and they get the very same environment, rebuilt identically: no setup, no 'works on my machine'.
Spin up a ready-to-run workspace in minutes, not the days that onboarding and dependency wrangling usually take.
Isolated, auditable environments keep secrets inside the boundary, so what an agent does is reviewable, and what it can reach is up to you.
Describe your environment in a YAML file and apply it: declarative, just
like kubectl. It stays persistent, so you can close your laptop and pick up
where you left off, or share the file and a teammate or an AI agent gets the same
environment, rebuilt identically.
$ rl apply -f my-new-great-dx.yaml
workstation/my-new-great-dx created
$ rl apply -f my-new-great-dx.yaml
workstation/my-new-great-dx unchangedThe environments your developers already love grow into the control plane your organization needs.
Org-wide defaults with team and personal overrides, set in the same declarative config as everything else.
Every agent runs inside policy you control, with its own scoped, revocable credentials and a reviewable record of what it did.
Run the control plane in your own cloud, so code and state never leave your boundary.
Every change is declarative and versioned, so you can see what changed, when, and by whom.