Deploy via SSH/rsync with dry-run preview, revision backups, and pre/post hooks. Or push to Railway, Vercel, Fly.io, Render — directly from Donk.
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.
For developers who deploy to their own servers, Donk's SSH/rsync deploy is a complete pipeline — not a wrapper around a CLI you could run yourself.
Before anything touches the server, Donk runs a dry run. You see exactly which files will be created, modified, or deleted — in a visual preview dialog with file sizes and change types highlighted. You review. You approve. Then the real deploy runs.
Every deploy creates a revision backup on the remote server — a compressed archive of the previous state. Something went wrong? Roll back to any previous revision from the revision manager. Up to 5 revisions kept by default, configurable per profile.
donk deploy my-api --target railwayVideo: 40–50 seconds. Dry-run preview showing file changes. Approve. Watch the deploy with pre/post hooks. Revision backup created. Deploy success.