Hey

Open-source social media, honestly reviewed. No Web3 hype, just what you actually get.

TL;DR

• What it is: A decentralized, permissionless social media application built on Lens Protocol — think Twitter/Threads, but your profile and posts are NFTs on a blockchain that no company can delete or monetize without your consent [1].
• Who it’s for: Developers, crypto-native creators, and privacy advocates who want to own their social graph. Not a cost-saving play — Threads is free. This is an ideology play.
• Cost savings: None in the traditional sense. Threads costs $0; Hey costs $0. The value proposition is ownership and censorship resistance, not dollars saved [merged profile].
• Key strength: Your profile, followers, and content are NFTs on Lens Protocol — portable across any Lens-compatible app, not locked to Hey’s servers [1][2].
• Key weakness: This is a full Web3 monorepo (Node.js, pnpm, Postgres, Lens Protocol API) with no Docker Compose path. Self-hosting it is a developer-level task. The non-technical founder audience this site targets will find it borderline inaccessible.

---

What is Hey

Hey (previously called Lenster) is an open-source social media client for the Lens Protocol. The basic pitch: instead of your posts and follower list living on Meta’s servers — where they can be deleted, shadowbanned, or monetized without your consent — everything lives on a blockchain. Your profile is an NFT. Your posts are NFTs. The social graph connecting you to your followers is an on-chain data structure that any app can read with your permission [1].

The project sits at 29,483 GitHub stars and is licensed under GNU AGPL-3.0 [merged profile][README]. The AGPL license is worth noting: it’s one of the most restrictive open-source licenses. If you build a SaaS on top of Hey’s code, you must open-source your entire server-side stack. This matters if you’re a founder thinking about embedding it in a product.

Hey is categorized under AI/ML in this site’s database, which is inaccurate — it’s a social network. The SaaS equivalent the profile lists is Threads [merged profile], though a more accurate comparison is Twitter/X or Mastodon.

The application is a Next.js monorepo with multiple packages managed via pnpm workspaces. The technical stack requires Node.js v22+, pnpm, and Postgres for local development [README]. There is no official Docker Compose path in the repository — deployment is a manual engineering exercise.

---

Why People Choose It

The two substantive third-party sources available paint a consistent picture: people choose Hey because they’re done trusting centralized platforms with their digital identity.

The SignalPlus analysis [1] frames the core value proposition: traditional social networks own your social graph. If Twitter bans your account, you lose your followers. If Instagram pivots, your content disappears. Hey’s Lens Protocol architecture means your followers are a portable, on-chain asset — you can take them to any other Lens-compatible application without starting from zero. This is a genuinely different model, not just a different UI on top of the same centralized database.

The monetization angle is also different. Rather than the platform profiting from advertising against your content, Hey enables direct creator-to-audience transactions. Creators can gate content, sell posts as collectibles, or accept direct payments — all without a platform taking a cut or changing the rules midstream [1].

The 4EVERLAND case study [2] reveals the infrastructure challenges Hey tackled to make decentralization practical. Earlier versions of the platform struggled with: data security vulnerabilities when handling file uploads, performance bottlenecks scaling to real user loads, and the tension between true decentralization and the performance users expect from modern social apps. The solutions — IPFS-based distributed storage, S3-compatible APIs with temporary credentials, dedicated content delivery gateways — are serious engineering choices, not buzzword compliance [2].

The honest summary: people choose Hey because they believe in data sovereignty and have given up on centralized platforms as trustworthy long-term infrastructure. They are not choosing it to save $20/month.

---

Features

Based on the repository, articles, and website description:

Core social functionality:

• Post creation, replies, reposts, and reactions [website]
• Follow/unfollow with on-chain social graph via Lens Protocol [1]
• Profile discovery and search [website]
• Media uploads to IPFS via 4EVERLAND’s distributed storage nodes [2]
• Notifications and direct messaging [website]

Ownership and portability:

• Profiles are NFTs — you own the account, not the platform [1]
• Posts are on-chain records — permanent and uncensorable by Hey specifically [1]
• Social graph portability — your followers can be accessed by any Lens-compatible app [1]
• Content monetization via collectible posts and direct creator transactions [1]

Infrastructure (relevant for self-hosters):

• pnpm monorepo with multiple apps and packages [README]
• Postgres database for application-layer data [README]
• IPFS distributed storage for media files [2]
• Lens Protocol API for on-chain social graph operations [website]
• AGPL-3.0 licensed — modifications must be open-sourced if deployed as a service [README]

What’s missing or unclear:

• No Docker Compose or containerized deployment path in the repository [README]
• No documented one-click deployment to any cloud provider
• Lens Protocol is a dependency — if Lens has issues, Hey has issues
• No admin panel, content moderation tools, or multi-user management documented for self-hosters

---

Pricing: SaaS vs Self-Hosted Math

This section looks very different from a typical unsubbed.co review, because the SaaS alternative — Threads, Twitter/X — is either free or cheap.

Hey (self-hosted):

• Software license: $0 (AGPL-3.0) [README]
• Infrastructure to run it: VPS + Postgres + IPFS storage + Lens Protocol API access
• Your time: substantial. This is a full-stack monorepo, not a Docker pull-and-run

Threads: Free. No subscription, no per-post pricing, no plan tiers.

Twitter/X: Free tier exists; X Premium is $8–22/month for blue checkmarks and algorithmic boosts.

The honest math: There is no straightforward “you’ll save X dollars by self-hosting Hey” calculation. The motivation to run Hey is not cost — Meta doesn’t charge for Threads. The calculation is about what you’re paying in non-monetary terms: your content, your social graph, your data, your ability to monetize without a platform tax [1].

If you are a creator who has had accounts banned, had posts removed, or who builds revenue on top of a social following that a platform could delete tomorrow — the cost comparison changes. The risk-adjusted cost of depending on Meta or X isn’t $0; it’s the potential wipeout of years of audience building. Hey’s argument is that AGPL code + a blockchain social graph eliminates that counterparty risk [1][2].

For founders who just want to run an internal communication tool or community forum without SaaS costs, Hey is the wrong tool. Look at Discourse, Mattermost, or Mastodon instead.

---

Deployment Reality Check

This is where Hey diverges most sharply from the typical self-hosted tool reviewed on this site.

What you actually need:

• Node.js v22+ and pnpm [README]
• Postgres database [README]
• Understanding of pnpm workspaces and monorepo structure [README]
• Environment variable configuration across multiple packages [README]
• Lens Protocol API credentials and understanding of how on-chain social graph writes work
• IPFS infrastructure for media storage (or a third-party service like 4EVERLAND) [2]
• Reverse proxy (nginx/Caddy) and domain for production

What can go wrong:

• There is no Docker Compose in the repository. Every deployment requires manually running the monorepo build process [README].
• The .env.example files are referenced but the documentation doesn’t walk you through production configuration comprehensively [README].
• Lens Protocol is a dependency you don’t control. Network issues, protocol upgrades, or Lens policy changes affect your instance.
• IPFS media storage requires either running your own nodes or paying a third-party provider like 4EVERLAND — the 4EVERLAND integration is documented as Hey’s production solution but not trivial to replicate [2].
• The AGPL-3.0 license means any modifications you deploy must be open-sourced, which matters if you’re customizing for a private community.

Realistic time estimate for a developer: 4–8 hours to a working local instance; 1–3 days for a production deployment with proper infrastructure, HTTPS, and media storage.

For a non-technical founder: This is not a realistic self-hosting target without a developer on hand. The README’s first instruction is essentially “install these developer tools” [README]. There is no guided deployment wizard, no managed hosting option from the Hey team, and no community documentation that simplifies this to a non-developer audience.

---

Pros and Cons

Pros

• Genuine data ownership. Your profile and social graph are on-chain NFTs — no platform can delete your account or take your followers [1]. This is architecturally different from every centralized social network.
• Portable social graph. Followers you build on Hey work on any Lens Protocol app. You’re building an asset, not a dependency [1].
• Creator monetization without platform tax. Direct transactions between creators and audiences, no algorithmic feed controlling your visibility [1].
• 29,483 GitHub stars signals real developer community engagement and active maintenance [merged profile].
• AGPL-3.0 — source is fully open; no proprietary lock-in on the application layer [README].
• Serious infrastructure design. The 4EVERLAND partnership shows the team thought through real-world challenges: multipart uploads, distributed IPFS pinning, temporary credential issuance to avoid exposing server secrets [2].

Cons

• Not a cost-saving play. Threads and Twitter are free. The value proposition here is ideological and risk-hedging, not monthly savings [merged profile].
• No Docker deployment path. Self-hosting requires real engineering. Non-technical founders cannot realistically run this themselves [README].
• Lens Protocol dependency. You’re not fully self-sovereign — you’re dependent on a third-party blockchain protocol for the core social graph. Protocol upgrades, fees, or instability propagate directly to your instance.
• AGPL-3.0 is restrictive. If you want to build a commercial product on top of Hey’s code, you must open-source your entire server stack. This rules out most commercial customization scenarios.
• Limited documentation for operators. The README covers developer setup; production deployment documentation is sparse [README].
• NFT framing creates friction. Telling non-technical users “your profile is an NFT” triggers skepticism in 2026. The underlying technology is sound, but the messaging is a hurdle.
• Niche total addressable user base. Building a social following on a platform with limited reach is harder than building on one with billions of users. The portability story is compelling, but only if enough people are on Lens Protocol.

---

Who Should Use This / Who Shouldn’t

Use Hey if:

• You are a developer or creator who has been burned by platform bans, content removal, or account suspensions and wants those risks eliminated architecturally.
• You’re building in the Web3 or crypto space and your audience expects decentralized infrastructure.
• You want to own your social graph as an actual portable asset, not as data locked in a corporate database.
• Your team includes at least one engineer who can handle a Node.js monorepo deployment and IPFS storage configuration.
• You’re willing to trade user base size for data sovereignty.

Skip it if:

• Your goal is escaping SaaS costs. Threads is free; this isn’t the right lever to pull [merged profile].
• You’re a non-technical founder without engineering support. The deployment complexity is real [README].
• You need a large existing user base to market to. Hey’s Lens ecosystem is a fraction of Threads or X.
• You’re uncomfortable with AGPL licensing implications for commercial use [README].
• You need compliance certifications, audit logs, or enterprise access controls.

---

Alternatives Worth Considering

Mastodon — federated, open-source, self-hostable social network with much better documentation, a Docker Compose deployment path, and a significantly larger active user base. The social graph is federated rather than blockchain-based, which makes deployment simpler but portability less absolute. Better fit for non-technical founders who just want to run an independent community.

Fediverse broadly — Mastodon, Misskey, Pleroma, Pixelfed. All ActivityPub-compatible, all self-hostable, all more operationally mature than Hey for non-engineers.

Discourse — if your use case is community or forum rather than a social feed, Discourse has excellent Docker deployment, clear documentation, and a managed hosting option. The right tool for founder communities, customer forums, and support channels.

Ghost — if your use case is creator monetization and newsletter, Ghost is self-hostable, has built-in membership and payment tools, and is far more accessible for non-technical deployment than Hey.

Threads / X — the zero-maintenance option. Free, billions of users, no deployment required. You accept the counterparty risk in exchange for reach and zero operational overhead.

---

Bottom Line

Hey is technically interesting and philosophically coherent. The Lens Protocol architecture genuinely delivers on data ownership in a way that federated solutions like Mastodon don’t — your social graph is portable at the protocol level, not just in theory. The 4EVERLAND infrastructure work shows the team solved real distributed systems problems rather than shipping a prototype [2]. At 29,483 stars, there’s genuine developer community behind it.

But this is a tool for a specific person: someone who has decided, on principle, that they won’t build an audience on infrastructure they don’t control, and who has the engineering resources to deploy a complex monorepo with IPFS storage and blockchain API dependencies. That person exists, and for them, Hey is worth serious evaluation.

For the non-technical founder who landed here searching for ways to cut SaaS bills — this isn’t the right tool. Your social media cost is probably $0 already. Look at Mastodon if you want community infrastructure you own, or Ghost if you want owned creator monetization. Hey’s value proposition is censorship resistance and blockchain-native portability, and those benefits only matter if that specific risk profile matches yours.

---

Sources

1. SignalPlus — “hey.xyz: Revolutionizing Social Media Through Decentralization and NFTs” (March 25, 2024). https://t.signalplus.com/crypto-news/detail/heyxyz-decentralized-social-media-nfts?lang=en-US
2. 4EVERLAND via Medium — “Case Study: How Hey.xyz Leveraged 4EVERLAND for Enhanced Decentralized Social Networking” (August 13, 2024). https://medium.com/4everland/case-study-how-hey-xyz-leveraged-4everland-for-enhanced-decentralized-social-networking-89e322a80aac

Primary sources:

• GitHub repository and README: https://github.com/heyxyz/hey (29,483 stars, AGPL-3.0 license)
• Official website: https://hey.xyz