Ploink is built by one person: Petar Slovic, an independent developer in Niš, Serbia.
Who builds it
I’m Petar. I build and run about ten small web products, mostly on Cloudflare, and I ship them myself. Ploink is the tool I made for that work, and I use it every day.
You can find me on GitHub as @petarjs, where the Ploink source lives, and you can write to me at hey@ploink.dev. I read every email.
Why it exists
Each of my projects deploys with one command, but each one is a little different. Running them meant a terminal, a cd and a command, again and again. A self-hosted GitHub Actions runner helped until I kept hitting Actions limits, and I didn’t want to pay for CI just to run a command my laptop can already run. Meanwhile my coding agents were finishing fixes faster than I could ship them.
So I built a button: one big hold-to-deploy key per project, on my own Mac, in my own shell. Agents can ask to press it, and I approve by holding it.
How it’s made and paid for
- Open source. The core app is MIT-licensed and public on GitHub, so you can read every line that touches your shell before you trust it.
- No account, no telemetry. The app runs on your Mac and only goes online for the things the Privacy Policy lists.
- Funded by Ploink Pro. The core stays free. Ploink Pro is an optional one-time purchase, sold through Gumroad as the merchant of record. See the Terms of Sale and the Refund Policy.
- Built with AI help. I write Ploink with Claude Code, then review, test and use every change myself.
Contact
Questions, bugs and ideas: hey@ploink.dev. Bugs and feature requests are also welcome as GitHub issues. Please email security reports instead of opening an issue.
The seller’s full details are in the Legal notice: Petar Slovic, Konrada Zilnika 1, 18000 Nis, Serbia.