Software Alternatives & Startups

Officially verified details Shardnet.app

Chat, store and share files without servers. Encrypted on your device, split across the network. No accounts. Storage nodes see only opaque ciphertext.

Shardnet.app

Shardnet.app Reviews and Details

This page is designed to help you find out whether Shardnet.app is good and if it is the right choice for you.

Screenshots and images

  • Message Mode //
    2026-06-24
  • Read mode //
    2026-06-24

Features & Specs

  1. Encryption

    AES-256-GCM — client-side, before any data leaves your device

  2. Chat

    Room-based, Ed25519-signed messages over the same swarm

  3. Open protocol

    Full spec published (WHITEPAPER.md) — no proprietary lock-in

  4. No Server Required

    Single static binary — zero runtime dependencies, zero cloud

  5. NAT traversal

    UDP hole punching + STUN — works behind most home routers

  6. Routing

    Kademlia DHT — fully decentralised peer discovery, no tracker

  7. Transport

    QUIC / TLS 1.3 — encrypted, low-latency, NAT-traversal built-in

  8. Erasure coding

    Reed-Solomon 10+5 — survives loss of up to 5 of 15 fragments

  9. Encryption

    AES-256-GCM — client-side, before any data leaves your device

  10. Identity

    Ed25519 keypair — cryptographic node identity, no accounts

Badges

Promote Shardnet.app. You can add any of these badges on your website.

SaaSHub badge
Show embed code

Questions & Answers

As answered by people managing Shardnet.app.
  1. How would you describe the primary audience of Shardnet.app?

    Technically-minded users and developers who want to store or share files without trusting a third party. This includes privacy-conscious individuals, open-source communities self-hosting shared documents, developers building decentralised applications that need a storage layer, and organisations that cannot or will not rely on cloud providers for sensitive data.

  2. Who are some of the biggest customers of Shardnet.app?

    Shardnet is currently in public alpha — functionally complete but not yet independently audited for security. Early adopters are individual developers and privacy researchers evaluating the protocol. We're not listing customers until the security audit is done and the protocol is production-ready. If you're interested in an early deployment, reach out directly.

  3. What makes Shardnet.app unique?

    Shardnet removes the server from the equation entirely. Files are encrypted on your device (AES-256-GCM) before leaving it, split into 15 fragments via Reed-Solomon erasure coding, then spread across the peer swarm. Any 10 of those 15 fragments reconstruct the original — even if a third of the network goes offline. Nodes storing your shards see only ciphertext indistinguishable from random noise. No account, no API key, no company holding your data. The decryption key travels only in your magnet link.

  4. Why should a person choose Shardnet.app over its competitors?

    Most "decentralised" storage products still have a centralised component — a coordination server, a token smart contract, a wallet requirement, or a proprietary daemon. Shardnet has none of these. It runs as a single static binary with no runtime dependencies, connects over QUIC/TLS 1.3, and routes via a Kademlia DHT. There are no tokens, no fees, and no registration. If you run a node, you contribute storage and gain access to the swarm — the protocol is self-sustaining because every user is also a provider.

  5. What's the story behind Shardnet.app?

    Shardnet started from a simple frustration: every "serverless" storage tool we looked at still had a server somewhere — a coordinator, an incentive layer, or a hosted gateway. We wanted something where the threat model was actually clean: zero-knowledge storage, no central point of seizure, no account to compromise. We built the protocol in Rust, wrote the spec first, then implemented it — QUIC transport, Kademlia DHT, Reed-Solomon erasure coding, AES-256-GCM encryption, all from scratch. The result is a single binary you can run on any Linux machine and be part of a global swarm in under ten seconds.

  6. Which are the primary technologies used for building Shardnet.app?

    Which are the primary technologies used for building Shardnet?

    Rust — the entire stack, compiled to a dependency-free static binary QUIC / TLS 1.3 (quinn + rustls) — encrypted transport with mutual Ed25519 authentication Kademlia DHT — XOR-metric peer discovery and shard routing (K=20) Reed-Solomon erasure coding — 10 data + 5 parity shards per file AES-256-GCM — client-side file encryption Ed25519 — node identity and signed chat messages Axum — embedded HTTP/WebSocket server for the web GUI Argon2id — proof-of-work for node admission (Sybil resistance)

Videos

We don't have any videos for Shardnet.app yet.

Do you know an article comparing Shardnet.app to other products?
Suggest a link to a post with product alternatives.

Suggest an article

Shardnet.app discussion

Log in or Post with

Is Shardnet.app good? This is an informative page that will help you find out. Moreover, you can review and discuss Shardnet.app here. The primary details have been verified within the last quarter. So they could be considered up to date. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.