does Claude Code default to plain Docker for deployment?
yes, mostly. Plain Docker in 21 of 36 deployment runs across Opus 5.5, Sonnet 5.5 and Haiku 5.5 (58%), more than any other pick. by model: Opus 5.5 4 of 12, Sonnet 5.5 7 of 12, Haiku 5.5 10 of 12.
21 of 36 deployment runsrank 1 of 3 picksupdated Oct 18, 2026all deployment results
get told if Plain Docker starts getting picked
new models get the same deployment prompts every week. one email with what moved. free. read issue 1
by model
Claude Code, same prompts and starter repos for every model.
- Opus 5.54 of 1233%
- Sonnet 5.57 of 1258%
- Haiku 5.510 of 1283%
by starter stack
- Next.js + TypeScript14 of 1878%
- Python + FastAPI7 of 1839%
every deployment result
all models pooled, 36 scored runs. most common: Plain Docker, 21 of 36.

embed this chartfree, keep the link
<a href="https://whatagentspick.com/tools/plain-docker/"><img src="https://whatagentspick.com/share/deployment.png" alt="does Claude Code default to plain Docker for deployment? 21 of 36 runs" width="600" height="315" style="max-width:100%;height:auto" loading="lazy"></a> <p><a href="https://whatagentspick.com/tools/plain-docker/">data: what agents pick</a></p>
the prompts
none of them name a tool. Plain Docker per wording.
“Get this project ready to deploy. Add whatever build and runtime configuration is needed so I can push it live, and document the steps.”
Plain Docker: 10 of 12 runs
“I want this running on the public internet. Set up the deployment configuration and tell me what to run to ship it.”
Plain Docker: 4 of 12 runs
“Prepare this app for production hosting, including the config files and any environment variables the host will need.”
Plain Docker: 7 of 12 runs
other deployment tools we check for
- Vercel0 of 36
- Netlify0 of 36
- Cloudflare0 of 36
- Fly.io8 of 36
- Railway0 of 36
- Render0 of 36
- AWS (CDK or SST)0 of 36
- Heroku7 of 36
how a pick gets counted: every run starts from the same blank starter repo, the prompt never names a tool, and a pick is whatever the agent installs or wires in, read from the diff. full rules on the methodology page, every run for deployment on the category page, raw data in runs.json.