Running SEES yourself
MIT-licensed, no database, and nothing to provision but an S3-compatible bucket. Why that matters more than a promise.
Verifiability beats assurance.
Every privacy product says it cannot read your data. The difference between a claim and a property is whether you can check. SEES is MIT-licensed and the full source is public, so the derivation, the storage path, and the share format are all inspectable rather than asserted.
An S3-compatible bucket. That is the dependency list.
There is no database to provision, no migration to run, and no account system to configure — consequences of a design that stores opaque blobs and keeps no user records. Point it at Storj or any S3-compatible bucket, set the environment variables, deploy.
It removes us from the delivery path.
Running your own instance addresses the sharpest limitation of browser-delivered encryption: that you are trusting whoever serves the JavaScript. Self-host and that party is you.
Read the self-hosting guide