Wallet identity
One local secp256k1 key, signing deploys and encrypting messages.
EVM Address
ECIES Public Key
DECENTRALIZED EDGE NETWORK · ONLINE
☁️ WEB25.cloud
01 BROWSER NODEE2E ENCRYPTEDP2P DELIVERY
🔐 Welcome back
Choose how you want to continue.
No external wallet required.
Signing happens locally in your browser before deployment.
DEPLOY / PIPELINE
Ship a static site
Signature pending
1. Select files
2. Build in-memory bundle
3. Review payload
4. Sign payload
5. Deploy signed memory torrent
6. Create GoFile mirrorOptional
7. Live + mirrored
Stage 1 · Select files
In-memory artifact not staged
▶ Next: Upload your website folder to stage files.
Step 1 · Choose your website folder
Everything is bundled in browser memory. Nothing is uploaded to a server.
Drag & Drop Your Website
Drop a folder with your static site files. We bundle it in browser memory, then sign and deploy.
Step 2 · Sign, then deploy
Your local identity signs the payload; the signed torrent is what goes live.
Optional. Uploads a copy of this signed deployment to GoFile. WebTorrent remains the primary transport, and your deployment succeeds either way.
View technical details
Payload Preview
Deploy Output
📚 How to Deploy
🎨 Build a static website with HTML, CSS, JavaScript, and assets
📤 Upload your folder using the area above
🧠 Build and verify the in-memory bundle (paths normalized)
✍️ Sign the deploy payload with your local identity
🔗 Copy and share your unique Web25 link
☁️ Keep this tab open while you seed the site
WEB25 gateway
Open any peer-hosted site by its hash, mirror locator or full WEB25 link.
hash 40-character infohash
hash&locator hash with GoFile mirror
web25 url a complete shared link
P2P is always tried first. A mirror is only ever a fallback.
keyword title, description or file name
publisher the address that signed it
hash the first characters
Searches only what this browser has already loaded. Nothing leaves your device.
Resolved by your browser
Your own node joins the swarm and pulls the bundle from whoever is seeding it.
Verified before it renders
The signed .torrentchain manifest is checked against the publisher identity.
Mirror as a fallback
If no peer answers, a temporary GoFile locator in the link can serve the same bytes.
🐛 Debug mode
Add &debug=true to any URL for detailed progress logs:
https://WEB25.cloud?orc=ABC123DEF456...&debug=true
The web, hosted by the people reading it
Sign a static site with a key that never leaves your browser, seed it to the swarm, and message anyone by their Nostr address — no backend, no signalling server, no mandatory wallet extension.
0servers to rent
1local key, three addresses
E2Eencrypted direct messages
P2Pbrowser-to-browser delivery
Built on
How it works
Three steps, all of them in your browser
Bundle and sign
Your folder is bundled in memory (gzip by default) and signed with your
local EVM identity. A .torrentchain manifest carries the
publisher identity and integrity metadata.
Seed to the swarm
WebTorrent seeds the signed bundle straight from this tab. An optional GoFile mirror can stand in as temporary fallback transport.
Share one link
Anyone who opens your WEB25 link resolves it peer-first, verifies the signature, and renders the site in a sandboxed, opaque-origin frame.
Under the hood
What the platform actually does
Three pieces carry the whole thing: who you are, how a site ships, and how two browsers talk.
One key, three addresses
A single local secp256k1 key signs your deploys, encrypts your messages and publishes your handle — no second seed anywhere.
0x…signs deploys04…encrypts messagesnpub1…is how people reach you
Sites ship signed
Your folder is bundled in memory, signed, and seeded straight from the tab. The signature travels with the bytes.
- gzip bundle, built in the browser
- Signed
.torrentchainmanifest - Verified before anything renders
Chats find each other
Type someone's Nostr address and the encrypted invitation is delivered for you — no magnet links, no key pasting.
- WebRTC first, relay fallback
- NIP-44 / NIP-59 gift wrap
- Unknown senders wait for your Accept
Local-first by design. Peer-to-peer by default.
WEB25.cloud keeps identities and data local, with WebRTC as the preferred direct transport. Public WebTorrent trackers, STUN servers, Nostr relays and edge services like GoFile are replaceable building blocks for discovery, connectivity and fallback — never dependencies on a single provider.
Loading chapter…
Loading chapter…
Loading chapter…
Loading chapter…
Loading chapter…
Loading chapter…
Status
Shipped today, and what comes next
📋 What is available now
✅ Signed static-site deploys with publisher identity in .torrentchain
✅ Load-time verification path for identity + bundle integrity
✅ Local EVM identity protected by WebAuthn passkeys
✅ One key, three identities: EVM, ECIES and Nostr
✅ Direct P2P messaging with asymmetric cryptography
✅ Address a chat by
npub, with encrypted Nostr signalling✅ Encrypted Nostr relay fallback when WebRTC cannot connect
✅ Browser-first workflow with no mandatory centralized backend
🛣️ Future goals
🛰️ Own WebTorrent tracker
🪐 Own Nostr infrastructure
📦 Migrating from GoFile to Sia Network
🔒 Encrypted static-site content delivery
💱 Decryption-key unlock via atomic-swap payment flow
Publish something nobody can take down for you
Create a local wallet, drop a folder, sign it, and share the link. It runs entirely in this tab.