Wallos Review 2026: Self-Hosted Subscription Tracker

Wallos does one job. It tracks subscriptions and tells you when they renew. That is the whole product. The GitHub repo lists 8K+ stars, the site is wallosapp.com, and the software is free to self-host. If you want a budget app that pulls your bank transactions and categorizes your groceries, this is not it. If you want a small, private dashboard that answers "what am I paying for, and when does it hit my card," Wallos is built for exactly that.

I have not signed up for or run Wallos. This review works from the provider's own published material: the GitHub repository, the official docs, the Docker setup instructions, and the site at wallosapp.com. Where a number is not published, I say so rather than guess.

What Wallos is: subscription tracking, nothing else

The scope is narrow on purpose. You add a subscription, set the price, the billing cycle, and the next payment date. Wallos stores it, shows it on a calendar, and pings you before it renews. That is the loop.

What it deliberately does not do matters just as much:

• No bank sync. There is no Plaid, no Open Banking, no account linking. You type the subscription in yourself. The provider's docs describe manual entry, not aggregation.
• No full budgeting. No income tracking, no category budgets, no net-worth view, no transaction ledger. It is not a Mint replacement and does not pretend to be.
• No investment tracking. Different job entirely. If you want portfolio tracking, that is a separate tool.
• No bill negotiation or cancellation service. Wallos tells you a charge is coming. It does not call the vendor for you.

That narrowness is the point. A subscription tracker that tries to be a budget app usually does both badly. Wallos stays in its lane, and the feature set reflects that discipline.

Install and hosting in 2026

Wallos ships as a Docker container. The official docs walk through a Docker Compose file, and that is the path most people will take. The provider states the app supports SQLite and MySQL/MariaDB as database backends, so you can run it as a single container with a local file database or point it at a separate database server.

Docker compose

The compose file maps a port, mounts a volume for persistent data, and sets a few environment variables. On a home server or a small VPS, that is a five-minute job if you already run Docker. The docs cover the compose example and the environment variables you need to set. If you have never touched a compose file, budget an evening, not five minutes.

Reverse proxy and HTTPS

Wallos itself does not terminate TLS. You put it behind a reverse proxy — Caddy, Nginx, Traefik — and let the proxy handle the certificate. The docs assume this setup. Running it bare on a public IP without HTTPS means your login credentials and subscription list travel in clear text. Do not do that.

Database options

SQLite is the low-effort choice: one file, no separate service, easy to back up. MySQL or MariaDB is the choice if you want the database managed separately or you already run one. For a personal subscription list, SQLite is plenty. The provider lists both, so pick based on what you already operate.

Update path

Updates come as new container images. You pull the new image and restart the container. The repo publishes releases, and the release cadence is visible on GitHub. Before you pull, read the release notes — schema changes can require a migration step, and the docs describe the upgrade process. Skipping several versions at once is where people get into trouble.

Backup strategy

Back up the database and the data volume. With SQLite that means copying the database file while the container is stopped, or using a consistent snapshot. With MySQL, a dump. The provider does not run backups for you — there is no cloud account, no vendor holding your data. If your disk dies and you have no backup, the subscription list is gone. A weekly cron job that dumps the database to another machine covers it.

Feature tour: renewals, notifications, multi-currency

The feature set is small and specific. Here is what the provider documents.

Calendar view

Subscriptions appear on a calendar by next payment date. You see the month ahead and what lands when. This is the core screen — the reason to open the app at all. A list view shows the same data sorted by renewal date.

Notifications

Wallos sends renewal reminders. The provider documents multiple channels, including email, Discord, and ntfy. You configure the channel you want and set how many days ahead the reminder fires. ntfy is the one worth noting for self-hosters: it is a push service you can also self-host, so the reminder path stays inside your own infrastructure if you want it to. Email needs an SMTP server, which means either your own mail setup or a relay.

Multi-currency

Subscriptions can be priced in different currencies, and Wallos converts them for the totals. The provider documents currency conversion using exchange-rate data. That matters if you pay for services in USD, EUR, and GBP and want one number for monthly spend. Exchange rates move, so the converted total is an estimate, not a locked figure.

Custom payment cycles

Not everything bills monthly or yearly. Wallos supports custom cycles — weekly, quarterly, every N days, and so on. The docs describe setting the cycle per subscription. This is where a spreadsheet gets annoying and a purpose-built tracker earns its place.

Tagging and categories

You can tag subscriptions and group them. Categories let you separate work tools from streaming from software licenses. The provider documents tagging as an organizing feature. It is not a budgeting category system with limits — just labels for filtering and reporting.

Spend stats

Wallos shows totals and breakdowns of what you spend on subscriptions. The provider describes spend statistics as part of the dashboard. It answers "how much per month, how much per year, and where is it going" without any bank connection.

Cost math: self-hosted vs paid trackers

Wallos itself costs nothing. The provider lists the software at no charge. The real cost is the infrastructure and the time.

What you actually pay for:

• A place to run it. A small VPS, or a home server you already own. VPS prices vary by provider and region; check current listings rather than trusting a number from a review. A home server you already run adds nothing to the bill.
• A domain, if you want one. Optional. You can reach it by IP on your local network. A public domain costs whatever your registrar charges, and prices change — check the registrar's current schedule.
• Your time. This is the real line item. Initial setup is an evening if you know Docker. Ongoing upkeep is small but not zero: updates, backups, certificate renewals if your proxy does not automate them, and the occasional broken dependency.

Compare that to a paid subscription tracker. Rocket Money has a free tier and a paid tier; the paid tier's price is set by Rocket Money and changes, so check their current schedule rather than a figure quoted in an old review. The trade is straightforward: a paid tracker does the bank sync and categorization for you and charges a recurring fee. Wallos charges no fee but asks for manual entry and a server.

My read: if you already run a home server and you enjoy this kind of thing, the marginal cost of Wallos is close to zero and the privacy gain is real. If you do not run a server and have no interest in learning Docker, the time cost of standing one up exceeds the value of tracking a dozen subscriptions, and a paid app is the cheaper decision once you price your own hours.

There is a middle path worth naming: a spreadsheet. It costs nothing, needs no server, and handles a dozen subscriptions fine. Wallos beats a spreadsheet on reminders and calendar view, not on raw tracking. If you never miss a renewal and do not care about notifications, the spreadsheet wins on effort.

Security and privacy model

The privacy story is the reason people pick self-hosted tools, and it is worth being precise about what it does and does not give you.

What you get:

• Data ownership. The subscription list lives in your database, on your hardware. No vendor account, no third party holding your spending data.
• No bank credentials shared. Because there is no bank sync, you never hand read access to your accounts to anyone. That removes a whole class of risk that comes with aggregator-based apps.
• Authentication. Wallos has a login. The provider documents user accounts and authentication. Treat that login as the only thing between the internet and your data.

What you take on:

• You are the security team. Patching, TLS, firewall, and access control are your job. The provider ships the app; it does not harden your server.
• Exposure risk. A Wallos instance open to the internet is a login page anyone can reach. Weak passwords get brute-forced. If you expose it publicly, put it behind HTTPS, use a strong unique password, and consider restricting access by IP or putting it behind a VPN.
• No vendor incident response. If your server is compromised, there is no support line. Backups are your recovery plan.

A hardening checklist I would apply before exposing an instance:

• HTTPS only, via reverse proxy, with a valid certificate.
• Strong, unique password; no reuse from other sites.
• Firewall rules that allow only the ports you need.
• Automatic security updates on the host OS.
• Regular database backups stored off the server.
• Consider a VPN or IP allowlist instead of public exposure.
• Keep the container image current; do not run a version from a year ago.

None of this is exotic. It is the baseline for running any self-hosted service that holds personal data. The point is that the privacy benefit is real only if you do the work.

Wallos vs alternatives

Rocket Money

Different category. Rocket Money connects to your bank accounts, finds subscriptions automatically, and offers cancellation help. It has a free tier and a paid tier; check Rocket Money's current pricing for the paid plan. Wallos does none of the automatic detection and none of the cancellation. If you want the app to find subscriptions you forgot about, Rocket Money does that and Wallos cannot. If you want no bank connection at all, Wallos is the fit. See our Rocket Money page for the other side of that comparison.

Ghostfolio

Also self-hosted, also open source, different job. Ghostfolio tracks investments and portfolios. It does not track subscription renewals. Comparing them is a category error — you would run both if you wanted both jobs done. Our Ghostfolio page covers what it does.

Maybe Finance

Another self-hosted personal finance project, broader in scope than Wallos. It aims at the full financial picture rather than subscriptions alone. If you want one self-hosted app for everything, that is a different bet than a narrow tracker. Our Maybe Finance page has the details.

Spreadsheets

The honest baseline. Free, no server, no updates, works forever. Loses on reminders, calendar view, and multi-currency conversion. Wins on setup time and maintenance. For under ten subscriptions, the spreadsheet is genuinely competitive.

Other self-hosted finance tools

The self-hosted finance space has several projects with overlapping goals. Wallos is the narrowest of them — subscriptions only. That narrowness is either the reason you pick it or the reason you skip it.

Verdict: score by category

Scoring a narrow tool against broad ones is unfair, so here is the breakdown by what Wallos actually claims to do.

• Setup effort: 3/5. Docker Compose is documented and straightforward if you know Docker. If you do not, the learning curve is real. Not a one-click install.
• Features: 4/5. For subscription tracking specifically, it covers the bases: calendar, reminders across multiple channels, multi-currency, custom cycles, tags, spend stats. It does not try to do more, and that is fine.
• Privacy: 5/5. No bank sync, no vendor account, data on your hardware. The strongest privacy position of any option in this comparison, provided you secure the instance.
• Upkeep: 3/5. Updates, backups, and TLS are on you. Low ongoing effort once set up, but not zero, and it never becomes zero.

Best fit: someone who already runs a home server or VPS, is comfortable with Docker, wants no bank connection, and wants renewal reminders without paying a subscription to track subscriptions. Poor fit: someone who wants automatic subscription detection, has no server, or has no interest in maintaining one. For that person, a paid tracker or a spreadsheet is the better call.

Wallos is a small tool that does a small job well. Judge it on that, not on what it refuses to be.

How this review was researched

This review is based on the provider's own published material: the Wallos GitHub repository (stars, releases, and issue tracker), the official documentation covering Docker setup, database options, notifications, and currency handling, and the official site at wallosapp.com. No account was created, no instance was deployed, and no subscription data was entered. Where the provider does not publish a figure — hosting costs, exchange-rate sources, or third-party pricing — this review says so and points you to the current schedule rather than quoting a number that may be stale. For our broader review standards, see our methodology page.