Knapsack encrypts every file on your machine before it leaves. We store ciphertext, sizes and timestamps — nothing else. Drive it from the CLI, a sync daemon, or a plain HTTP API.
No AI features, no dashboards you never open. Knapsack does storage, sharing and sync — and does them the same way every day.
Content and file names are sealed before upload. The server sees an opaque blob, its length and a checksum — enough to store it, not enough to read it.
Files are split into 4 MB chunks and deduplicated per account. Re-uploading a 40 GB image after a one-line change moves a few megabytes.
Every upload has a session. Kill the process, lose the network, come back tomorrow — it continues from the last acknowledged chunk.
Hand a file to someone without an account. Set a TTL, a download limit and an optional passphrase; revoke it at any point.
The last 30 versions of every object are kept. Snapshot a whole prefix before a risky migration and roll the prefix back as one unit.
Point it at a directory and forget it. Bidirectional, conflict-preserving, and honest about what it is doing in the log.
A single static binary, no runtime to install. The same operations are available over HTTP with a scoped token, so CI can push artifacts without shipping your master key anywhere.
Every feature is on every plan. Egress is included up to twice your stored volume per month; past that it is €4 per TB.
No, and that is the point. Your key is derived locally with Argon2id and never transmitted. We can reset your login so you can see the object list, but the contents stay unreadable. Print the recovery code when you sign up and keep it somewhere physical.
Ciphertext blobs, their byte lengths, upload timestamps, an account identifier and the IP of the connection. File names, directory structure and content are sealed. We publish the object schema in the docs so you can verify what a stored record looks like.
Single-stream uploads saturate about 900 Mbit/s from a European connection; with four parallel streams the CLI reaches roughly 3 Gbit/s. Encryption is not the bottleneck — XChaCha20 runs at several GB/s per core.
Three European regions: Frankfurt, Helsinki and Amsterdam. Each object is written to two regions by default. Paid plans can pin storage to a single region if a policy requires it.
The account becomes read-only: you can list, download and delete, but not upload. That state lasts 90 days, we send two reminders, and only then is storage reclaimed.
25 GB free, no card, no sales call. Install the binary and push something in under a minute.