How to Self-Host Actual Budget: YNAB Alternative 2026

TL;DR

Actual Budget (MIT, ~15K GitHub stars, TypeScript/Node.js) is a local-first, privacy-respecting personal finance app with zero-based budgeting (the same methodology as YNAB). Your data lives on your server — no subscription, no telemetry, complete ownership. YNAB costs $99/year. Self-hosted Actual is free. The sync server stores encrypted budgets so all your devices stay in sync.

Key Takeaways

• Actual Budget: MIT, ~15K stars, TypeScript — zero-based budgeting, local-first
• Local-first: Budget data is stored locally (SQLite) and synced via the server — not in a cloud database
• YNAB methodology: Zero-based budgeting — every dollar gets a job
• Bank sync: Optional GoCardless/SimpleFIN integration for automatic transaction import
• Mobile: Web app (PWA) — works as a home screen app on iOS/Android
• Privacy: End-to-end encrypted sync — your server never sees budget contents

---

Actual Budget vs YNAB vs Firefly III

Feature	Actual Budget	YNAB	Firefly III
License	MIT	Proprietary	AGPL 3.0
Cost	Free (hosting)	$99/year	Free (hosting)
Zero-based budgeting	Yes	Yes	No (envelope)
Bank sync	GoCardless/SimpleFIN	Yes (built-in)	Yes (Nordigen)
Local-first	Yes	No	No
Mobile app	PWA	iOS/Android	PWA
GitHub Stars	~15K	—	~14K
Data ownership	Full	YNAB's servers	Full

---

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_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB: "20"
      ACTUAL_UPLOAD_SYNC_ENCRYPTED_FILE_SYNC_SIZE_LIMIT_MB: "50"

volumes:
  actual_data:

docker compose up -d

Visit http://your-server:5006.

---

Part 2: HTTPS with Caddy

HTTPS is required for Actual's service worker (PWA functionality and offline sync):

budget.yourdomain.com {
    reverse_proxy localhost:5006
}

---

Part 3: Initial Setup

1. Visit https://budget.yourdomain.com
2. Create server password (protects access to the sync server)
3. Create budget — Start fresh or import from YNAB
4. Add your accounts:
   • Checking account
   • Savings account
   • Credit cards

---

Part 4: Budget Setup (Zero-Based Method)

The zero-based budgeting principle: Income − Budgeted = $0

Every dollar you receive gets assigned to a category:

Budget Categories

INCOME THIS MONTH:  $5,000

BILLS:
  Rent/Mortgage:     $1,500
  Utilities:           $150
  Internet:             $60
  Phone:                $60
  
NECESSITIES:
  Groceries:           $600
  Gas:                 $150
  
SAVINGS:
  Emergency Fund:      $500
  Vacation Fund:       $200
  
DISCRETIONARY:
  Dining Out:          $200
  Entertainment:       $100
  Shopping:            $150
  
DEBT:
  Car Payment:         $350
  
TOTAL BUDGETED:     $4,020
REMAINING:            $980  ← assign to savings or next month

Adding Transactions

1. Click on account → + Add Transaction
2. Date, payee, category, amount
3. Or import a CSV from your bank

---

Part 5: Bank Sync (Automatic Import)

SimpleFIN (US Banks)

SimpleFIN connects to US bank accounts ($1.50/month):

1. Sign up at simplefin.org
2. Connect your bank accounts
3. In Actual → Settings → Advanced → Enable Bank Sync
4. Enter your SimpleFIN Access URL

GoCardless (European Banks)

For European banks:

1. Sign up at GoCardless (free tier available)
2. Get API ID and Secret Key
3. In Actual → Settings → Bank Sync → GoCardless

Manual Import (Any Bank)

Download transactions as CSV from your bank:

• Actual → Account → Import → Select CSV file
• Map columns: date, payee, amount

---

Part 6: Reports

Actual includes built-in reports:

• Net Worth: Track total assets vs liabilities over time
• Cash Flow: Monthly income vs expenses chart
• Spending Breakdown: Category breakdown for any period
• Custom Reports: Filter by account, category, date range

---

Part 7: Multi-Device Sync

All devices connect to your self-hosted sync server:

1. On a second device, visit https://budget.yourdomain.com
2. Enter server password
3. Open existing budget → data syncs automatically

All sync data is end-to-end encrypted using a client-side encryption key. The server stores only ciphertext.

---

Part 8: YNAB Migration

Import your YNAB budget into Actual:

1. In YNAB: Export Budget (Settings → Export Budget Data)
2. In Actual: File → Import → YNAB4 or YNAB5
3. Select your exported .json file
4. Budget categories, accounts, and transactions are imported

---

Advanced: Self-Hosted SimpleFIN Bridge

Run your own SimpleFIN-compatible bridge for free (requires your bank credentials):

services:
  actual-sync:
    image: ghcr.io/actualbudget/actual-server:latest
    ports:
      - "5006:5006"
    volumes:
      - actual_data:/data

See Actual Bridge for the self-hosted SimpleFIN alternative.

---

Maintenance

# Update Actual Budget:
docker compose pull
docker compose up -d

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

# The backup contains encrypted budget files per user

# 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 all open source personal finance tools at OSSAlt.com/alternatives/ynab.