Actual Hosting
Plan personal finances with envelope budgets, account syncing, and detailed reports.
- One click deploy
- 1 GB RAM Memory needed
- 15 GB Disk Space Needed
- From 2 € Price
Official links
Actual’s official links and original website
Actual Website
More
Tech
- Docker image
- actualbudget/actual-server:latest
- Default port
- 5006
How Actual works
Actual organises money into accounts, transactions, categories, and budget envelopes. Users assign available funds to planned purposes, record or import transactions, reconcile accounts, and examine reports that show spending or balances. Rules can categorise recurring transaction patterns, while schedules and targets help plan expected activity.
The application follows a local-first model: clients keep working data locally and can synchronise through a server so several devices share the same budget. Optional end-to-end encryption protects supported budget data in transit through the sync service. Bank synchronisation is separate and depends on supported third-party providers, country availability, credentials, and configuration.
Key Actual features
Envelope budgeting gives each available amount a purpose before spending. Registers, reconciliation, rules, schedules, payees, notes, and reports support day-to-day bookkeeping. Import tools help bring transactions from supported files, and synchronisation keeps approved devices aligned around the same budget.
Optional bank sync should be evaluated carefully. Provider tokens are handled server-side and are not covered by the budget’s end-to-end encryption in the same way as encrypted budget data. Availability varies by provider and region, and automatic imports still require review for duplicates, categorisation errors, pending transactions, or changed bank behaviour.
Actual vs YNAB
Actual is a self-hosted, local-first budgeting application with envelope planning, registers, rules, reports, and optional synchronisation. YNAB is a managed subscription service with maintained web and mobile applications, bank import, targets, reports, educational material, and provider-operated account infrastructure.
YNAB may suit households that want a commercial service, guided methodology, maintained bank connections, and vendor support. Actual is attractive when users prefer to operate their own sync server and control the application environment. Neither product replaces professional accounting, tax, investment, or financial advice.
Who uses Actual
Individuals can plan monthly spending, couples can coordinate a shared household budget, and technically confident users can migrate from spreadsheets into structured accounts and envelopes. It also suits people who want local clients to remain useful when the server is temporarily unavailable.
The application is intended for personal budgeting rather than statutory bookkeeping or institutional finance. Users should reconcile against real statements and keep independent records required for tax, legal, or business purposes.
Self-hosting Actual: requirements and cost
Actual server demand depends on budgets, transaction history, connected clients, sync frequency, imports, reports, and concurrent users. The catalogue does not require PostgreSQL or MariaDB; persistent application data supports the sync service. Bank connections, where available, rely on separate providers and credentials outside the hosting plan.
AvaHost maps Actual to Plan 1 at €2. Actual includes one-click deployment, automated HTTPS for a private hostname, application updates, and scheduled backups. Optional bank sync and its provider accounts are not bundled. Application email is disabled. Treat backup recovery, encryption passwords, client access, and provider tokens as distinct responsibilities, and do not use the application as a substitute for professional financial advice.
F.A.Q
Actual starts at €2 on Plan 1. Budget count, transaction history, connected clients, synchronisation frequency, imports, reports, and concurrent users influence resource use. The fee covers the hosted sync server, not bank-data providers, financial institutions, accounting services, tax advice, investment guidance, or any subscription required for an optional external connection.
Not required. The catalogue deployment keeps persistent Actual server data without a separate PostgreSQL or MariaDB container, so the relational-database step-up does not apply. Protect the hosted data, encryption password, client copies, and backups independently. A lost encryption secret may not be recoverable merely by restoring the server files.
A custom hostname can serve Actual with automated HTTPS after DNS points to AvaHost. Enter the final server address on each approved client and verify a full synchronisation before relying on it. After changing domains, confirm device access, encryption state, imported data, and any bank-provider callback or configuration that may store the previous URL.
Optional bank sync is not bundled. It depends on supported third-party providers, regional availability, customer credentials, and current integration behaviour. Provider tokens are stored server-side and are not covered by budget end-to-end encryption in the same way as encrypted budget data. Review imported transactions, keep credentials protected, and reconcile against real statements.