What it is

Actual is a local-first personal finance application built for envelope budgeting, part of the open-source personal finance ecosystem. It runs entirely on the user’s device by default, ensuring data remains under full local control, while optionally syncing changes across devices via a self-managed or hosted backend.

It solves the problem of proprietary budgeting tools that lock user data behind cloud services or paid subscriptions. Actual eliminates vendor lock-in by storing all financial data in a local SQLite database, enabling users to own, inspect, and migrate their data without reliance on third-party infrastructure.

Key capabilities

• Envelope budgeting with rolling monthly allocations and category-based spending limits
• Local-first data storage using SQLite, with optional sync via a self-hosted or Fly.io/PikaPods backend
• Multi-device synchronization using a conflict-aware, bidirectional sync protocol
• Import/export of financial data via CSV, YNAB4, and Actual’s own JSON schema
• Customizable account types (checking, savings, credit, cash) with reconciliation support
• Transaction filtering, categorization, and recurring transaction rules
• Extensible architecture via Node.js core (loot-core) and modular UI packages

Who uses it and how

• Self-hoster users deploy the Docker image or native desktop apps to maintain full control over sensitive financial data
• Migrators from YNAB or other envelope budgeting tools use the provided CSV and YNAB4 import workflows to transition budgets
• Non-technical users adopt managed hosting via PikaPods or Fly.io to avoid local setup while retaining data ownership
• Contributors extend functionality by modifying the loot-core, desktop-client, or desktop-electron packages

Getting started

Install via downloadable desktop apps for Windows, macOS, and Linux, or deploy using Docker (actualbudget/actual-server), Fly.io, or PikaPods. The app launches locally with no account required; sync is enabled by configuring a remote server URL.

When to use it — and when not to

Use Actual when data ownership, offline access, and envelope-style budgeting are priorities, and when you can manage local storage or self-host sync. Avoid it if you require automated bank feeds, investment tracking, or multi-user collaboration—its sync is device-to-device only, and it lacks native integrations with banking APIs. Self-hosting requires managing a Node.js server, SQLite database, and optional SMTP for notifications.