New engineer at 9am. Shipping by 10.
Pick a template, get an owner-scoped dev workspace on your own cluster, and land in a browser IDE or an in-pod terminal — already wired to your remote execution, with the agent CLIs installed. No laptop setup, no per-repo devcontainer archaeology, and no cost while it sits idle.
Onboarding time is a tax on every hire.
And it is paid again on every laptop refresh, every toolchain bump, and every engineer who switches teams.
The setup document is always out of date, because the only thing that keeps a setup document accurate is someone repeatedly suffering through it. Meanwhile the environment that matters — the one where the build actually reproduces — lives on a cluster, not a laptop.
Modelling a dev environment as a Kubernetes resource collapses the gap. A template is a WorkspaceConfig; an environment is an owner-scoped DevWorkspace reconciled into a StatefulSet with a persistent home. It's inspectable, forkable, and identical for the tenth hire and the first.
Pick → provision → route → land.
Nothing in this sequence requires a ticket, an admin, or a working laptop.
Pick
Choose a WorkspaceConfig in the console. The facade writes an owner-scoped DevWorkspace CR with a random adjective-animal name — spec.owner is your identity, and it's immutable.
Provision
The operator reconciles it into a StatefulSet, a persistent home volume, a headless Service, and a per-workspace Secret, mounting the template's rendered files read-only at /etc/fastverk/config.
Route
ws-proxy authenticates your session against spec.owner and routes the subdomain to the pod. Your credentials are stripped before they reach it.
Land
You're in a browser IDE or an in-pod terminal, already pointed at your remote execution, with the agent CLIs a click away.
A card per workspace.
Its template, its phase, its URL — and a launch button per provisioned tool. Values illustrative.
| workspace | template | phase | url |
|---|---|---|---|
| spurious-racoon | default | Running | spurious-racoon.ws.fastverk.com |
| brave-otter | rust-bazel-rbe | Provisioning | — |
| quiet-lynx | default | Suspended | resumes on access |
The environment is the artifact.
Not a document describing how to recreate it.
A dev environment is a Kubernetes resource — owner-scoped, template-driven, and scale-to-zero when idle.
Backed by shipping plugins.
Each claim on this page is anchored to a plugin that provides it. The site build resolves these cross-references against the live feature catalog and fails if one of them doesn't exist — so this list can't quietly outlive what the platform ships.
An owner-scoped DevWorkspace from a reusable WorkspaceConfig template, composed from version-pinned tool layers, booting RBE-ready with the agent CLIs built in and scaling to zero when idle.
plugin detail →Resolves the workspace subdomain to the right pod behind one wildcard, gates on session plus ownership, and proxies HTTP, IDE WebSockets and SSH-over-WebSocket — no per-workspace DNS, cert, or Ingress is ever minted.
plugin detail →On day zero nobody knows which repo a thing lives in. Semantic search over the whole forge returns code units with a deep-link to the exact lines.
plugin detail →Read history, refs and file trees across every mirrored repo without cloning any of them first.
plugin detail →Adjacent problems.
Some estates can't send their build plane to a vendor. The whole platform launches into your own AWS account instead.
Read more →Turning agents on is a one-line change. Deciding what they may touch, whose authority they carry, and how you stop them is the actual project.
Read more →Prove it's safe to merge.
Hosted, or launched into your own AWS account. Start free — no card required.