Skip to main content
OSSAlt

How to Self-Host Actual Budget: Personal Finance 2026

·OSSAlt Team
actual-budgetpersonal-financebudgetingself-hostingdockerynab2026
Share:

TL;DR

Actual Budget (MIT, ~15K GitHub stars, JavaScript) is a zero-based budgeting app — the same methodology as YNAB (You Need a Budget) but self-hosted and free. YNAB charges $14.99/month ($179.88/year). Actual Budget runs on your server, syncs across your devices, and supports bank import via OFX/CSV files or Simplifi/GoCardless integrations. Your financial data stays entirely on your hardware.

Key Takeaways

  • Actual Budget: MIT, ~15K stars — zero-based budgeting, reports, reconciliation
  • Local-first sync: Changes sync between your devices without sending data to any cloud
  • Import transactions: OFX/CSV import from any bank's export feature
  • Reports: Spending breakdown, net worth, budget vs actual comparisons
  • Rules engine: Auto-categorize transactions based on payee patterns
  • vs YNAB: Same methodology, free, self-hosted — no $15/month subscription

Zero-Based Budgeting Basics

Actual Budget follows zero-based budgeting:

  1. Every dollar has a job — assign all income to categories before spending
  2. Give every dollar a budget — groceries, rent, car, entertainment, savings
  3. Track actual spending — import transactions, match to categories
  4. Budget the future — not last month's income, but this month's actual available money
Income this month: $5,000

Budget:
├── Housing: $1,500
├── Groceries: $500
├── Transportation: $300
├── Utilities: $150
├── Entertainment: $200
├── Eating out: $200
├── Savings: $1,500
├── Emergency fund: $300
└── Buffer/miscellaneous: $350
    ─────────────────────
Total budgeted: $5,000 ← Every dollar assigned

Part 1: Docker Setup

# docker-compose.yml
services:
  actual:
    image: actualbudget/actual-server:latest
    container_name: actual-budget
    restart: unless-stopped
    ports:
      - "5006:5006"
    volumes:
      - actual_data:/data
    environment:
      ACTUAL_HTTPS_KEY: ""   # Leave empty to use Caddy for TLS
      ACTUAL_HTTPS_CERT: ""
      NODE_ENV: production

volumes:
  actual_data:

docker compose up -d

Visit http://your-server:5006

Part 2: HTTPS with Caddy

budget.yourdomain.com {
    reverse_proxy localhost:5006
}

Part 3: First Setup

Create your budget

  1. Visit https://budget.yourdomain.com
  2. Create new file → name your budget (e.g., "Personal 2026")
  3. Set password (optional but recommended)

Add accounts

  1. + Add account
  2. Name: Checking, Savings, Credit Card, Investment
  3. Account type: Checking / Savings / Credit card / Asset / Liability
  4. Starting balance: your current balance

Add budget categories

Default categories to create:

Income
├── Paycheck
└── Freelance income

Housing
├── Rent/Mortgage
└── Utilities

Food
├── Groceries
└── Eating out

Transportation
├── Car payment
├── Gas
└── Public transit

Personal
├── Entertainment
├── Clothing
└── Health/Medical

Savings
├── Emergency fund
├── Retirement
└── Vacation fund

Part 4: Import Bank Transactions

OFX/QFX/CSV import

  1. Log into your bank → Export transactions → OFX or CSV
  2. In Actual: Account → Import transactions
  3. Select your exported file
  4. Actual auto-maps columns for CSV:
    • Date, Payee, Amount (negative = expense)

Auto-import with SimpleFIN Bridge (US banks)

# SimpleFIN Bridge provides bank connectivity for ~$1.50/month:
# 1. Get access token from simplefin.org
# 2. In Actual: Settings → Show advanced settings → Enable SimpleFIN sync
# 3. Add SimpleFIN token
# 4. Link your bank accounts

GoCardless (European banks)

# Add environment variables:
environment:
  ACTUAL_NORDIGEN_SECRET_ID: "your-gocardless-secret-id"
  ACTUAL_NORDIGEN_SECRET_KEY: "your-gocardless-secret-key"

Part 5: Budget Workflow

Monthly budgeting

  1. Budget tab → shows current month
  2. Available to budget → your unassigned income
  3. For each category: type in how much you're budgeting
  4. Goal: Available to budget = $0 (every dollar assigned)

Rollover (carryover)

Categories can roll over unspent money:

  • Grocery budget: $500, spent $430 → $70 rolls to next month
  • Helps smooth irregular expenses

When you overspend a category

Entertainment budget: $200
Spent: $250
Overspent by: $50

Options:
1. Move $50 from another category (e.g., Buffer)
2. Let it reduce next month's available money

Part 6: Transaction Rules

Auto-categorize transactions based on patterns:

  1. More → Rules → + Create rule
  2. Condition: Payee contains "TRADER JOE"
  3. Action: Set category to Groceries
  4. Apply to: New transactions
Rule examples:
- "NETFLIX" → Entertainment
- "SHELL" or "CHEVRON" → Transportation/Gas
- "AMAZON" → Shopping (or split rule)
- "CVS" or "WALGREENS" → Health
- Payee starts with "EMPLOYER NAME" → Income/Paycheck

Part 7: Reports

Spending breakdown

Reports → Spending → Shows:

  • Spending by category (pie chart)
  • Spending by month (bar chart)
  • Year-to-date totals

Net worth

Reports → Net Worth → Tracks your assets minus liabilities over time:

Assets: Checking + Savings + Investments
Liabilities: Credit cards + Loans
Net worth = Assets - Liabilities

Budget vs actual

Reports → Budget → Compare what you budgeted vs what you actually spent per category.

Part 8: Multi-Device Sync

Actual syncs between your devices using end-to-end encrypted sync:

Desktop app

# Download Actual desktop app:
# actualbudget.org → Downloads
# Windows/Mac/Linux desktop apps available

# Connect to your server:
# File → Connect to server → https://budget.yourdomain.com

Mobile (PWA)

  1. Open https://budget.yourdomain.com on your phone
  2. Add to Home Screen (iOS: Share → Add to Home Screen)
  3. Works as a PWA — near-native experience

Maintenance

# Update:
docker compose pull
docker compose up -d

# Backup:
tar -czf actual-backup-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect actual-budget_actual_data --format '{{.Mountpoint}}')

# The backup includes your budget database file (.db)
# Keep multiple backups — financial data is critical

# Logs:
docker compose logs -f actual

Why Self-Host Actual Budget?

The case for self-hosting Actual Budget comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Actual Budget means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Actual Budget, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Actual Budget headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Actual Budget data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Actual Budget without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Actual Budget's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Actual Budget backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Actual Budget's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Actual Budget's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Actual Budget's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Actual Budget's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f actual-budget

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Actual Budget's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

  1. Confirm the container is running: docker compose ps
  2. Test locally on the server: curl -I http://localhost:PORT
  3. If local access works but external doesn't, check your firewall: ufw status
  4. If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats actual-budget. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Actual Budget Updated

Actual Budget follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Actual Budget is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See also: Firefly III — double-entry bookkeeping alternative

See all open source finance tools at OSSAlt.com/categories/finance.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)

Step-by-step: infrastructure setup, data migration, backups, and security for 15+ common SaaS replacements. Used by 300+ developers.

Join 300+ self-hosters. Unsubscribe in one click.