/dev/null
Sign in

Commit

83b4f6a

al mokhtar@almokhtarbr
Tired of paying the "Heroku tax" but hate vendor lock-in? (https://railyard.run/) I built Railyard to give you that same seamless PaaS developer experience, but it deploys full-stack apps and databases directly onto servers you own (DigitalOcean, Hetzner, Vultr). Why switch? •…
RailyardRailyard: deploy full-stack apps to servers you ownDeploy your frontend, backend, Postgres, Redis and workers to servers in your own DigitalOcean, Hetzner or Vultr account. Flat price per team, no markup on compute.
Chris Dossman@lemoz
Your MCP docs say deploy_app builds the latest commit. Can it target a specific SHA? With multiple agents working in parallel, I’d want to deploy the exact revision that was reviewed, even if another commit landed in the meantime.
al mokhtar@almokhtarbr
Yes, as of today. deploy_app takes an optional ref: a full commit SHA, a tag or a branch. Railyard builds exactly that revision, even if newer commits landed on the branch since it was reviewed: deploy_app { "app": "my-app", "ref": "3f2a9c1d4b5e6f708192a3b4c5d6e7f8091a2b3c" } Without ref it still builds the latest commit. The same deploy-approval rules and rate limits apply, and the deploy record shows the exact SHA that went out, so you can check what each agent shipped. Same thing outside MCP: CLI: railyard deploy my-app --ref <sha> API: POST /api/applications/:id/deploys {"ref": "<sha>"} Docs: https://railyard.run/docs/mcp I tested it by having Claude drive the MCP and deploy a specific older commit on a live server. Happy to jump on a quick call and walk through https://app.railyard.run/book
RailyardMCP for AI agents · Docs · RailyardLet Claude Code, Cursor or any MCP client list, inspect, deploy and restart your apps with a scoped token. Destructive actions wait for a human.

commit 83b4f6a