Encrypt before
it leaves.
Content, filename and file type are encrypted in your browser by default. Storage nodes receive encrypted bytes. You keep the recovery key.
Open source. Yours to grow.
Your files.
More than one
way home.
Encrypt in your browser. Keep copies on nodes you trust, or split a file into recoverable parts. Stay in control when a host goes offline.
Public preview · Bring your own storage and signer
Encrypted first. Distributed by you.
- Your storage
- Your signer
- Open protocols
- No Wildbloom account
01 / Take ownership
A file deserves more
than a fragile link.
A disk fails. A service closes. A link stops working. Wildbloom helps you decide where your files live, who can read them, and how to bring them back.
Encrypt before
Give your file
another way back.
Keep complete copies or recoverable parts on separate nodes. Choose a layout that can survive losing a host.
Choose the people.
Choose the places.
Use your own machines or storage from trusted operators. Your signer approves actions; Wildbloom never asks for your private signing key.
A file’s way home
A little room for
the unexpected.
See how encryption and recoverable parts give a file more than one way home.
Read the story instead
- Your files. More than one way home. An encrypted file sits among four storage nodes. A little room for the unexpected.
- Private before it leaves. Your browser encrypts the file. Storage nodes receive encrypted bytes. Your key stays with you.
- Spread the parts. Keep your options. Choose nodes you trust. In this illustrated 2-of-4 layout, each of four nodes receives a different part. Any two parts can rebuild the encrypted file.
- Two nodes offline. Still a way back. Nodes 2 and 4 go offline. The parts on nodes 1 and 3 remain available. Recover from those parts with your saved receipt and recovery key, then verify the result.
- Keep your key. Keep your way home. Save the signed recovery receipt. Keep the recovery key separately. Wildbloom is a public preview. Bring your own storage.
This film illustrates recovery; it is not a live storage test. Choose independent nodes and keep your receipt and key safe. The example below lets you try the same recovery threshold.
02 / Make room for failure
One node goes away.
Your file needn’t.
Replication keeps complete encrypted copies. Sharding with erasure coding creates parts that can rebuild the file, even when some are missing.
Try taking nodes offline in this example. Any two of the four parts are enough to recover.
Build your own storage poolA little room for the unexpected
Interactive example2 of 4
parts needed
to recover
Tap a node to take it offline or bring it back.
Your file can come home.2 parts available. Enough to recover.
An illustration, not a live storage check. Recovery also needs your saved receipt and recovery key. Nothing is uploaded or contacted here.
Choose independent machines and locations: nodes sharing a disk, power supply or connection can fail together. Pool storage is a preview. Understand recovery and its limits ↗
03 / From file to safe return
A few deliberate steps.
A clear route back.
- 01
Prepare it locally
Choose your file and storage layout. The browser encrypts it. Save your recovery key somewhere safe.
- 02
Choose where it lives
Approve uploads with your signer. Encrypted bytes go to your chosen Blossom nodes, with hashes checked on read-back for pools.
- 03
Keep your route home
Save the signed file event or private pool receipt. Keep the recovery key separately. You need both to recover.
- 04
Recover. Verify. Repair.
Retrieve and decrypt locally. Restore lost redundancy in the browser, or explicitly enable the separate owner repair service.
Built on open protocols.
Blossom stores the bytes. Nostr carries signed file pointers when you choose to publish them. Pool receipts stay private. Optional WebTorrent offers another delivery path.
Read the protocol ↗04 / Know your storage
Trust your people.
Verify your bytes.
Keep a node for yourself, or offer a bounded share of its capacity at terms you set. Buyers choose and pay the person running that node directly. ForgeSworn supplies the software; it does not operate the storage service or hold customer balances.
Find trusted nodes
Discover signed recommendations from people you choose. Review a node before contacting it.
Find a nodePay the operator directly
Review the allowance, term and refund policy. Supported operators accept Lightning or LNURLcash; Wildbloom holds no customer balance.
Explore storage offersCheck your file is there
A fresh full-read audit verifies current retrievability. It cannot promise continuous custody or future availability.
Recover and verify05 / Make it yours
Start in a browser.
Put down your own roots.
Wildbloom is the browser client. Wildbloom Node is the home for your encrypted bytes. Use them together, or bring an existing Blossom server.
No install.
No Wildbloom account.
Bring a trusted storage node and Nostr signer. Source files up to 256 MiB. This website does not store your files.
Open the client Already have a receipt? Recover a file →A home for
encrypted bytes.
A desktop tray app with storage, pool health and owner repair controls. Use your HTTPS setup or optional Tor.
macOS 0.3.5 preview · signed & notarisedWindows & Linux 0.3.3 preview · Windows unsignedMac 0.3.5 includes optional checkout and storage audits; Windows and Linux downloads are the earlier 0.3.3 preview. Trusted automatic updates remain open. Prefer to build from source? ↗
A few things to know
Clear expectations.
Better decisions.
A public preview for people who want more control over their files. Keep an independent backup of anything irreplaceable.
Is Wildbloom ready for my only copy?
Keep another backup. Encrypted storage, recovery and repair have automated acceptance coverage. A private Archipelago test node has passed real LNURLcash purchase, renewal, automatic full refund, restart and paired backup restore. Independent security review, broader physical-device testing, live reference-mint payment and independent operator deployment acceptance remain open.
Read the acceptance evidence ↗Can I sell storage from Archipelago?
Yes, as an opt-in public preview. Your own uploads default to your node, and you decide how much capacity stays reserved for you and how much to offer. You set the price, duration, grace, delivery, refund terms and payment receiver. Buyers pay you directly. ForgeSworn provides the software; it does not run your node, list sellers, set terms, collect payments or provide the storage service.
Read the operator runbook ↗Can a storage node read my file?
With encryption enabled, nodes receive encrypted content, filename and file type. Your separate recovery key unlocks the file. Connections still reveal metadata such as timing, byte counts and, in direct mode, IP addresses. Optional Tor reduces address exposure; it does not remove every clue.
Understand the privacy boundary ↗Can I keep the whole file off every node?
Choose erasure-coded sharding. Upload and repair send each storage node only its assigned part. Reconstruction happens in your browser or separate owner repair service. Encryption protects the contents; splitting alone does not prevent operators combining parts or fetching other parts if they obtain your receipt.
Does repair happen automatically?
You can explicitly enable a separate owner repair service in Wildbloom Node. It works on encrypted bytes without the recovery key, but needs enough surviving parts, an external signer and approved storage destinations. Repair authority expires and needs approval again after restarting the app. Free-capacity discovery, draining and cluster-wide rebalancing are not available.
Set up owner repair ↗What do I need to recover a file?
Your signed file event or private pool receipt, the separate recovery key, and enough available verified bytes or parts. Save the record and key before closing the browser. Extra copies cannot replace a lost recovery key. Ordinary file recovery needs no signer.
Open file recovery →Files that outlive their host.
Let your files
put down roots.
Try Wildbloom Open source · MIT licensed · Made by ForgeSworn
Browser client
Publish or retrieve a file
This site stores nothing. Files go from your browser to storage you choose. Bring a trusted Blossom server or run Wildbloom Node. There are no default servers or relays.
Files are encrypted locally by default. Signing keys stay in your browser signer or external signer; never paste a private key here. Connections and public events still reveal metadata. Each network action needs your go-ahead.
Publishing? Choose your storage, connect a signer, then prepare your file.
Recovering? Start with your saved event or receipt. Ordinary file recovery needs no signer.
01
Choose your infrastructure
No endorsed defaults. You decide which services learn about the file.
Use Tor Browser rather than SOCKS-proxying a normal browser. Wildbloom cannot prove that this browser is using Tor; an ordinary browser lacks Tor Browser's fingerprint protections and may not provide Web Crypto on HTTP onion origins. Tor-only mode refuses clearnet endpoints and disables WebRTC, but a NIP-07 add-on or reused Nostr key can still fingerprint or identify you.
One node holds the encrypted file. Keep a separate backup: this layout has no redundancy.
Pool files are always encrypted. Split mode sends each node only one coded part; reconstruction and repair happen in your browser or an explicitly configured owner repair service. Operators may collude or fetch other parts if they learn their addresses. Encryption protects the contents. Keep the signed pool receipt privately alongside a separate recovery key; pool receipts are not published to relays or swarms.
Inspect the file to validate placement. Extra failure groups provide spare destinations. A signed receipt describes intended placement; only verified reads count as stored parts. Keep the receipt even if an upload is interrupted.
Peer mode has no hidden public STUN or TURN default. That avoids an undeclared third party, but peer connections may fail across networks until an operator-controlled ICE policy is reviewed and configured.
+
Find nodes, buy storage and verify storage
Each action is separate. Discovery is a recommendation, payment buys an allowance, and a storage check verifies current retrievability.
Discover recommended nodes
Results come from signed Blossom server lists published within 30 days. A recommendation does not prove ownership, capacity or independent failure domains. Nodes are contacted only after you choose an action.
Find public paid storage and free shelter
Your chosen relays learn that you are looking for storage services. Listings are signed operator claims, not recommendations or proof of uptime. Storage nodes are contacted only when you load a selected service’s current terms.
Free shelter accepts signed mirrors from an existing source. It is best effort and evictable; it does not permit unknown direct uploads. Paid storage still requires a fresh private quote and separate payment consent.
Buy storage directly from this node
Uses the Blossom server selected above. Lightning and LNURLcash are paid directly to its operator. Checkout is currently available in direct mode only; external wallets have their own network behaviour.
When the selected node advertises refund support, this address is bound privately into the quote and lets the operator return the exact LNURLcash price if paid storage cannot be activated. It is sent only to that node, never to discovery relays. Older nodes keep their manual refund process.
After a timeout or cancellation, check the same order. Do not pay a second time. An activated allowance is not proof that a file was uploaded or replicated.
Verify storage with a fresh challenge
First resolve a signed file event or private pool receipt below. This reads every selected encrypted byte and independently downloads it for verification. It needs no decryption key. Large checks use bandwidth. Passing proves current retrievability, not continuous retention or a dedicated physical copy.
02
Publish a file
Inspect your file, save its recovery key, then approve the upload. Keep the signed file event or pool receipt for recovery.
External signing handoff
The handoff exposes the intended service and metadata, and the returned event adds the public signing identity. Transfer it deliberately. Never paste a private key or recovery key here.
Optional: configure trackers before uploading to make this file available to peers.
Signing creates a NIP-94 file event locally. Configured trackers also add a NIP-35 torrent index.
Save the signed file event to recover without a discovery relay. It contains public metadata, never the file or its recovery key. Keep the recovery key separately.
03
Retrieve and verify
Start with your saved file event or pool receipt. Verify it locally, enter the recovery key when asked, then fetch and save the verified file. No signer is needed for ordinary recovery.
If the original server is unavailable, enter a server that already holds a copy before resolving the event. Leave blank to use the signed event's URL. A Blossom fetch contacts only the chosen server, which sees your connection and the file's hash. The signed size, hash and encryption checks still apply. This does not create a replica or prove ongoing storage.
Use a saved file event or pool receipt
Load the signed file event or pool receipt you saved, or paste its JSON below. You do not need to configure relays or a publishing layout for this. Verification checks its signature and file information locally. Check the author or retained event ID before fetching; a valid signature alone does not identify someone you trust.
Repair reconstructs ciphertext locally without a recovery key, then uploads only the intended parts to their approved nodes. Connect the receipt author’s signer first. The browser must remain open.