blixtOne-shot sends, zero ceremony
No device pairing, no shared-folder config, no teardown afterwards. A 12-word code, a 6-digit check, and the file moves.
Comparison
Blixt vs Syncthing
Syncthing is one of the best pieces of software in its category: free, open source, continuously syncing folders between your own devices with no central server, backed by a huge community. Blixt solves a different problem — sending a file once, to a specific person. Here is where each one fits.
| Syncthing | Blixt | |
|---|---|---|
| Built for | Continuous folder sync between your own devices | One-shot transfers: file → code → receiver |
| Price | Free and open source | Free plan; flat paid plans |
| “Send this file once” | No dedicated flow — you create a shared folder, exchange device IDs, accept the share, then tear it down | The core flow: drop a file, read a code out loud, done |
| Receiver setup | Install, exchange device IDs, accept the folder, pick a path | Type the code and compare six digits — or open a bCloud share link in a plain browser |
| MITM verification | Device IDs are certificate fingerprints you exchange up front | Fail-closed certificate pinning plus a 6-digit SAS compared out of band |
| Resume after a drop | Yes — block-level sync picks up where it left off | Yes — missing chunks only, verified against a MAC-protected journal |
| Works with no internet | Yes — local discovery on the same LAN | Yes — LAN mode uses no signaling server at all |
| Interfaces | Browser GUI on localhost, plus community wrappers | Desktop GUI, local web UI, and CLI on one core |
| Support | Community forum | Priority support on the Max plan |
Credit where due
Where Syncthing is the better choice
- Keeping folders continuously in syncacross your own machines. That is Syncthing’s actual job, and Blixt does not do it — there is no continuous sync or watch-folder mode in Blixt today.
- A mesh of many devices — laptops, a NAS, headless servers, an Android phone — all holding the same data set.
- Data that changes constantly. Block-level sync ships only the changed parts, every time they change.
- Running everything yourself, with no accounts anywhere. Syncthing needs no sign-in of any kind.
And it’s free and open source.Syncthing’s code is public, reviewed by a large community, and has years of production use behind it. Blixt’s code is not public. If continuous sync between your own devices is the job, use Syncthing — it is excellent at it.
The other direction
Where Blixt wins
Non-technical receivers
Your counterpart gets a desktop app, a local web UI, or — via a bCloud share link — just a browser tab on any device.
Verification out of band
The code is derived from the TLS session itself. Matching digits prove nobody sits in the middle — including a compromised signaling server.
Built for the big single file
Parallel streams, Multiconnect link bonding, and resume from verified blocks — plus priority support on the Max plan and bCloud storage when you need them.