wealthfolio
Wealthfolio is an open-source, local-first personal finance tracker built in Rust with a Tauri desktop frontend. It supports portfolio tracking, net worth management, spending analytics, and financial simulations—all stored on your device with no cloud requirement. An optional subscription (Wealthfolio Connect) adds brokerage auto-sync and encrypted multi-device sync.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | wealthfolio/wealthfolio |
| Owner | wealthfolio |
| Primary language | Rust |
| License | AGPL-3.0 — OSI-approved |
| Stars | 7.8k |
| Forks | 550 |
| Open issues | 282 |
| Latest release | v3.6.1 (2026-07-07) |
| Last updated | 2026-07-07 |
| Source | https://github.com/wealthfolio/wealthfolio |
What wealthfolio is
Desktop/web/mobile application written in Rust (backend) and TypeScript/React (frontend), distributed as a Tauri desktop app or self-hosted web service via Axum + SQLite. Features a plugin system (TypeScript SDK), multi-currency support, and optional read-only broker integrations (30+ institutions). Licensed under AGPL-3.0.
Get the wealthfolio source
Clone the repository and explore it locally.
git clone https://github.com/wealthfolio/wealthfolio.gitcd wealthfolio# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Database path and optional broker credentials (via WF_SECRET_KEY) must be securely managed in production; follow .env.web configuration guidance and ensure 32-byte encryption key is rotated and audit-logged.
- Desktop builds require Rust, Node.js, pnpm, and Tauri toolchain; web deployments need Axum server + SQLite. Build from source or use pre-built binaries (no official package manager listings noted in data).
- Addon system uses TypeScript SDK with hot reload in dev mode; production addon distribution and permission enforcement require integration with the official addon repositories (GitHub-hosted).
- CORS configuration mandatory when auth enabled; wildcard origins rejected for security. Requires explicit allow-list for multi-origin deployments.
- No mention of automated migration strategy or backward compatibility guarantees across major versions; test upgrades in staging environments first.
When to avoid it — and what to weigh
- Require straightforward commercial licensing — AGPL-3.0 requires derivative works to be open-source and share improvements. Closed-source commercial use requires explicit dual licensing (not stated in provided data).
- Need built-in automated wealth management or robo-advisor — Wealthfolio is a tracker and simulator, not an automated investment advisor; features are limited to portfolio visualization, goal planning, and performance analysis.
- Rely on vendor-provided multi-device sync out-of-the-box — Local-first architecture means sync requires either Wealthfolio Connect subscription or manual setup; free version is single-device unless self-hosted.
- Low tolerance for AGPL obligations in supply chain — If your org policy prohibits AGPL dependencies or requires copyleft-free stacks, adoption is blocked without legal review or dual-license negotiation.
License & commercial use
Licensed under AGPL-3.0 (GNU Affero General Public License v3.0). This is a strong copyleft license: any modifications or derivative works must be open-sourced under AGPL-3.0, and network use (e.g., deploying as a web service) triggers disclosure obligations. Redistribution of binaries or libraries derived from Wealthfolio requires source code availability and the same license.
AGPL-3.0 permits commercial use of the unmodified application and free deployment. However, any internal modifications, customizations, or proprietary forks trigger copyleft obligations—source must be released under AGPL-3.0. Closed-source commercial deployments are not permitted without explicit dual licensing (not documented in provided data). Requires legal review before building proprietary products on Wealthfolio. Dual-license negotiation may be possible; contact project maintainers.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
Local-first architecture eliminates centralized breach risk for core data. Key considerations: (1) WF_SECRET_KEY must be securely generated (openssl rand -base64 32) and rotated; (2) CORS must be explicitly configured (wildcard rejected when auth enabled); (3) Optional Wealthfolio Connect requires separate account credentials for brokerage sync—security of brokerage connections delegated to third parties (Plaid or direct integrations, not detailed); (4) Addon system has permissions framework but full security model requires code review; (5) AGPL-3.0 source availability requirement aids transparency but does not guarantee security audits. No mention of security policy, responsible disclosure, or audit status.
Alternatives to consider
Sharesight (commercial SaaS)
Cloud-based portfolio tracker with automatic brokerage sync across 50+ brokers; suits users comfortable with SaaS and recurring fees; no self-hosting or open-source requirements.
Koinly (commercial SaaS)
Tax-focused portfolio and crypto tracking with cloud sync; better for tax reporting automation; closed-source and requires recurring subscription.
GnuCash / Ledger (open-source, AGPL/MIT)
Lightweight, local-first personal finance tools; no brokerage sync; steeper learning curve; permissive licenses (MIT) suitable for commercial forks if needed.
Build on wealthfolio with DEV.co software developers
Strong fit for privacy-focused portfolio tracking and self-hosted deployments. Requires AGPL-3.0 commercial licensing review before closed-source use. Discuss addon development and compliance needs with your legal and engineering teams.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
wealthfolio FAQ
Can I use Wealthfolio in a closed-source commercial product?
Do I need Wealthfolio Connect to use the app?
Can I self-host Wealthfolio on my own server?
Is there a Postgres support or only SQLite?
Software development & web development with DEV.co
DEV.co helps companies turn open-source tools like wealthfolio into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source devops stack.
Evaluate Wealthfolio for your finance tech stack
Strong fit for privacy-focused portfolio tracking and self-hosted deployments. Requires AGPL-3.0 commercial licensing review before closed-source use. Discuss addon development and compliance needs with your legal and engineering teams.