Alphabiz is an Electron media player built on WebTorrent with a credit marketplace
Web3 YouTube Alternative - fully decentralized media platform and blockchain-based marketplace
At a glance
- What is it?
- Alphabiz is a GPL-2.0 Electron application that plays mainstream media formats over a WebTorrent P2P stack with DHT, trackers and NAT traversal, and adds a credit based marketplace where seeding earns AB credits. It ships for Windows, macOS and Linux plus a web edition, and the last push was on 2026-10-11.
- Who is it for?
- Alphabiz suits someone who wants a media player that fetches over P2P, wants subtitles including styled ASS and SSA, or wants to run their own branded build of a media platform on the same core. It is the wrong tool if you need a stable, actively maintained release, since the current stable build is 0.3.3 from 2024 while the 0.4 line is still a beta, and it is the wrong tool if you want a guaranteed content catalogue.
- Can I use it commercially?
- Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 12 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 23, 2026, and from our analysis. They are not legal advice.
Editorial analysis
The pitch is a media platform with no gatekeeper
Alphabiz describes itself as the open-source Web3 YouTube alternative, a fully decentralized media platform and blockchain-based marketplace, and the three-line summary is stream over P2P, publish without gatekeepers, trade media on a credit system.
The argument in the why section is about intermediaries. Video platforms decide what gets published, who gets paid, and where you are allowed to watch, and Alphabiz is built so that none of that needs a middleman.
The four consequences are listed as publish freely with no platform approval and no regional lockout, stream at full speed because content is delivered peer-to-peer so downloads scale with the swarm instead of one server's upload pipe, search the world through a global decentralized library that works without a proxy, and earn by sharing, with spare bandwidth and disk space earning AB credits, the platform's own unit of exchange.
That last one is the part that makes it a Web3 project rather than a torrent client. The unit of exchange is a credit, and the marketplace is where media is priced and traded. The README describes the decentralized marketplace as publish, price and trade media on a credit system, with seed-phrase wallets keeping the keys with the user. A seed phrase is the same model as any crypto wallet, which means the key management is the user's problem and a lost seed phrase is a lost wallet.
The project is GPL-2.0, the licence file is at the top of the tree and the package.json declares GPL-2.0-only, and the homepage is alpha.biz with a web edition at web.alpha.biz.
WebTorrent with DHT, trackers and NAT traversal
The what's inside table names the pieces, and the streaming engine is the technical centre.
The P2P streaming engine is WebTorrent with DHT, trackers and NAT traversal using NAT-PMP and UPnP, so you watch while you download. WebTorrent is a Node implementation of the BitTorrent protocol, and the three additions are what make it usable as a streaming client rather than only a downloader. DHT is the distributed hash table that finds peers without a central index, trackers are the fallback for finding them, and NAT traversal through NAT-PMP or UPnP is what lets two peers behind home routers find each other at all.
That combination is why the platform claims it can work without a proxy and scale with the swarm. There is no server to be slow, and there is no single index that can be blocked.
The media player is described as playing the mainstream formats on a custom Electron build with extra codecs, with full subtitle support including styled ASS and SSA. The custom Electron build is the interesting part. Electron normally ships with a fixed set of proprietary codecs, and media playback is one of the classic reasons to rebuild it. The ASS and SSA support matters for anime and for fan subtitling, where the styled subtitle format carries positioning and styling information that plain SRT does not.
The library side adds channels, recommendations and a community take-down process with committee voting instead of a single moderator. The committee model is a deliberate governance choice, and it is the kind of detail that tells you the project has had to deal with the moderation problem that any upload-based platform faces.
The locale story is unusually thorough: 17 languages out of the box, plus language packs the app loads at runtime so translations ship without a new release. For a project with a Chinese-speaking author and a global audience, that split is a sensible way to keep the release cadence independent of the translation work.
The build is a forked Electron app with a patch pipeline
The repository is a JavaScript project and the scripts show how the build works.
The main entry point is electron/UnPackaged/electron-main.js, and the packageManager field pins yarn at 1.22.22, which is Yarn Classic rather than the modern Berry releases. The postinstall is where the Electron customisation happens: it runs a skipPatch script, symlinks the @zeeis/velectron package over the electron package, and then runs electron-rebuild against Electron 21.3.3.
That is the mechanism behind the custom codecs. Velectron is a patched Electron build, and the symlink plus electron-rebuild step replaces the stock binary with one that decodes the formats the app needs. It is a common approach in this space and it is also a maintenance obligation, because every Electron security update has to be re-applied to the patch.
The build script removes the unpackaged node_modules, reinstalls inside the unpackaged tree, and then runs packager.js with CI set to false, so the packaging step is a node script rather than a configuration file. The unpackaged script does the install and the electron-rebuild without packaging, which is the loop a developer works in.
The end-to-end test setup is notable. There are pretest and posttest pairs for four separate suites, electron main, wallet, library and libChannel, and each pair runs update-version.js and copy-patch.js with a --pre or --post flag. The copy-patch step is what puts the patched Electron back in place before a test run and takes it out again afterwards, so the repository is not left in a patched state between suites.
The playwright.config.js at the top level is the test runner config, and there is a test/ directory with test.config.js beside it. The other top level entries are release tooling, with release.json, versions.json, update-version.js, shasum.js and packager.js handling versioning and packaging, plus a patches/ directory for the Electron patch and a developer/ directory for the branding configuration.
Forking it to your own brand is the intended use
The build your own branded app section is the most unusual thing about this project, and it is presented as a first class use case rather than a footnote.
Alphabiz is designed to be forked. Everything about the product you ship, meaning the name, icons, colours, protocol scheme, update channel, recommended channels, take-down policy and terms, lives in the developer/ directory. Change one file, run four commands, and you have Windows, macOS and Linux installers for your own app. The clone command in the README notes that a source ZIP will not build, which is the normal constraint for a project with submodules or generated artefacts.
The framework table entry says it plainly: a framework, not just an app, fork, edit one config file, and ship installers under your own brand, the same core, your product.
That framing is worth pausing on as a reader. It is a fairly explicit invitation to run a media distribution platform, complete with a marketplace and a P2P catalogue, under your own name. The stated purpose of the developer/ configuration includes the take-down policy and the terms, which tells you the project considers the governance parts of a deployment to be configurable per operator.
The distribution breadth that this makes possible is in the update channels and platform table. Stable, nightly and internal channels served from GitHub or S3, with a remote config the app refreshes on launch, and packaging for Windows as EXE, MSI and APPX, macOS as DMG and the Mac App Store, and Linux as DEB and Snap.
The web edition is a third target. The same core runs in a browser at web.alpha.biz, which is what makes a P2P media player usable without installing anything, and it is listed in the download table as any platform, nothing to install.
Downloads, checksums and one package you should not trust
The download table is thorough, and it contains one warning that is worth reading carefully.
The current stable release is 0.3.3, and the official download page serves the same files straight from the repository's GitHub Releases. Windows 10 and 11 x64 get an MSI installer and an EXE installer. macOS 11 and later gets a DMG for Apple silicon and a separate one for Intel. Linux on Ubuntu 20.04 or Debian x64 gets a DEB and a Snap, and the Snap command given is sudo snap install --dangerous alphabiz-0.3.3.snap. The dangerous flag is the Snap packaging of a network-facing application that has to reach outside the sandbox, and it is not a small thing to accept casually.
Arch Linux is covered by an AUR package named alphabiz-bin, which the README marks as community-maintained, and there is a web edition for any platform.
Every file on the release page has a .sha sidecar with its SHA-256 checksum, and portable .7z archives and every earlier version are there too. Publishing checksums beside the artefacts is the minimum, and it is what lets someone verify a download without trusting the hosting page.
The warning is about the appx. The .appx attached to 0.3.3 was signed with a development certificate that has since been retired, and the instruction is not to add that certificate to a trusted certificate store, and to install the MSI or EXE instead. Retiring a signing certificate without re-signing the artefact attached to an existing release is exactly the kind of thing that leaves a package in an unusable state, and the honest handling is to say so plainly rather than to quietly remove the file.
The version numbers carry a gap worth noting. The stable release is 0.3.3 from 2024, while the package.json says 0.4.0-beta.1 and the release list includes a 0.4.0-beta.1 tag from 2026-08-29, so the 0.4 line has been in beta for over a month with the stable line a year older.
Where Alphabiz is the wrong choice
The first limit is the version state. The current stable release is 0.3.3 from 2024-09-13 and the 0.4.0-beta.1 tag is from 2026-08-29, so the release the README points people at is a year old while the interesting work is in a beta. The release history also shows a daily nightly channel that ran through 2022 and 2023 and then stopped, so the cadence has changed shape more than once.
The second is the trust surface of a seed-phrase wallet. The marketplace keeps the keys with the user, which is the right default, but it also means the wallet model, the credit system and any marketplace transactions are the user's responsibility. The README does not describe a recovery flow, a revocation path or what happens to credits when a key is lost, and for something framed as a marketplace that is a real gap.
The third is the content question, which the project is explicit about but a reader should be clear on. This is a P2P media distribution platform with a marketplace and a decentralized library, and a global searchable catalogue of user-published content is not the same as a licensed catalogue. The take-down process with committee voting is an attempt at governance, and the fact that the policy is configurable per fork in developer/ is a design choice with consequences.
The fourth is the maintenance obligation of the patched Electron. Rebuilding Electron for codecs means carrying a patch across every Electron upgrade, and the postinstall script shows the mechanism. A project that maintains a fork of the browser runtime has a security surface that a stock Electron app does not, and the release history suggests the pace at which that has been kept up.
The fifth is the base image and toolchain. Electron 21.3.3 is the version being rebuilt, which is a specific and dated choice, and Yarn Classic 1.22.22 as the package manager means the project is on the older Yarn toolchain. Nothing here is a blocker, but a fork starting today inherits both.
Editorial conclusion
Alphabiz suits someone who wants a media player that fetches over P2P, wants subtitles including styled ASS and SSA, or wants to run their own branded build of a media platform on the same core. It is the wrong tool if you need a stable, actively maintained release, since the current stable build is 0.3.3 from 2024 while the 0.4 line is still a beta, and it is the wrong tool if you want a guaranteed content catalogue. Before installing, check the signed package warning in the README, because the appx attached to 0.3.3 was signed with a retired development certificate, and note the Snap install needs the dangerous flag.
Frequently asked questions
What is Alphabiz?
It is an open-source Web3 media platform and marketplace, described as a YouTube alternative that is fully decentralized. It ships as an Electron desktop app for Windows, macOS and Linux, as a web edition, and as a framework you can fork to launch your own branded app on the same core.
How does Alphabiz stream media?
It uses a P2P streaming engine built on WebTorrent with DHT, trackers and NAT traversal through NAT-PMP and UPnP, so you can watch while you download. The player itself runs on a custom Electron build with extra codecs and supports styled ASS and SSA subtitles.
What are AB credits and how are they earned?
AB credits, written as alpha in the README, are the platform's own unit of exchange. They are earned by sharing spare bandwidth and disk space, and the decentralized marketplace lets users publish, price and trade media on the credit system, with seed-phrase wallets keeping the keys with the user.
How do I build my own branded Alphabiz app?
Fork the repository and change the configuration in the developer/ directory, which holds the name, icons, colours, protocol scheme, update channel, recommended channels, take-down policy and terms, then run the four build commands to produce Windows, macOS and Linux installers. A source ZIP will not build, so you need to clone with git.
Which Alphabiz download should I avoid?
The .appx attached to release 0.3.3, because it was signed with a development certificate that has since been retired. The README says not to add that certificate to a trusted certificate store and to install the MSI or EXE instead.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/tanshuai-alphabiz)Was this useful?