Wealthfolio

The open-source, private portfolio tracker — investments, net worth, spending, and simulations.
Local-first: your data lives on your device.

Website · Discord · Twitter · Releases

⬇️  Download for macOS · Windows · Linux  ·  📱 iOS App  ·  🐳 Docker

[](https://www.buymeacoffee.com/afadil)

Introduction

Wealthfolio is an open-source, private portfolio tracker — investments, net worth, spending, and simulations. All your data is stored locally on your device: no cloud database, no account required, free forever.

For automatic brokerage syncing (30+ institutions, read-only) and encrypted multi-device sync, there's Wealthfolio Connect — an optional subscription that covers the real cost of the brokerage data connections. The app never requires it: manual tracking and CSV import are free, forever.

Visit the website at wealthfolio.app.

✨ Key Features

• 📊 Portfolio Tracking - Track your investments across multiple accounts and asset types
• 📈 Performance Analytics - True time-weighted and money-weighted returns, benchmark comparison, and historical analysis
• 💰 Activity Management - Import and manage all your trading activities
• 🎯 Goal Planning - Set and track financial goals with allocation management
• 🔒 Local Data - All data stored locally with no cloud dependencies
• 🔄 Optional Broker Sync - Auto-sync 30+ brokerages with Wealthfolio Connect (read-only, entirely optional)
• 🧩 Extensible - Powerful addon system for custom functionality
• 🌍 Multi-Currency - Support for multiple currencies with exchange rate management
• 📱 Cross-Platform - Desktop (Windows, macOS, Linux), iOS, and self-hosted Docker/web

Wealthfolio 3.7 requires macOS 12 or newer and iOS/iPadOS 16 or newer. macOS 12 installations should apply current macOS and Safari updates so the system WKWebView meets the Safari 16 browser floor. Windows uses the evergreen WebView2 runtime; Linux and self-hosted installations should keep WebKitGTK or their browser updated.

🧩 Addon System

Wealthfolio features a powerful addon system that allows developers to extend functionality:

• 🔌 Easy Development - TypeScript SDK with full type safety and hot reload
• 🔒 Secure - Comprehensive permission system with user consent
• ⚡ High Performance - Optimized for speed with minimal overhead
• 🎨 UI Integration - Add custom pages, navigation items, and components
• 📡 Real-time Events - Listen to portfolio updates, market sync, and user actions
• 🗄️ Full Data Access - Access to accounts, holdings, activities, and market data
• 🔐 Secrets Management - Secure storage for API keys and sensitive data
• 📦 Private Assets - Package images, fonts, media, configuration, and Wasm for the isolated addon sandbox

Get started building addons: See the Addon Documentation Hub

Documentation for all Activity types, including the required form fields, is available in docs/activities/activity-types.md.

Roadmap

See ROADMAP.md.

📖 Documentation

Core Application

• Activity Types - Complete guide to all supported activity types and their required fields
• Roadmap - Future plans and development roadmap

Architecture

• Credential Storage - Native backends, server encryption, Android backup, and recovery
• Android Testing - Setup, emulator/device commands, APK builds, and smoke tests
• Adapter System - Compile-time environment detection for Desktop/Web builds

Addon Development

• Addon Documentation Hub - Main entry point for addon development
• Getting Started - Guide to get started with addon development
• API Reference - Complete API documentation with examples
• Architecture - Design patterns and architecture guide
• v3.6 to v3.7 Migration - Packaged assets and compatibility notes

Quick Links

• 💡 Official Addons - Browse maintained addon examples in the official addon repository
• 🧩 Community Addons - Browse addons shared by the community in the community addon directory
• 🛠️ Development Tools - CLI tools for addon development

Getting Started

Prerequisites

Ensure you have the following installed on your machine:

• Node.js, using the version in .node-version
• pnpm, using the packageManager version in package.json
• Rust, using rust-toolchain.toml
• Tauri

Building from Source

1. Clone the repository:

bash git clone https://github.com/wealthfolio/wealthfolio.git cd wealthfolio

2. Install dependencies using pnpm:

bash pnpm install --frozen-lockfile pnpm build:types

See Frontend tooling for editor setup, checks, and instructions for updating an existing checkout.

3. Setup environment configuration:

Copy the environment template and configure it for your setup:

bash cp .env.example .env

For optional Connect setup, see Wealthfolio Connect in source builds.

Desktop development uses a separate application identity and profile directory. On macOS, the default layout is:

text ~/Library/Application Support/com.teymz.wealthfolio.dev/ ├── profiles.json └── profiles/<uuid>/app.db

To select another profile directory during desktop development, set WF_DATA_DIR in .env to an absolute path as described in .env.example. Leave it unset to use the default development app-data directory. Use a dedicated development directory; this setting selects the registry and its profiles, not an individual database file. An existing root-level app.db is only adopted on first profile initialization.

If your older .env contains DATABASE_URL, remove it: pnpm tauri dev ignores it, including on first launch. Use WF_DATA_DIR for development directory selection. Packaged desktop apps do not ship with an .env file.

4. Run in Development Mode:

pnpm tauri dev

The command automatically applies apps/tauri/tauri.dev.conf.json, which sets com.teymz.wealthfolio.dev and Wealthfolio (Development). This identity remains in effect when additional --config overrides are supplied, including when running pnpm tauri dev --release. Production builds (pnpm tauri build) retain the production identity. For an isolated packaged debug build, select the same configuration explicitly:

pnpm tauri build --debug --config apps/tauri/tauri.dev.conf.json

Credentials follow the selected application identity, not debug/release mode. Production Keychain names are unchanged. Development has separate credentials, so sign in and en