Hyphanet

Decentralized anonymous publishing, honestly reviewed. Not a SaaS replacement — something stranger, older, and more important.

TL;DR

• What it is: A peer-to-peer anonymizing network for censorship-resistant publishing and communication, originally launched as Freenet in 2000 and renamed Hyphanet after a naming conflict with a separate project [website]. You don’t “self-host” Hyphanet the way you host Nextcloud — you run a node that joins a global encrypted datastore.
• Who it’s for: Journalists, activists, and anyone who needs to publish or communicate in ways a government or hosting provider can’t shut down. Not for non-technical founders looking to cut SaaS costs — this is different territory entirely.
• Cost: Free (GPL-2.0). Runs on any machine with Java. The only cost is bandwidth and electricity.
• Key strength: True censorship resistance at the protocol level. Content distributed across thousands of nodes with no single takedown target. No company to serve a court order to [README].
• Key weakness: Brutally slow — loading a page on the network can take minutes, not seconds. Small active community (1,160 GitHub stars) [merged profile]. The UX hasn’t aged gracefully. If your threat model doesn’t include state-level censorship, there’s almost certainly a better tool.

---

What is Hyphanet

Hyphanet is a peer-to-peer platform for censorship-resistant communication and publishing. It works by building a distributed, encrypted, decentralized datastore across every machine running the software. Websites (called “Freesites”), forums, chat, file sharing, and video-on-demand applications are built on top of this datastore [README]. Nothing is stored in any one place — content is split into encrypted chunks, distributed across participating nodes, and reassembled on demand.

The project has an unusually long history for open-source software. Ian Clarke published the original Freenet design as a thesis paper in 1999 and launched the software in 2000. That makes it over 25 years old — ancient by internet standards — and it is still under active development, with build 1506 released in February 2026 [website].

The naming situation requires a brief explanation. There are now two projects with overlapping names. “Locutus,” a newer and architecturally different project, rebranded itself as “Freenet.” The original Freenet team responded by renaming their project “Hyphanet” to reduce confusion [website]. The GitHub repository is still named hyphanet/fred — fred stands for Freenet REference Daemon — and the codebase is the direct continuation of the original 2000-era project [README].

The network has two operational modes. Opennet connects you to random strangers on the global network — easier to join, lower privacy ceiling. Darknet (friend-to-friend mode) connects only to people you know and trust directly, making the network invisible to any centralized observer and resistant even to traffic analysis at the node level [website]. Darknet mode is what the project considers its strongest privacy guarantee; Opennet is the on-ramp for people without an existing trusted network.

---

Why people choose it

Hyphanet is chosen for a specific reason: you need to publish or communicate and you cannot trust any infrastructure provider not to be compelled to stop you.

The alternatives listed by AlternativeTo users include Tor, I2P, IPFS, Matrix, ZeroNet (now discontinued), GNUnet, and Shadowsocks [5][1]. Each of these occupies slightly different territory. Tor routes your traffic anonymously through existing servers but doesn’t store content — if the origin server goes down, the content disappears. IPFS distributes content but relies on nodes actively pinning it; the privacy model is weaker than Hyphanet’s by design [5]. I2P focuses on anonymous communication channels rather than content persistence [1][5].

What Hyphanet offers that most of its alternatives don’t is persistent, censorship-resistant publishing with strong anonymity. A Freesite published to Hyphanet doesn’t disappear when you turn off your computer — it lives in the distributed datastore as long as people access it. The more popular a piece of content, the more copies are cached across the network. This property is specifically designed for situations where the publisher can’t maintain continuous availability without risking identification [website][README].

A Reddit thread from the Freenet community [4] describes who actually uses it: people in countries with internet restrictions, journalists communicating with sources, and activists who need a publishing channel that can’t be taken offline by a complaint to a hosting provider. The build notes from the same thread show active contributor work on things like “new user entrance” (a first-time wizard), a dark theme, stream error recovery, and CPU optimization [4] — a healthy enough list for a volunteer-driven project, though the pace is slow compared to commercial or larger open-source efforts.

The honest competitive framing: choose Hyphanet if persistence and publisher anonymity are the requirements. Choose Tor if you want anonymous browsing of normal websites. Choose I2P if you want anonymous internal network services. Choose Matrix/Signal if you want encrypted messaging with a better UX [5].

---

Features

Based on the README and official website:

Core network:

• Distributed encrypted datastore — content stored in chunks across participating nodes [README]
• Opennet mode: connects to random global peers, easy onboarding [website]
• Darknet (friend-to-friend) mode: connects only to trusted contacts, invisible to external observers [website]
• Shoeshop plugin: builds a “sneakernet” — bridges isolated friend-to-friend networks when regional internet itself is severed from the global network [website]
• Content popularity-based caching: frequently accessed files survive longer [README, build notes]
• Keepalive plugin: explicitly keep files alive regardless of access frequency [4]

Applications built on the datastore:

• Static website hosting (“Freesites”) [website]
• Forums and microblogging [website]
• File and media sharing [website]
• Video-on-demand [website]
• Decentralized version tracking and blogging [website]
• Spam resistance without central authority [website]

Privacy and anonymity:

• All traffic encrypted and routed through multiple hops [README]
• No central server — no single point of subpoena or shutdown [README]
• Friend-to-friend mode makes network topology invisible to outside observers [website]
• GPL-2.0 — fully auditable source code, no proprietary black boxes [README]

Build and infrastructure:

• Java-based daemon (fred) with Gradle build system [README]
• Browser-based UI via local port [inferred from setup documentation]
• Plugin architecture for extending functionality [4]
• Windows installer, Linux/macOS/*nix installer, Android support [website]
• Active vulnerability patching — builds 1502–1506 specifically note security fixes [website]

What it lacks:

• Real-time communication (the latency makes it unsuitable)
• Modern UX by any contemporary standard
• Centralized search (by design — a searchable index would compromise anonymity)
• REST API for programmatic use

---

Pricing: SaaS vs self-hosted math

This section looks different for Hyphanet than for most tools on this site because there’s no SaaS equivalent with a subscription to escape. Hyphanet is free software under GPL-2.0. The cost is zero for the software [merged profile].

The relevant comparison is against commercial VPN and privacy services, which are the closest paid alternatives people use when they need anonymity:

• Mullvad VPN: ~$5/month for anonymizing internet traffic [1]
• ProtonVPN: $4–10/month depending on tier [1]
• Commercial VPN general range: $3–15/month, typically $60–120/year

Hyphanet costs nothing and provides stronger anonymity guarantees in friend-to-friend mode than any commercial VPN — because a VPN provider is still a company that can be legally compelled, while Hyphanet’s friend-to-friend network has no company to compel [website]. However, it solves a different problem: Hyphanet is for publishing and accessing content on its own network, not for anonymizing your normal web browsing.

Running costs:

• Hardware: any machine that can run Java — an old laptop, a Raspberry Pi, a small VPS
• Bandwidth: variable; nodes route traffic for others, so you’re contributing some bandwidth to the network
• Electricity: marginal
• Your time: significant, especially initial setup and understanding the network model

If your use case is censorship-resistant publishing specifically, there is no commercial SaaS equivalent to compare against. The question isn’t “Hyphanet vs a $99/year subscription” — it’s “Hyphanet vs nothing.”

---

Deployment reality check

Running a Hyphanet node is not the same as deploying a Docker container with a web app behind a reverse proxy. The mental model is different.

What you actually do:

1. Download the installer for your OS (Windows .exe, Linux/macOS shell installer, or Android APK) [website]
2. Run the installer — it sets up a Java daemon that starts automatically
3. Access the node’s web UI through your browser at localhost
4. Complete the first-time wizard (added in build 1495, noted in the Reddit release thread [4])
5. Wait — the node needs time to connect to the network and build routing tables

What takes time:

• First connection: the node starts in Opennet mode and needs to find peers. This can take from minutes to hours depending on network conditions.
• Switching to Darknet mode: you need to manually exchange “node references” with trusted friends who are also running Hyphanet. If none of your contacts run it, you’re stuck on Opennet.
• Content retrieval: loading a Freesite for the first time can take several minutes. The network is slow by design — routing through multiple encrypted hops with no central cache takes time.
• Building a useful friend-to-friend network: this is a social problem, not a technical one. You need people you trust who also run nodes.

What can go wrong:

• Java version compatibility issues — Hyphanet requires a specific Java version range, and system Java installs vary
• Firewall configuration — for best performance, Hyphanet needs open ports for peer connections; this requires router configuration many users skip
• The Apple Silicon note on the website [website] flags that the current installer needs library updates for ARM Macs — check the download page before assuming the standard installer works for your hardware
• Performance varies wildly with the number of active peers and your geographic location
• Content you publish is only accessible if the network has enough demand to keep caching it; obscure Freesites fade from the datastore

Realistic time investment:

• Basic setup on Windows: 30–60 minutes following the installer
• Functional darknet node with multiple trusted peers: days to weeks (requires coordination with other humans)
• Understanding enough of the network model to publish effectively: several hours of reading

This is not a “deploy and forget” tool. It requires ongoing node operation and, for Darknet mode, active relationship management with other node operators.

---

Pros and Cons

Pros

• Genuine censorship resistance. The distributed datastore means there is no hosting provider, no CDN, no domain registrar to pressure. Content that enters the network can persist without the publisher remaining reachable [README][website].
• Strong anonymity in Darknet mode. Friend-to-friend routing means the network topology itself is hidden from outside observers — not just traffic content, but the existence of the network [website].
• GPL-2.0 license. Fully auditable. No proprietary components, no company with access to your traffic [merged profile][README].
• 25+ years of active development. The project has survived longer than most privacy tools. Security vulnerabilities get patched (multiple recent builds explicitly address vulnerabilities) [website].
• No account, no identity. Nothing to sign up for, nothing to link to your real identity at the software level.
• Shoeshop sneakernet. The ability to bridge isolated networks when the regional internet itself is cut is a capability essentially no other tool offers [website].
• Android support. Mobile node operation is available [website].

Cons

• Extremely slow. Loading content through multiple encrypted hops takes minutes, not seconds. This is fundamental to the protocol design, not a fixable bug. Real-time use cases are not viable.
• Outdated UX. The browser-based interface reflects decades of incremental development, not a coherent design pass. Expect functional but rough.
• Small community. 1,160 GitHub stars [merged profile]. The Reddit community (r/Freenet) is active but small [4]. Volunteer-driven development means slow progress.
• Confusing naming. “Hyphanet” is not widely recognized yet. Explaining what you’re running requires explaining the Freenet/Hyphanet rename, which adds friction in every conversation about it [website].
• Darknet mode requires social coordination. The strongest privacy guarantees require trusted contacts who also run nodes. This is a chicken-and-egg problem — the network’s value depends on adoption.
• Content impermanence. Unpopular Freesites fade from the datastore over time. Keepalive tools exist but require active management [4].
• No clearnet access. Unlike Tor, Hyphanet doesn’t anonymize your normal web browsing. It’s a separate, internal network only.
• Java dependency. Requires a functioning Java environment. On some platforms (particularly Apple Silicon currently [website]), this adds setup friction.

---

Who should use this / who shouldn’t

Use Hyphanet if:

• You’re a journalist, activist, or researcher who needs to publish content that a government or hosting provider can’t take down.
• You’re operating in or communicating with people in a region where internet access is filtered or monitored at the ISP level.
• You have trusted contacts who are willing to also run nodes, enabling Darknet mode’s strongest privacy guarantees.
• You need content to persist without you remaining online — a Freesite stays available even if you shut down your computer.
• You’re willing to accept slow access speeds as the cost of strong anonymity.

Skip it (use Tor) if:

• You want to browse normal websites anonymously.
• You need reasonable page load times.
• You want a large existing ecosystem of hidden services [5].

Skip it (use I2P) if:

• You want anonymous internal network services with an active community and better routing performance [1][5].

Skip it (use Signal/Matrix) if:

• You need real-time encrypted messaging. Hyphanet’s latency makes synchronous communication impractical [5].

Skip it entirely if:

• Your goal is to cut SaaS costs, run your own tools, or replace subscription software. Hyphanet solves none of those problems — it’s specifically and exclusively a censorship-resistance and anonymity tool.
• You want something you can hand to a non-technical colleague with minimal explanation. The network model is not intuitive and the UX will frustrate non-technical users.
• You need search to discover content. By design, there’s no searchable index.

---

Alternatives worth considering

From the AlternativeTo listing for Hyphanet [5][1]:

• Tor — the largest anonymizing network. Better for browsing existing clearnet and .onion sites anonymously; weaker for persistent content publishing. Widely documented and supported [5].
• I2P — focused on anonymous network services within its own network. More active community than Hyphanet, better performance, different threat model [1][5].
• IPFS — distributed content storage with weaker anonymity guarantees. Better performance, much larger ecosystem, used in Web3 contexts. Not designed for adversarial censorship environments [5].
• ZeroNet — listed as an alternative but marked discontinued on AlternativeTo [5]. Not a viable choice for new deployments.
• Matrix/Element — federated, end-to-end encrypted messaging. No anonymity at the network level but strong encryption and no central server. Self-hostable [5].
• GNUnet — similar goals to Hyphanet, smaller community, active academic development [5].
• Mullvad/ProtonVPN — commercial VPN services for anonymizing normal browsing. Easier setup, faster, but a company in the trust chain [1].

For censorship-resistant publishing specifically, the realistic shortlist is Hyphanet vs I2P vs Tor hidden services. For anonymizing general internet access, skip all three and evaluate Tor Browser or a reputable VPN.

---

Bottom line

Hyphanet has been solving a specific problem for 25 years: how do you publish something that a government, hosting provider, or court order cannot take down? It does that well, and it has the scars and battle-hardened protocol design to prove it. It does essentially nothing else well. The speed is slow by design, the UX is showing its age, and the community is small enough that you’ll feel the limits. But for its intended use case — censorship-resistant publishing in adversarial environments — there’s nothing quite like Darknet mode’s friend-to-friend routing model, which makes the network itself invisible to outside observers.

If you’re reading this site to escape a Zapier bill or avoid per-seat SaaS pricing, Hyphanet is probably not what you’re looking for. If you’re thinking about how to communicate or publish in an environment where the infrastructure itself can be weaponized against you, it is worth understanding. It’s been quietly working on that problem since before most of today’s cloud infrastructure existed.

---

Sources

1. AlternativeTo — Shadowsocks Alternatives (Top VPN Services & Similar Apps). https://alternativeto.net/software/shadowsocks/
2. AlternativeTo — Apps with ‘Peer-To-Peer’ feature (P2P tool landscape). https://alternativeto.net/feature/peer-to-peer/
3. Shaynly — A Catalog Of Self-Hosted Free Software Network Services And Web Applications. https://shaynly.com/self-hosted-free-software/
4. r/Freenet — Freenet build 1495 released: faster new user entrance, enhanced user experience, and better performance (Reddit community release thread). https://www.reddit.com/r/Freenet/duplicates/zyip1d/freenet_build_1495_released_faster_new_user/
5. AlternativeTo — Great Hyphanet Alternatives: Top Anonymizing Networks in 2024. https://alternativeto.net/software/freenet/

Primary sources:

• GitHub repository (fred — Freenet REference Daemon): https://github.com/hyphanet/fred (1,160 stars, GPL-2.0)
• Official website: https://hyphanet.org/
• README: https://github.com/hyphanet/fred/blob/next/README.md