BigConfig package · Walter

Cloud dev environments,
standardized for your team.

Provision consistent, high-productivity dev boxes for every engineer on your team — on any infrastructure. Walter sets up the machine, installs the toolchain, clones your repos, and leaves a personalized environment your agent can manage.

Get started → View on GitHub

Like Google Cloud Workstations — on any cloud, with your team's software.

Any
cloud, any toolchain
1
command per box
Nix
reproducible toolchain
Yours
infra, data, bill
What you get

A team standard,
not a wiki page.

The BigConfig walter package codifies every decision — host specs, toolchain, dotfiles, repos, access — as a declarative Clojure config your team can clone, version, and ship to any cloud.

Any cloud

Hetzner Cloud, Oracle Cloud Infrastructure, or bring your own server. Swap providers in bb.edn — the dev environment stays identical.

One-command provisioning

`bb walter create` spins up the VM, runs Ansible, installs devbox, clones your repos, hands you a ready box. `bb walter delete` tears it down.

Reproducible toolchain

Declare your team's languages, runtimes, and CLIs once. Devbox installs them pinned and reproducible — identical across every engineer's box.

Personalized shell, by default

Doom Emacs, Zellij, Fish, Atuin — codified once, installed everywhere. New hires get the team standard the moment the box finishes provisioning.

Repos & worktrees pre-cloned

Your team's repositories arrive on the box with worktrees already set up for the branches you work on. No first-day dance to get to code.

Ansible-managed host

Users, SSH keys, firewall rules, base packages — every machine-level concern codified as a playbook, not a runbook in a wiki.

Walter vs Google Cloud Workstations

Same idea.
Different shape.

Cloud Workstations standardizes dev environments — on Google's terms. Walter does the same job on your infrastructure, with your software, on your bill.

Infrastructure
Cloud Workstations GCP only
Walter Any cloud — Hetzner, OCI, or BYO server
Pricing model
Cloud Workstations Per-seat, per-hour through GCP
Walter The cost of your own VM — no markup
Toolchain
Cloud Workstations Container images you build, push, and maintain
Walter Declarative devbox.json, Nix-pinned
Shell & editors
Cloud Workstations Whatever's baked into the image
Walter Doom Emacs, Zellij, Fish, Atuin — codified
Data residency
Cloud Workstations Google's regions
Walter Your provider, your region, your jurisdiction
Ops surface
Cloud Workstations GCP console, IAM, gcloud
Walter `bb walter` — agent-operable from a prompt
Lock-in
Cloud Workstations GCP-native configuration
Walter Portable bb.edn + Ansible, runs anywhere
Air-gapped / on-prem
Cloud Workstations Not supported
Walter Supported via BYO server
Deploy with your agent

Describe it.
Your agent writes the config.

Describe the team environment in plain English. Your agent refines the plan, writes a single bb.edn, and runs it.

You need to create a project to provision a cloud dev environment for your team.
This project contains only the `bb.edn` file.
The `bb.edn` contains the dependency https://github.com/amiorin/walter
You can download https://github.com/amiorin/walter to see how it works.
https://github.com/amiorin/walter is built on top of https://github.com/amiorin/big-config
All the options should be defined in the `bb.edn`.
Only the `walter` task should be created.
The compute provider is Hetzner with 8 GB RAM, 4 vCPUs, 80 GB disk.
Each team member gets a user with their SSH public key.
The devbox toolchain includes the languages and CLIs your team uses.
Your team's dotfiles repository is cloned into every user's home.
Your team's project repositories are cloned with worktrees for active branches.
Personalized environment includes Doom Emacs, Zellij, Fish, and Atuin.
You need to create the `.envrc` for HCLOUD_TOKEN — I will provide the value later.
How it works

Three steps from empty cloud account to working dev box.

  1. 01 — Describe

    Tell your agent what the team needs

    Which cloud, what size box, which toolchain, which repos. The agent turns the conversation into a single bb.edn.

  2. 02 — Provision

    Ship it to your infrastructure

    bb walter create provisions the VM, configures users and firewall, installs devbox, clones your repos, and hands you an SSH endpoint.

  3. 03 — Operate

    Hand ops over to the agent

    Upgrades, rebuilds, teardown — every runbook is a BigConfig workflow your agent can execute on behalf of the team.