Suwayomi-Server: A Self-Hosted Manga Server That Runs Tachiyomi Extensions
A rewrite of Tachiyomi for the Desktop
At a glance
- What is it?
- Suwayomi-Server is a Java manga reader server that executes Mihon (Tachiyomi) extensions and exposes a library, downloads and OPDS endpoint to whatever client you point at it. The README is clear about what it does and equally clear that you need to bring your own front-end.
- Who is it for?
- Adopt Suwayomi-Server if you already run a home server, want your manga library on your own disk, and are willing to pick a client separately. Do not adopt it if you want a single desktop app that manages itself and never sees a terminal, or if you expect the project to ship its own reading interface.
- Can I use it commercially?
- Yes, with conditions. MPL-2.0 is a weak copyleft licence: you can use it inside commercial and closed-source software, but if you distribute changes to its own files, you must publish those changes under the same licence.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly Java, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The problem: manga readers that live on one device
A phone manga reader keeps its library, its download queue and its reading progress inside one app on one device. Move to a tablet, a laptop or a Kobo and you either rebuild the library or accept that the two copies drift apart. Suwayomi-Server moves that state onto a machine you control and turns the reader into a client. The README describes it as "a free and open source manga reader server that runs extensions built for Mihon (Tachiyomi)". The audience is people who already self-host something, who are comfortable with a jar file or a Docker container, and who care more about keeping their library on their own hardware than about a polished out-of-the-box desktop experience. It is explicitly not a fork of Mihon, and the README states that plainly: Suwayomi is "an independent Mihon (Tachiyomi) compatible software". That distinction matters for anyone worried about the project inheriting upstream's direction.
How the server and its clients divide the work
The architecture is a server plus a user interface, and the README is blunt that you need both: "You need a client/user interface app as a front-end for Suwayomi-Server". Download the server release directly and you get a bundled copy of Suwayomi-WebUI, so the default path is a browser tab pointed at the server. Two clients are listed as integrated, meaning the server can keep them updated automatically: Suwayomi-WebUI and Suwayomi-VUI, both web apps and PWAs. Everything else in the client list is marked "potentially inactive or abandoned", including the desktop shells (Tachidesk-JUI, Tachidesk-VaadinUI, Moku, Tachidesk-Sorayomi, Tachidesk-qtui) and a KOReader plugin. That labelling is the most useful thing in the README for a prospective adopter: the maintained surface is the server plus the two web UIs, and the desktop wrappers that used to define the Tachidesk name are the part most likely to rot. The server itself is written in Java with Kotlin and Javalin in the topic list, and the README claims portability on the grounds that "any platform that runs java and/or has a modern browser can run it".
What the server actually provides
The feature list maps to concrete server-side jobs. It installs and executes Mihon extensions, which is how source support arrives without the server implementing each site itself. On top of that it offers searching and browsing of installed sources, a library with categories, automated library updates that check for new chapters, automated download of new chapters, a view of latest updated chapters, and offline download storage. Backups are Mihon-compatible, and the README notes automated backup creation. Tracking covers MyAnimeList, AniList, MangaUpdates and others. Cloudflare-protected sources are handled through FlareSolverr support rather than anything built in. There is an OPDS and OPDS-PSE endpoint at /api/opds/v1.2, which is the hook for e-reader software rather than a browser. Note the caveat the README puts above the list: those are capabilities of the server, and "the actual working support is provided by each front-end app". So a feature existing on the server does not guarantee your chosen client exposes it.
Getting it running: bundles, Docker, and the jar
The README splits installation into OS-specific bundles and other methods. The bundles ship "The Java Runtime Environment, ElectronJS and the Suwayomi-Launcher", so they avoid a separate Java install. Windows, macOS and GNU/Linux each get a section. Under other methods the README lists Docker, Arch Linux, Debian/Ubuntu and NixOS, which tells you the packaging effort has gone into Linux distributions first. The advanced path is running the jar release directly, which is the option for anyone on an architecture the bundles do not cover, and the README acknowledges that case directly: "If a bundle for your operating system or cpu architecture is not provided". There is also a section on using Suwayomi remotely, which is the mode where the server sits on one machine and clients connect over the network. The exact command lines for Docker, the jar invocation and the distro packages are not reproduced in the material available here, so check the README's own sections before running anything. What the material does establish is that the jar path requires a Java runtime you supply yourself, and that the bundled route does not.
Extension API churn is the real maintenance cost
The recent release titles are the most informative part of this repository for anyone estimating upkeep. Version v2.3.2243 is titled "SyncYomi Support, Extension API v1.6, and More! Fix 4", and the two releases before it are Hotfix 3 and Hotfix 2 of the same feature set. Three releases inside roughly ten days, all tagged as fixes or hotfixes, all built around an Extension API bump. That pattern says the extension interface moves, and when it moves, the server has to follow. For an operator this means the upgrade cost is not just pulling a new container: it is re-checking that your installed sources still load and that your client still talks to the server. The README's own warning that working support depends on the front-end compounds this, because an Extension API change can require a matching client update too. This is the strongest argument for the bundled WebUI, since the README says the server can keep integrated clients up to date automatically. It is also the strongest argument against pinning an old abandoned desktop shell.
Where it is the wrong tool, and what to use instead
If you read manga on one device and want an app you install and forget, this is the wrong shape entirely. You would be running a Java server, choosing a client, and maintaining both, to replace something that already worked. The README's own framing supports that reading: it tells you a front-end is required, and the desktop clients that once made this feel like a normal application are listed as potentially inactive or abandoned. The honest alternative is Mihon itself, the upstream app the extensions are built for. The difference in approach is not a feature comparison, it is where state lives. Mihon keeps the library on the device and talks to sources directly; Suwayomi-Server keeps the library on a host and serves it to clients. Suwayomi gains you multi-device access, a single download queue and an OPDS endpoint for e-readers. Mihon gains you a supported application with no server to patch. The README also notes you can point Mihon at a Suwayomi server, and describes a Suwayomi extension and tracker plus a merge source in Neko for syncing, so the two are not mutually exclusive. If you already read on Mihon and only want the library centralised, that sync route is a smaller change than replacing your reader.
Licence and what to verify before you commit
Suwayomi-Server is MPL-2.0. That is a file-level copyleft licence, which in practice means modifications to covered files have to be made available under the same terms if you distribute them, while you can combine the code with differently licensed files in a larger work. Running an unmodified server for yourself does not trigger distribution obligations. This is a description of the licence text, not legal advice; if you plan to redistribute a modified build, read the MPL-2.0 terms or get proper counsel. The README also carries a disclaimer section, which is worth reading given that the server executes third-party extensions. On the practical side, verify three things first. That the extensions for the sources you actually read still work against Extension API v1.6, since that version is what the current releases target. That your chosen client is one of the two integrated ones, because the rest are flagged as potentially inactive. And that the OPDS endpoint at /api/opds/v1.2 behaves with your e-reader software, since OPDS-PSE support varies between readers. If all three check out, the server is a reasonable home for a library you want to keep.
Editorial conclusion
Adopt Suwayomi-Server if you already run a home server, want your manga library on your own disk, and are willing to pick a client separately. Do not adopt it if you want a single desktop app that manages itself and never sees a terminal, or if you expect the project to ship its own reading interface. Before committing, verify that the extensions for your sources still load under the current Extension API version, and confirm the OPDS endpoint at /api/opds/v1.2 returns what your reader expects.
Community notes