
Self-hosted personal finance OS — cash flow, net worth, budgets, and every income stream you own. Fr
Self-hosted personal finance OS — cash flow, net worth, budgets, and every income stream you own. Fr
Most finance apps show you a pie chart of last month's spending and call it a day. Aurum goes further.
It's built for people who don't just want to log transactions — they want to understand the mechanics of their money: how capital grows or shrinks over time, which assets are pulling their weight, which subscriptions are quietly draining them, and which income streams are actually passive versus which just look that way on paper.
Aurum treats your financial life as a system, not a spreadsheet.
Log income, expenses, and transfers across as many accounts as you want, organized into categories (with one level of subcategories) plus free-form tags, and searchable. One purchase spanning multiple subcategories of the same parent (a grocery receipt part "Sweets", part "Alcohol") can be recorded as a single split transaction instead of several — every report and chart still counts each share under its own category. Already have history elsewhere? Import a bank's CSV export in a guided 3-step wizard instead of typing every line by hand — with built-in profiles for T-Bank, monobank and PrivatBank exports (columns, date/amount formats and declined-payment rows handled automatically), and manual column mapping for everything else. A dedicated Cash Flow view charts income vs. expense month by month.
A live net worth timeline (30 days to all-time) aggregating cash and every manually tracked asset — investments, crypto, real estate, vehicles, precious metals — into one number, with a full breakdown by asset class, by how each asset behaves (income / neutral / drain), and by risk level.
A CoinMarketCap-style portfolio tab for the coins you actually hold: live price plus 1h/24h/7d change, your holdings value, average buy price, and profit/loss — computed from a full buy/sell history, no separate portfolio tracker needed. Refresh on demand with one button, or let it auto-refresh once a day; either way it plugs straight into the Net Worth engine above as just another tracked asset.
Set a monthly limit per category and watch progress bars fill up. Track savings goals with a running contribution log. Register recurring bills and post them with one click when they're due — nothing runs automatically in the background.
Rank every category by total spend over any custom period to find what's actually eating your budget. A rules-based Advice tab surfaces rising spending categories, unbudgeted top expenses, and month-over-month savings rate trends in plain language.
A standalone ROI calculator: enter what you'd invest and what it would pay you monthly, and see the annual return, payback period, and a compound-interest projection — with a year-by-year comparison chart of compounding vs. just banking the cash — before you commit to a purchase.
Aurum watches your numbers in the background and surfaces a warning the moment something crosses a threshold you configure: a sustained negative cash flow streak, a declining net worth trend, an over-budget category, too much capital sitting at risk, or cash sitting idle in an account for too long.
Full Russian/English UI with a language switch in Settings, a light/dark/system theme toggle, and every screen designed mobile-first from day one.
Export your entire dataset — accounts, transactions, assets, budgets, goals — to a single JSON file at any time, and restore it later on a fresh install.
Aurum ships as three containers — Postgres, a FastAPI backend, and an nginx-served frontend — wired together with Docker Compose. No local Python, Node, or Postgres installation needed; Docker is the only requirement.
You need Docker Engine and the Docker Compose plugin (the docker compose command, not the older standalone docker-compose).
Confirm both are available:
docker --version
docker compose versiongit clone https://github.com/Zproger/Aurum.git
cd AurumCopy the template and open it in an editor:
cp .env.example .envAt minimum, change these two before going any further:
| Variable | What it does |
|---|---|
AURUM_POSTGRES_PASSWORD |
Password for Aurum's own Postgres container. The template ships with change-me on purpose — replace it with something real. |
AURUM_BASIC_AUTH_USER / AURUM_BASIC_AUTH_PASSWORD |
Aurum has no login screen of its own. Leave these blank and the app has no password at all — fine if it's only reachable from localhost, not fine anywhere else. Set both to put an HTTP Basic Auth prompt in front of the whole app. See Security & Self-Hosting below. |
Everything else in .env (currency, CORS, the port Aurum listens on) has a sensible default and can be left alone for a first run.
docker compose up -d --buildThis builds the backend and frontend images, starts Postgres, waits for it to report healthy, then starts the backend (which runs every database migration automatically — nothing to do by hand) and finally the frontend. First run takes a minute or two; after that, images are cached and it's seconds.
Visit http://localhost:3000 (or whatever port you set via AURUM_WEB_PORT in .env). A default account and the standard expense/income categories are seeded automatically — there's nothing to configure before you can add your first transaction.
docker compose psAll three containers (db, backend, web) should show healthy. If web or backend doesn't, check its logs:
docker compose logs backend
docker compose logs webdocker compose down # stop everything, keep your data
docker compose up -d # start it again later
docker compose down -v # stop AND permanently delete your data — be sure
git pull && docker compose up -d --build # update to newer codeYour data lives in a Docker named volume (aurum_pgdata), not in the repo folder — it survives docker compose down, image rebuilds, and git pull. It's only gone if you explicitly run docker compose down -v or delete the volume yourself. For anything short of that, use the in-app Settings → Backup & Restore to export a JSON snapshot of everything before making risky changes.
Everything Aurum's UI can do — adding transactions, managing accounts and budgets, importing a CSV,
tracking assets, exporting a backup — is also available as a plain JSON REST API at /api, so you
can script Aurum or connect it to other programs. See DOCS.md for the full reference,
or open /api/docs on your running instance for interactive Swagger docs.
Aurum has no built-in login system. It's built for one person to self-host one private instance of their own financial data — not as a multi-tenant service with per-user accounts. That's a deliberate trade-off, not an oversight, but it means:
AURUM_BASIC_AUTH_USER / AURUM_BASIC_AUTH_PASSWORD unset in .env, anyone who can reach the container can read, edit, and delete all of it — no password prompt at all. The app itself now says so on first load, with a warning you have to dismiss. This is fine if Aurum is only reachable from localhost.Both default to "this machine only", so opening Aurum up is a deliberate act rather than something that happens by accident:
| Variable | Default | What it does |
|---|---|---|
AURUM_BIND_ADDRESS |
127.0.0.1 |
Which host interface the port is published on. The default means nothing else on your network can connect, even on the same Wi-Fi. Set 0.0.0.0 to open it. |
AURUM_ALLOWED_HOSTS |
localhost 127.0.0.1 |
Hostnames Aurum answers to; anything else gets a 421. This blocks DNS rebinding, where a site you're browsing points its own domain at 127.0.0.1 and reads your instance through your own browser. |
If you open the bind address, add whatever you type in the address bar to AURUM_ALLOWED_HOSTS too — the LAN IP, your domain, a .local name. Forgetting the second one is the usual cause of a 421 on an otherwise working setup.
Aurum speaks plain HTTP by design — certificates belong to a dedicated terminator, not to the app's own nginx. Basic Auth sends your password on every request, so without TLS anyone who can see the traffic has it.
A ready-to-use Caddy setup ships with the repo (docker-compose.tls.yml + Caddyfile). It gets a Let's Encrypt certificate on first start and renews it by itself:
# in .env — a real domain pointing at this host
AURUM_DOMAIN=aurum.example.com
AURUM_ALLOWED_HOSTS=aurum.example.com
docker compose -f docker-compose.yml -f docker-compose.tls.yml up -d --buildCaddy then owns ports 80 and 443 (80 stays open for the ACME challenge and the HTTPS redirect), the web container stops publishing a port of its own, and HSTS is added at the proxy — deliberately there and not in nginx.conf, since promising browsers "never use plain HTTP for this host again" is only safe once TLS is actually in front.
If you find a security issue, please open a private report via GitHub's Security tab rather than a public issue.
Aurum is built in the open, for everyone. Contributions of all kinds are welcome — code, design, documentation, ideas, and bug reports. See CONTRIBUTING.md for how to get a dev environment running and what a good pull request looks like.
Aurum is released under the PolyForm Noncommercial License 1.0.0.
In plain terms: you can read the code, self-host it, modify it, and use it for any personal, educational, or noncommercial purpose, for free, forever. What you can't do is take it (or a modified version of it) and sell it, host it as a paid service fo
No open issues yet, or sync has not completed.