Fast owner-held copies
Keep working sets on a phone, laptop, workstation, NAS, or home server according to device role.
Daemonet Storage
Your files do not need one forever-home.
Build resilient storage from devices and locations you choose using client-side encryption, authenticated chunks, replication, sharding, integrity verification, resumable transfer, and policy-driven placement.
Pocket Dimension
Storage assembled from places you choose.
Keep full copies on trusted personal devices where that makes sense. Place encrypted replicas or independently useless shards where trust is limited. Reconstruct only on an authorized device that possesses the required keys and policy.
The stable identity of a collection survives a replaced disk, laptop, provider, or host. Placement is a customer policy—not an invisible provider decision.
Encrypted remote copies
Preserve authenticated ciphertext across independent locations and resume safely after interrupted transfer.
Separate trust
Split content into verified pieces so a storage participant need not possess a useful copy of the whole.
Detect silent damage
Authenticate chunks and manifests, audit availability, and distinguish a present object from a correct one.
Restore redundancy
Recreate missing pieces from authorized sources before a second failure collapses the recovery threshold.
Prove reconstruction
Exercise recovery on clean hardware and compare the restored content to the signed expected manifest.
Policy-driven placement
Different devices can do different jobs.
A photographer may use a phone as an ingest cache, a laptop as the working archive, a home server as a full replica, and an untrusted provider as encrypted recovery capacity. The collection remains one authority-controlled system.
Encrypt locally
Chunk and authenticate content before any untrusted capacity receives it.
Place by policy
Choose full replica, shard, cache, archive, retention, geography, and repair responsibility explicitly.
Audit continuously
Challenge storage roles for the exact evidence required without asking them to decrypt the object.
Restore deliberately
An authorized device retrieves enough verified material, reconstructs locally, and records the recovery result.
Cryptographic boundary
“Encrypted” does not mean immortal, anonymous, or safe from a compromised authorized endpoint. Protect keys, keep enough independent pieces, rotate revoked recovery authority, and test that the system can restore without 1Man or one provider.
Assume a device will disappear