Aether
Decentralized Application
Community
Links
Details
License AGPL-3.0 (aether-app: github.com/aethereans/aether-app); 1.2k stars, 44 forks, 1 contributor (Burak Nehbit); Mim protocol open
Dev Status ⚠️ Stalled
Dev Status Detail Effectively stalled (P2P) / Active (Pro): aether-app GitHub repo (AGPL-3.0) last commit ~2021-2022 per AlternativeTo and community reports; described as "abandonware" by community as of ~2023. Aether Pro (aether.app) SaaS remains active with ongoing development. P2P network may still have active nodes but no official new releases.
Owner Aether Technologies, Inc — Burak Nehbit (founder/CEO, ex-Google/YouTube UX designer + engineer); co-founder Lau (joined 2019-2022)
Country USA (Silicon Valley / West Coast)
Start Year 2013
Stack Go (P2P backend, Mim protocol, ~40%); Vue.js + TypeScript (Electron frontend, ~18%); Electron (desktop runtime); gRPC (internal IPC); JavaScript (~41%); SCSS; Snap/AppImage/deb/rpm (Linux packaging)
Funding Patreon (community donations); small pre-seed VC (undisclosed, for Aether Pro); Gitcoin grant (listed on Gitcoin, grant #2105)
Last Investigated Mar 9, 2026
Decentralized Application Attributes
Origins Burak Nehbit began development ~2013 as a privacy-conscious, censorship-resistant Reddit/Usenet alternative. Inspired by Usenet's decentralized community model with modern UX. First public release 2018 (2.0). Covered by The Verge (2013) and Hacker News. Aether Pro created 2019-2021 with small pre-seed VC to fund P2P development via SaaS revenue.
Database Local filesystem (each node stores full content graph, ~300MB typical); no central DB; distributed flood replication
Query Language None — browse/search via app UI; no programmatic query interface
Data Formats Text-only (posts, threads, comments); Markdown with code highlighting (180+ languages); #hashtags; inline image/video preview (user-controlled allowlist); proof-of-work signatures per action
Collaborative Live Editing No — asynchronous threaded posts only; no real-time co-editing
Rich Text Editing Markdown with syntax highlighting for 180+ programming languages; no WYSIWYG editor
Mobile Support No — desktop-only (P2P architecture makes mobile impractical; noted as known limitation); Aether Pro (SaaS) may have mobile web access
Web Support No (P2P app) — desktop client required; Aether Pro (SaaS at aether.app) is web-accessible
Native Apps Yes — Windows, Mac OS, Linux (Electron); Linux: .deb, .rpm, .tar.gz, .AppImage, Snap Store
Terms Free to use (P2P app); Patreon optional support; Aether Pro: subscription SaaS ($10/mo per member, 14-day trial, 30-day money-back); on-premises installations available
Funds Patreon: individual backers (names listed in BACKERS.md); sponsors include Peter Wang; Gold Sponsor slot unfilled; VC amount undisclosed
Based On Mim protocol (custom, open P2P protocol for content graph distribution); Usenet conceptual model; proof-of-work spam prevention (not blockchain)
Use Case Category Decentralized social discussion / community forum; public discourse; privacy-conscious community building
User Interface Type Desktop GUI (Electron); dark-mode default; Reddit-like threaded community layout; community list + post threads + mod activity tab
Offline Capabilities Partial — content stored locally on user's node (~300MB); previously synced content accessible offline; new content requires P2P connection; no explicit offline-first design
Collaboration Features Asynchronous threaded discussions per community (subreddit-analog); upvoting/downvoting; moderation (with user override); mod elections; community creation; pseudonymous participation
Data Portability Limited — content stored locally on node; user can back up their own node data; no standard export format; no ActivityPub or federated protocol compatibility; ephemeral (6-month deletion) by design
Integration Ecosystem None — standalone P2P app; no API for external integrations; no plugin ecosystem; Mim protocol open but no third-party implementations known
Web2 Data Export None — no import from Reddit, Mastodon, or other platforms; no export to web2 formats
Prosocial Coherence High design intentionality — subjective moderation model ("consent of the governed") is a principled alternative to black-box algorithmic moderation; mod transparency (all actions visible with stated reasons); mod elections enable democratic community governance; ephemeral content reduces permanent reputation harm. Pro: empowers user agency over information environment. Con: smaller community = echo chamber risk; block list for illegal content is a centralized choke point.
Economic Flows No in-app economy; Patreon donations for P2P development; Aether Pro SaaS subscription funds P2P R&D; no token or crypto payment layer; unique username purchase (supporter perk)
Governance & Decision Making P2P network: community-level democratic moderation — users elect/impeach mods via voting; users can disable any mod locally (reverts all that mod's actions for that user); no global admin; block list (for legally required content removal) is the only centralized governance element. Platform-level: Aether Technologies, Inc makes protocol and product decisions; open source allows forking.
Media / Publishing Text-only posts and threads; inline image/video link previews (user-controlled); code blocks with syntax highlighting; no native media hosting or uploads
Knowledge Management Searchable threaded community archives; hashtags; but ephemeral (6-month deletion) limits long-term knowledge retention; no wiki or structured knowledge features
Sensemaking Upvote/downvote surfacing; community-elected moderators as trusted filters; user-selected moderation subscriptions allow personalized information curation; no algorithmic feed; chronological + voting hybrid. Ephemeral design intentionally limits permanent record / accountability.
Project Management None — discussion forum only; Aether Pro (SaaS) has team channels that can serve project coordination use cases but not native PM features
Communication Model Asynchronous; public threaded posts within communities; no private messaging (P2P version); Aether Pro adds chat rooms and email newsletter delivery
Network Resilience High (P2P layer) — fully P2P, no central servers; content replicated across all nodes; network survives as long as ≥1 node exists and remembers content; self-healing by design. Partial caveat: block list mechanism (for illegal content) contacts an external list, introducing a centralized dependency.
Discovery Mechanism Flood-based content graph distribution — every node receives all content; community browser within app; no algorithmic recommendation; hashtag browsing; no external discovery
Max Participants ~2,000 monthly active users (P2P, as of 2022 reporting); "handles thousands of users in a global realm" per billing docs; no technical hard cap — flood distribution scales with node storage
Data Sovereignty High (P2P) — all content stored locally on user's node; no central server holds user data; pseudonymous by default; IP tracking difficult (P2P relay); user controls moderation experience; ephemeral deletion after 6 months (protocol-enforced, not user-controlled); block list for illegal content is the only external data dependency.