Skip to content
pier pier

What is pier

pier gives every coding-agent session its own VM on your own AWS account. One command launches an EC2 instance and drops you into tmux inside it, with your repo on a fresh branch, your agents installed and authenticated, your MCP servers configured, and your dev environment built by the repo’s own setup script.

Detach and forget it. An in-VM supervisor parks the VM once the agent goes quiet. The instance stops, the disk persists. Attach again and it resumes in about 20 seconds with files, branches, and credentials exactly as you left them.

pier setup          # once: a short wizard sets up the account groundwork
cd ~/code/myapp
pier fix-login      # new session: your branch, your secrets, your dev env
pier proxy          # sessions as hostnames: the dev server at fix-login.pier:3000
pier                # the TUI: list, attach, create, resize, destroy

What it costs

Section titled “What it costs”
Session stateCosts
running~$0.04/h
parked~$3-4/mo (disk only)

Design in one paragraph

Section titled “Design in one paragraph”

There is no control plane. No server, no database, no daemon on your laptop. Session state lives in EC2 instance tags. Every byte between you and the VM rides ssh straight to it at line rate, with port 22 open to your IP only. Networks that block that path fall back to an SSM tunnel automatically. The VM never holds cloud credentials.

Where to go next

Section titled “Where to go next”