Privacy-first subscription tracker

Self-host Wallos and see every renewal before it charges.

Wallos is an open-source subscription tracker for recurring costs, renewal dates and reminders. Deploy your own instance on VibeNest with persistent SQLite data, uploaded logos and free SSL.

Free tier validated No paid key required Persistent SQLite + logos GPL-3.0

Manual entry, private by default

Track services, prices, billing cycles, renewal dates and categories without connecting a bank account or sending financial history to a subscription SaaS.

Comfortable on Free

The validated 256 MB / 0.5 CPU run peaked at 19.48 MB RAM while onboarding, uploading a logo and adding a subscription.

Your records survive deploys

Separate persistent volumes keep the Wallos database and uploaded subscription logos across container restarts and redeploys.

Deploy Wallos in one click

  1. 1. Launch Wallos VibeNest opens the prepared Docker Compose adapter with the correct branch, port and persistent volumes.
  2. 2. Create the first owner Open the project as soon as it is live. The first account owns the instance; public registration then stays closed.
  3. 3. Add recurring costs Enter subscriptions, billing cycles and renewal dates. Core tracking works immediately without an API key.

Wallos vs Actual Budget

Choose Wallos when the job is narrow: keep a clean list of subscriptions, see monthly and yearly recurring costs, and get renewal reminders. It is lighter than a complete budgeting system and does not need bank access for its core workflow.

Choose Actual Budget when you need envelope-style budgeting, transaction importing, account reconciliation and local-first budget sync. Wallos complements that workflow; it is not a replacement for a full ledger.

Optional integrations stay optional

Fixer is only needed for automatic exchange-rate updates. AI helpers and email, Telegram, Gotify, Pushover or other notifications use credentials you supply. None of them is required to add subscriptions or review recurring spend.

Storage and backup notes

Keep both named volumes attached: /var/www/html/db stores SQLite state and /var/www/html/images/uploads/logos stores uploaded logos. The Free profile deliberately caps PHP requests and backup uploads at 64 MB; use a paid hardware tier for larger restores.

Source, VibeNest recipe and live proof

Original open-source project

Review the upstream source, release notes and GPL-3.0 license before you deploy or update the app.

Original GitHub

VibeNest-ready recipe

VibeNest adapter pins the official Wallos 5.8.1 image, runs two on-demand PHP workers under a 64 MB PHP request limit, and persists both SQLite data and uploaded logos. Core tracking works without paid API keys; Fixer currency updates, AI and notification providers are optional.

Deploy repository

Public deployment proof

Public URL opened the real Wallos login; registrations closed after the first owner account; Coolify reported running:healthy after restart and redeploy.

Open live deployment

Frequently asked questions

What is Wallos? +

Wallos is an open-source, self-hosted subscription tracker for recurring costs, renewal dates, categories, currencies, payment history and reminders.

Does Wallos need a paid API key? +

No. Subscription tracking, dashboards and manual renewals work without any paid key. Fixer currency updates, AI features and notification providers are optional integrations.

Does Wallos fit the VibeNest Free tier? +

Yes. The production validation ran with a 256 MB RAM and 0.5 CPU limit; the measured RAM peak was 19.48 MB during onboarding and a basic subscription workflow.

Is Wallos an alternative to Actual Budget? +

Only for subscription tracking. Wallos is purpose-built for recurring charges and reminders; Actual Budget is the better choice for transaction imports, envelope budgeting, reconciliation and full household budgets.

Will my data survive a redeploy? +

Yes. The adapter persists both the SQLite database and uploaded logos. A real test subscription and logo survived restart and redeploy validation.

What should I do after the first deploy? +

Open the URL immediately and create the first owner account. Keep public registration closed, use a strong private password and arrange backups before entering important data.

Deploy your private subscription tracker

Start with a measured Wallos adapter, then keep recurring-cost data, renewal dates and logos in one instance you control.

Deploy Wallos

Reconnecting to the server...

Reconnecting in sec.

Failed to reconnect.
The page will reload automatically.

Session paused by the server.

Failed to resume the session.
Reloading the page...