Same engine. Same features. Same sync.
No analytics, no tracking. The only outbound call is a daily version check — one env var disables it.
curl -fsSL https://budgero.app/install.sh | bashThen run budgero serve to start the server.
Need help? Read the full setup guide
Maximum privacy and control over your financial data.
Same product, different responsibilities:
Everything from Budgero Cloud, running on your terms.
Run Budgero on your own server, NAS, Raspberry Pi, or any cloud provider you trust.
Your data is encrypted with your master password. Even on your own server, data stays protected.
Complete data ownership. Back up, migrate, or export anytime. No vendor lock-in.
Access your budget from any device through your self-hosted instance.
Your financial data never touches external servers. Complete privacy by design.
Easily import your existing YNAB budget. Keep your categories, transactions, and history.
Anything that runs Docker. A Raspberry Pi 4 (4GB+) is enough for a single user. A NAS, a small home server, or a $5/month VPS will comfortably handle a household. Budgero is a small Go binary and a SQLite-backed database — there is no Postgres, no Redis, no message queue, no Java. Resource use stays under 200MB of RAM in normal operation.
Yes. Synology DSM, Unraid, QNAP Container Station, and TrueNAS all run the official Budgero Docker image without modification. You point a single port at the container, mount a persistent volume for the SQLite database, and you are done. The full setup guide covers the NAS-specific paths.
Yes — Budgero ships multi-arch Docker images (linux/amd64 and linux/arm64), so a Raspberry Pi 4 or 5 works out of the box. A Pi Zero 2 W will technically run it, but for responsiveness a Pi 4 is recommended.
Yes — for any deployment beyond localhost, Budgero needs to be served over HTTPS. The zero-knowledge encryption runs in the browser via the Web Crypto API (window.crypto.subtle), which browsers only expose in secure contexts (HTTPS, or http://localhost). For LAN-wide or remote access the easiest path is a reverse proxy with automatic Let's Encrypt — Caddy is the simplest, Traefik and Nginx Proxy Manager also work well. If you'd rather skip certs entirely, Tailscale (HTTPS MagicDNS) and Cloudflare Tunnel both terminate TLS for you and require no port forwarding.
All data lives in a single SQLite file inside the volume you mounted. Snapshot the volume, copy the file with `docker cp`, or use any standard SQLite backup tool. Because Budgero is end-to-end encrypted on the device, even if you store backups in third-party cloud storage, the contents stay encrypted under your master password.
Pull the latest Docker image and restart the container. Database migrations run automatically on startup. The app shows a dismissable notice when a newer release is available, but you decide when to upgrade — the running container will keep working on the version you deployed for as long as you want. The Self-Hostable changelog is published alongside Cloud releases.
Yes. There is no telemetry, no license check, no analytics. The only routine outbound call is a daily update check against budgero.app that carries the version number of your install and nothing else — set UPDATE_CHECK_DISABLED=true and it never fires, with no loss of functionality. Optional currency exchange rates (currencylayer.com, your own API key) are the only other outbound call. You can run Budgero on a fully isolated network indefinitely.
Export your YNAB budget as CSV and use the import flow inside Budgero. Categories, transactions, and account structure come across. The import preview lets you confirm before anything is written, so you can iterate until the mapping is right.
Self-hosted Budgero handles authentication locally. You create accounts directly on your instance, and each user has their own encrypted workspace. For households, you can run a shared instance and invite household members. There is no SSO out of the box, but the auth layer is designed so you can put it behind your own reverse proxy (Authelia, Authentik, Tailscale) if you want.
Budgero is source-available, not OSI open source. The full source code is published in a public read-only GitHub mirror under the Functional Source License (FSL-1.1-Apache-2.0): you can read, audit, modify, and self-host it — the only restriction is offering it as a competing hosted service, and each release automatically converts to Apache 2.0 two years after publication. We are a small commercial project funded by the Cloud edition; self-hosters get a free Docker image with the full feature set, no license keys, no feature gating, and no telemetry beyond a disable-able daily update check (a version number, nothing else). Between the public source and the automatic Apache 2.0 conversion, your ability to keep running Budgero doesn't depend on our continued operation.
Self-Host has no license, no feature gates, and never will. If it earns a place in your homelab, you can support development with a one-time, pay-what-you-want donation.
Support BudgeroIf you're evaluating self-host because you outgrew another budgeting app, these comparisons might help.
YNAB-specific comparison — feature parity, import path, and what you give up by leaving the YNAB cloud.
Side-by-side feature comparison: privacy, multi-currency, offline mode, and pricing across both products.
For people leaving Monarch — multi-currency, works outside the US, and zero-knowledge encryption that Monarch doesn't offer.
Six budgeting apps compared on price, privacy, multi-currency, and self-hosting (including Actual Budget and Firefly III).
If you prefer zero setup, start with Budgero Cloud and get encrypted sync right away.
Start Cloud TrialPrefer zero setup? Budgero Cloud handles infrastructure, backups, and updates for you.
Coming from YNAB? See the self-hosted YNAB alternative comparison.