Compared
Sometimes another tool is the right answer.
s3nd sits between three kinds of tools: code-based file transfer, file sharing for people, and local-first sync engines. Each page describes the other tool in its own terms first, then where the two part ways, and says plainly when to pick it.
01Command-line file transfer
Tools that move a file between two machines with a code. The closest cousins of the CLI.
02File sharing for people
Upload, get a link, send it to someone. Products first, primitives second.
Proprietary
s3nd vs WeTransfer
A WeTransfer alternative that keeps the file in your own bucket
MPL-2.0
s3nd vs Firefox Send
A Firefox Send alternative that needs nothing deployed
GPL-3.0
s3nd vs PairDrop
A PairDrop alternative for when the other device is not in the room
MIT
s3nd vs transfer.sh
A transfer.sh alternative with no service to run
03Local-first sync engines
Continuous, multi-user synchronization between a client database and a backend. A different, bigger job.
Proprietary service; the client addon is open source
s3nd vs Dexie Cloud
A Dexie Cloud alternative for apps that have no accounts
Client SDKs Apache-2.0; the service is source-available
s3nd vs PowerSync
A PowerSync alternative when there is no backend database
Apache-2.0
s3nd vs ElectricSQL
An ElectricSQL alternative for apps without Postgres
Source available; Zero is Apache-2.0
s3nd vs Replicache
A Replicache alternative for one-shot moves rather than multiplayer
Apache-2.0
s3nd vs PouchDB
A PouchDB alternative that does not need a CouchDB
Proprietary service; SDKs Apache-2.0
s3nd vs Firebase
A Firebase alternative for local-first apps that keep their data
04Storage tooling
General-purpose tools for talking to a bucket. Broader than s3nd, and without the code.
Put a file. Hand over the code.
Point it at the bucket you already pay for. Nothing to deploy, nothing to sign up for, nothing in the middle.
npm install -g @s3nd/clis3nd init --provider r2 --bucket drops3nd put ./anything.zip