George Kapellakis

220 hours at 35 EUR/hour, against work that is already designed rather than open-ended development: a streaming cloud-to-cloud relay, so a transfer between two object stores stops round-tripping through the local disk; multiple sources into one destination; and three measured performance fixes announced publicly in August 2026. The designs exist and the commitments are public. They are unimplemented because blitcp is maintained outside working hours, which is the gap this request closes.

The Windows binaries are unsigned, so the first launch shows a SmartScreen warning that says nothing about what the program does, and every user has to click through it. A certificate removes that for everyone who downloads the tool. This is the single purchase users would actually feel.

The macOS builds — both the CLI and the desktop app, for Intel and Apple Silicon — are unsigned and unnotarised, so Gatekeeper refuses to open them until the user digs through Security settings. This is the same barrier as the Windows warning, on the other platform, and the membership is what makes signing and notarisation possible.

blitcp reads and writes arbitrary paths, can re-execute itself under sudo, handles SSH keys and cloud credentials, and preserves file modes across machines. Bugs in that surface are not cosmetic: past releases fixed a setuid bit carried from an untrusted remote and a reflink path that emptied files it was meant to copy. Both were found in-house; an outside reviewer looking at the credential and privilege paths is worth more than another regression test written by the person who wrote the code.

The benchmarks compare against cp, rsync, robocopy and TeraCopy on real drives — spinning disks, USB enclosures, SATA and NVMe SSDs — bought to be measured rather than rented from a cloud instance. A comparison is only worth something if the hardware under it is real.

The blitcp.dev domain and the edge worker behind the contact form and the update endpoint. The site itself is a static export and costs nothing to serve.

Pay whatever you like, once. Nothing about the tool changes either way: every feature stays free, the licence stays Apache-2.0, and donors get no separate build.