A self-hosted cross-site manga tracker, honestly reviewed. No marketing fluff, just what you get when you run it yourself.

TL;DR

What it is: A self-hosted web application for tracking manga reading progress across multiple source sites — Manga Plus, MangaDex, MangaHub, and others — from a single dashboard [README].
Who it’s for: Manga readers who follow series across different scanlation and official sites and want one place to track reading progress without signing up for cloud accounts on each [README].
Cost savings: The main comparison isn’t against paid SaaS — most manga trackers (MyAnimeList, AniList, MangaUpdates) are free. The value here is data ownership and avoiding account lockout when services change their terms or shut down.
Key strength: The Multimanga feature is genuinely useful — it groups the same series across multiple sources so you get one dashboard card, one notification, and one “mark as read” action regardless of which site has the freshest chapter [README].
Key weakness: 130 GitHub stars and a single developer. This is a personal project that happens to be polished, not a venture-backed company. The license field returns NOASSERTION, meaning the licensing terms are not clearly declared in the repository metadata [merged profile].

What is Mantium

Mantium is a web application that tracks manga chapters across multiple source sites. You add a series, set your reading status (reading, dropped, completed, on hold, plan to read), mark the last chapter you read, and configure how often Mantium should check for new chapters. When a new chapter drops, you get notified. That’s the whole loop [README].

What Mantium explicitly does not do is download chapter images or serve as a manga reader. It retrieves metadata: series title, cover image, chapter numbers, chapter URLs. You still click through to the source site to read. Mantium is a reading tracker and notification layer, not a Kavita or Komga replacement [README].

The project was built by a single developer (diogovalentte) and hit v1.0 in September 2024, adding search forms, pop-up interactions, MangaUpdates support, and Tranga integration [1]. Three weeks later, v2.0 shipped with Custom Manga support and the Multimanga feature that became the project’s most distinctive capability [2]. As of this review it sits at 130 stars with 7 forks on GitHub — a small but active project.

Natively supported sources include Manga Plus (Shueisha’s official English platform), MangaDex, MangaHub, MangaUpdates, RawKuma, KLManga, and JManga. For everything else, the Custom Manga feature lets you manually manage chapters from any site [README].

Why people choose it

There are almost no third-party reviews of Mantium beyond brief mentions in the selfh.st weekly newsletter when new versions shipped [1][2]. That’s expected for a 130-star project. What you find instead is a pattern common in r/selfhosted discussions about manga tracking: frustration with fragmentation.

The problem Mantium solves is real. Manga series switch sources constantly — an official publisher picks up a title, a scanlation group drops it, a site goes down, region restrictions change which platform has a given series. Readers end up with a mental map of “I’m on chapter 47 of this one on MangaDex, chapter 23 of that one on MangaHub” with no unified view. Commercial alternatives like MyAnimeList and AniList require account creation, store your data on their servers, and don’t have fine-grained per-chapter tracking tied to specific source URLs [README].

Mantium’s answer is the Multimanga container. When you add a series, even if you’re tracking it on three different sites simultaneously, it shows as one card in the dashboard, sends one notification, and requires one “mark as read” update. The system automatically selects which source to surface as the “current” entry based on the highest chapter number or most recent release date [README]. That’s a legitimately clever solution to a genuinely annoying problem.

The iFrame endpoint is the other feature that differentiates it from a simple list app. If you run a personal dashboard (Homarr, Dashdot, any homepage tool that accepts embeds), you can pull a minimalist unread-manga widget directly into your existing setup without opening a separate app [README]. The selfh.st newsletter [2] flagged the v2.0 release as notable for the custom and multi manga additions — the community noticed the feature, even if detailed review coverage hasn’t followed.

Features

Tracking and status:

Per-series status: reading, completed, dropped, on hold, plan to read [README]
Manual or URL-based manga addition for supported sites [README]
Name-based search for natively supported sources [README]
Last-read chapter tracking per series [README]
Periodic background checks configurable per instance (e.g., every 30 minutes) [README]
Notifications on new chapter detection [1][README]

Multimanga:

Groups the same manga across multiple sources into one dashboard entry [README]
Automatic current-source selection based on highest chapter number or most recent release [README]
Single notification and single “mark as read” regardless of source count [README]
Manual override of current source and cover image [README]

Dashboard:

Grid and list display modes [README]
Sorts unread manga to the top by default, with animation highlight [README]
Sidebar with name filter, status filter, and sort options (name, last chapter read, last uploaded chapter, chapter count, unread priority) [README]
Column count and display mode configurable per user [README]

iFrame:

Embeddable endpoint showing only unread manga with reading or completed status [README]
Designed for external dashboard integration [README]

Custom Manga:

Manual chapter management for sites Mantium doesn’t natively support [README]
Allows tracking of nearly any manga source with manual updates [README]

Technical:

REST API [merged profile]
Docker and Docker Compose deployment [README]
PostgreSQL backend [merged profile]
Tranga integration (a separate manga downloader/tracker tool) [1]
Separate API and dashboard Docker images [README]

Pricing: SaaS vs self-hosted math

This is where the Mantium framing differs from most self-hosted software reviews. The main alternatives to Mantium — MyAnimeList, AniList, MangaUpdates — are free cloud services. The cost argument for self-hosting Mantium isn’t about saving a monthly bill. It’s about something else.

What free cloud trackers cost you:

Account creation and personal data on someone else’s server
Reading history tied to a platform that can change API terms, go read-only, or shut down (MangaFox, Manga Rock, and dozens of others have done exactly this)
No cross-site chapter URL tracking — these services track titles, not which specific source chapter you last read

What self-hosting Mantium costs:

A VPS running Docker: $4–6/month on Hetzner or Contabo covers a machine that will run Mantium alongside other services comfortably
Your time to set it up: 30–60 minutes for a technical user following the Docker Compose path

If you already run a homelab or self-hosted stack, Mantium adds negligible marginal cost. If Mantium would be your first self-hosted app, the $5/month VPS cost is the real number — compare that against the risk of losing your tracking history when a free service changes its model.

Data isn’t available on any commercial manga-specific tracking SaaS that Mantium directly replaces at a cost. The value proposition is sovereignty over reading data, not dollar savings.

Deployment reality check

Mantium ships with a docker-compose.yml in the repository root. The default setup runs two containers: one for the API (Go backend) and one for the dashboard (frontend), backed by a PostgreSQL database. There are separate Dockerfiles for each component (Dockerfile_API, Dockerfile_dashboard) [README].

What you need:

A Linux VPS or homelab machine with Docker and docker-compose
PostgreSQL (included in the default compose setup or external)
A reverse proxy (Caddy or nginx) for HTTPS if exposing beyond localhost
An .env file configured from the provided .env.example

What can go sideways:

The NOASSERTION license status is the first thing to flag. The GitHub repository metadata doesn’t return a recognized SPDX license identifier. There’s a LICENSE file in the repo, but automated tooling couldn’t parse it into a standard identifier [merged profile]. If you’re in a corporate environment or building something on top of Mantium, read that LICENSE file directly before proceeding. For personal use, this is unlikely to matter.

The project is a single-developer effort. There are 640 commits in the history [website scrape], which shows steady development, but there’s no company, no commercial backing, and no team behind it. If the developer stops maintaining it, you’re on your own. The 7 forks means the community isn’t large enough to guarantee a maintained fork if the project goes dormant.

Notifications require additional setup depending on your preferred channel. The README documents Tranga integration [1], but notification infrastructure (email SMTP, Telegram, etc.) isn’t bundled — you configure the integration separately.

Custom Manga covers the “site not in the supported list” case, but it’s manual. You’re adding chapters yourself, not getting automatic updates. For any series on an unsupported site, this degrades from a tracker to a manual list [README].

Realistic time estimate: 30 minutes for a technical user with Docker experience and an existing VPS. 2–3 hours for someone setting up Docker for the first time, including reverse proxy and HTTPS configuration.

Pros and Cons

Pros

Multimanga is a genuinely useful abstraction. Tracking the same series across three sites as one unified entry, with automatic source selection and single notifications, solves a real fragmentation problem [README][2].
iFrame embedding. Drop the unread manga widget into any dashboard that accepts HTML embeds. Clean, minimal, useful [README].
REST API included. Programmatic access to your tracking data for scripting, automations, or custom integrations [merged profile].
Active development cadence. v1.0 and v2.0 shipped in the same month (September 2024), both adding substantial features [1][2]. 640 commits in the history suggests sustained work.
Docker Compose deployment. Standard, documented, no exotic dependencies.
Custom Manga fallback. No source support for a site? You can still manually track it without abandoning the tool [README].
Tranga integration. If you also use Tranga for manga management, the two tools connect [1].

Cons

Single-developer project at 130 stars. This is a personal tool that’s been released. That’s not inherently bad, but it means no team, no commercial backing, no SLA, and no guarantee of long-term maintenance [merged profile].
NOASSERTION license. The license isn’t cleanly declared in repository metadata. Read the actual LICENSE file before deploying in any context where licensing matters [merged profile].
No native reading support. Mantium is purely a tracker. You still need to open the source site to read. If you want one app that both organizes and serves manga, you need a different tool (Komga, Kavita) or a combination [README].
Custom Manga is manual. Sites outside the supported list require manual chapter entry — no automatic scraping or detection [README].
No mobile app. The iFrame helps for embedding in dashboards, but there’s no native iOS or Android client. The web UI needs to be responsive enough for mobile use.
Notifications require separate setup. Notification channels (beyond the Tranga integration) aren’t bundled [1].
No community to speak of. 7 forks and minimal third-party coverage mean you’re likely debugging solo if something breaks.

Who should use this / who shouldn’t

Use Mantium if:

You read manga across multiple sites (MangaDex, Manga Plus, etc.) and want a single dashboard instead of mental bookmarks per site.
You’re already running a self-hosted stack and want to add a manga tracker with minimal overhead.
You want your reading history on your own server, not subject to AniList or MyAnimeList account policies.
You use a dashboard tool like Homarr or Homepage and want an embeddable unread-chapters widget.
You’re comfortable with Docker Compose and a 30-minute setup.

Skip it if:

You read manga on one site only — the Multimanga feature is its main differentiator, and you don’t need it.
You want a manga reader, not just a tracker. Komga or Kavita serve downloaded files; Mantium tracks URLs to external sites.
You need long-term stability guarantees. A single-developer project with 130 stars can’t promise that.
You want a mobile-first experience.
You’ve never used Docker and don’t want to learn — the setup is reasonable, but it’s not a one-click install.

Stick with AniList/MyAnimeList if:

You’re fine with a cloud account and the main thing you want is social features (community ratings, recommendations, friend lists).
You track anime alongside manga and want unified tracking in one place.

Alternatives worth considering

Komga — Self-hosted manga server and reader for files you’ve downloaded locally. Different use case (reading owned files vs. tracking external sources), but often mentioned together. More stars, more community, more established [selfhostsource.com context].
Kavita — Similar to Komga. Self-hosted reading server for local files. Not a tracker for external sources.
Tachiyomi / Mihon — Android app that reads directly from sources. Not self-hosted in the server sense, but solves the cross-site reading problem on mobile without a server setup.
AniList — Free cloud tracker. Social features, anime + manga unified, no setup. The thing you’d use if you don’t want to self-host.
MyAnimeList — The original. Larger community, more reviews, more integrations. Cloud, account required.
MangaUpdates — Natively supported as a source by Mantium, and also a standalone tracker. More focused on series metadata and release tracking.
Tranga — A different tool that Mantium integrates with, focused on manga downloading and library management. Complements rather than replaces Mantium [1].

For someone who wants self-hosted manga tracking specifically (not reading), Mantium is the most feature-complete option in the space at this star count. The main question is whether you trust a single-developer project for long-term use.

Bottom line

Mantium is a polished personal project solving a specific problem well: fragmented manga tracking across sources that don’t talk to each other. The Multimanga feature — one card, one notification, one chapter update for a series tracked across three sites — is the kind of thing you’d build yourself if you were frustrated enough and knew Go. Someone was, and they did, and they released it. At 130 stars it’s not a community tool yet, and the unclear license and single-developer status are real considerations before betting your reading history on it. But if you already run Docker containers at home and follow manga across MangaDex, Manga Plus, and whoever else happens to have the latest chapter of your series, this is worth the 30-minute setup time.

Sources

Ethan Sholly, selfh.st — “This Week in Self-Hosted (6 September 2024)” — mentions Mantium v1.0.0 release with search form, pop-up forms, MangaUpdates support, and Tranga integration. https://selfh.st/weekly/2024-09-06/
Ethan Sholly, selfh.st — “This Week in Self-Hosted (27 September 2024)” — mentions Mantium v2.0.0 release with custom manga and multi manga support. https://selfh.st/weekly/2024-09-27/
selfhostsource.com — “Software — Self-Hosted Software Directory” — includes Mantium in the self-hosted software catalog. https://selfhostsource.com/software/