Ship it.
From where you built it.

You built the feature. Tested it locally. Ran the Doctor. It's ready to ship. Now you need to: commit, push, open the Railway dashboard, trigger a deploy, wait for the build log, and hope the environment variables match. Or you SSH into your VPS, pull the code, restart the service, and pray.

Donk manages the entire deploy flow. Pick a target — Railway, Vercel, Fly.io, Render, or SSH/rsync to your own server. Configure credentials once. From then on, deploy is one click. Pre-deploy hooks run migrations, build assets, run tests. Post-deploy hooks notify Slack or tag a release.

• SSH/rsync — direct file sync to any server. rsync bundled with Donk.
• Railway — deploy via the Railway CLI. Build packs or Docker.
• Vercel — push to Vercel with framework detection.
• Fly.io — deploy to Fly machines via the Fly CLI.
• Render — push to Render with auto-detection.
• Pre-deploy hooks — run tests, build, migrate before pushing
• Post-deploy hooks — notify, tag, clean up
• Deployment history with timestamps and status
• CLI access — donk deploy my-api --target railway