Actual Budget is a mature, open-source personal finance application that operates on a local-first architecture with optional multi-device sync. In production, it provides envelope and tracking budgeting, transaction management, bank account synchronization via GoCardless/SimpleFIN/Pluggy, scheduled transactions, an advanced rules engine for auto-categorization, custom reports and dashboards (including Monte Carlo forecasting), and multi-user sync server capabilities. The system is built as a monorepo with distinct packages: `loot-core` (business logic, SQLite database, CRDT sync, custom AQL query language), `desktop-client` (React SPA with Redux and TanStack Query), `desktop-electron` (Electron wrapper), `mobile-client` (Capacitor-based), `sync-server` (Express with authentication and bank integrations), `cli` (headless management), `api` (public npm package), `component-library` (design system), and `crdt` (conflict-free replicated data type). Data flows from user input or bank imports into a local SQLite store, with optional sync to other devices via a CRDT protocol over a WebSocket/HTTP server. The project demonstrates high engineering craftsmanship with extensive tests, custom but well-documented systems, and a strong modular architecture. It is not a data research project.
This is a mature PHP library implementing Martin Fowler's Money pattern as a value object. It provides a `Money` class that stores amounts as numeric strings in the smallest currency unit (e.g., cents), ensuring precision and avoiding floating-point errors. The library includes a rich set of features: arithmetic operations (add, subtract, multiply, divide, mod), comparison, allocation (by ratios or to N targets), aggregation (min, max, avg, sum), formatting (decimal, Intl, Bitcoin), parsing (decimal, Intl, Bitcoin), currency conversion via exchange rate providers (FixedExchange, Swap, Exchanger, IndirectExchange), and a `Teller` facade for migrating legacy float-based code. It supports multiple currency repositories (ISO 4217, Bitcoin, crypto-currencies from Binance) and offers pluggable calculators (BCMath required, GMP optional). The architecture is interface-driven with clean separation of concerns, extensive test coverage, and static analysis integration. It is not a data research project; it is a pure application library for monetary value handling.
Brick\Money is a high-quality, immutable PHP library for representing monetary values, performing arithmetic, currency conversion, allocation, and locale-aware formatting. It provides exact arithmetic via brick/math, supports multiple contexts (default, cash rounding, custom scale, auto-scale), and includes a rich set of exchange rate providers (configurable, PDO-backed, cached, chained, base-currency derived). The library features a strategy pattern for allocation (five algorithms including Hamilton's method) and cross-currency comparison. It is thoroughly tested, type-safe, and follows modern PHP practices (PHP 8.2+, readonly classes, enums, sealed interfaces). The codebase demonstrates strong software craftsmanship with clean abstractions, immutable value objects, and well-isolated components. It is actively maintained with regular releases and comprehensive documentation.
money-rails is a Ruby gem that integrates the RubyMoney library with Rails, providing a `monetize` macro for ActiveRecord and Mongoid models. It allows developers to map integer cents columns (e.g., `price_cents`) to Money objects, handling currency conversions, validation, formatting, and serialization. The gem includes migration helpers, a custom ActiveModel validator, ActionView helpers, an ActiveJob serializer, test helpers, and configuration for global currency defaults and rounding modes. It supports multiple Rails versions (7.0–8.1), Mongoid 7–9, and Ruby >= 3.1. The codebase is well-structured, extensively tested, and follows Rails plugin conventions with clean separation of concerns.
OpenBudgeteer is a personal budgeting application built with .NET 9.0 featuring a Blazor WebAssembly frontend and ASP.NET Core Web API backend. It implements the bucket budgeting methodology, allowing users to manage financial accounts, transactions, budget categories (buckets), automated transaction rules, recurring transactions, and financial reporting. The application supports multiple database providers (MySQL, PostgreSQL) and uses Redis for session storage and application settings. The architecture follows a layered approach with distinct data, service, presentation, and API layers. The data layer uses Entity Framework Core with a repository pattern for data access. The service layer provides business logic through generic and EF Core-specific services. The presentation layer employs the MVVM pattern with Blazor components and ViewModels handling UI state and logic. The API layer exposes RESTful endpoints for the frontend to interact with the backend. Key reusable components include a generic repository pattern, a generic service pattern, a ViewModel base class for Blazor, a fluent CSV bank transaction mapper, and a MudBlazor theme persistence service. These components demonstrate craftsmanship in abstraction and separation of concerns, making them suitable for extraction and reuse in other projects. The application is actively maintained with recent updates to .NET 9.0, MudBlazor, and ApexCharts, indicating low technical drift.
Akaunting is a self-hosted accounting and invoicing platform for small businesses and freelancers. It manages invoices, bills, banking transactions, transfers, reconciliations, multi-currency, multi-tax, recurring documents, and financial reports. It includes a customer portal for invoice viewing and payment, and supports multi-company, multi-user with role-based permissions. The system is highly internationalized with 40+ language locales. The architecture is built on a custom PHP framework (Illuminate) that extends Laravel conventions. It uses an event-driven architecture with domain events, listeners, and a job queue for async processing. The frontend combines Blade templates, Vue.js components, and Livewire for interactivity. Multi-tenancy is achieved through company scoping via a global query scope. The system is extensible via a module system with an app store, and includes a CLI for maintenance tasks. Key entry points include the installation wizard (controllers under Install/), authentication flows, and core CRUD controllers for sales, purchases, banking, and settings. Data flows typically involve controllers dispatching jobs that emit events, which listeners handle to update related entities, send notifications, or trigger side effects. Reports use a filter/group/rows event system for extensibility. Import/export is handled via Excel with multi-sheet support. External dependencies include PHP 8.1+, Node 18-20, and a database (MariaDB, MySQL, PostgreSQL, SQLite). It uses Laravel Mix for asset compilation, integrates with payment gateways, email services, and error trackers (Sentry, Bugsnag), and relies on a module marketplace at api.akaunting.com.
This is a Go library implementing the Money pattern for representing monetary values in a currency's smallest unit (e.g., cents). It provides precise arithmetic operations (addition, subtraction, multiplication, rounding), allocation and splitting of amounts without floating-point rounding errors, and formatting to human-readable strings with currency symbols and separators. The library includes a comprehensive set of ISO 4217 currency definitions, supports JSON serialization/deserialization with customizable marshal/unmarshal functions, and integrates with database/sql via Scanner and Valuer interfaces for storing monetary values in relational databases. It has no external dependencies beyond the Go standard library, making it lightweight and easy to embed. The architecture is a simple library with clear separation of concerns: a calculator for arithmetic, a formatter for display, a currency registry, and the core Money struct that composes these components.
Liberapay is a production web application for recurrent monetary donations, operating as a non-profit platform. It allows donors to set up weekly, monthly, or yearly contributions to creators, teams, and organizations. The architecture is a monolithic Python web application built on the custom Aspen/Pando framework (a fork of Aspen), using PostgreSQL for persistence, Jinja2 for server-side rendering, and a mix of Stripe and PayPal for payment processing. Key entry points include the homepage (`www/index.html.spt`), user profile pages (`www/%username/index.html.spt`), donation management (`www/%username/giving/`), payment flows (`www/%username/giving/pay/stripe/%payin_id.spt`), and admin dashboards (`www/admin/`). Data flows involve user authentication via sessions and OAuth, tip creation and scheduling, payin execution through Stripe/PayPal, weekly payday settlement, and email notifications. External dependencies include Stripe, PayPal, Amazon SES (email), Sentry (error tracking), S3 (file storage), and multiple OAuth providers (GitHub, Twitter, Mastodon, etc.). The codebase is well-structured with reusable modules for payment prospect calculation, encryption, content security policy, currency handling, and OAuth abstraction, though it carries technical debt from a custom framework and aging dependencies.
Firefly III is a self-hosted personal finance management application built on the Laravel PHP framework. It provides comprehensive double-entry bookkeeping with support for multiple currencies, accounts, budgets, categories, bills, piggy banks, recurring transactions, and rules. The system exposes both a full web UI using Blade templates and Alpine.js (with legacy jQuery components) and a RESTful JSON API (v1) for programmatic access. Key features include transaction splitting, budget limits, auto-budgeting, rule-based transaction processing, exchange rate management, webhook integration, multi-user with group administration, and detailed reporting with charts. The codebase follows a repository pattern with interfaces, uses events and listeners for side effects, and includes a substantial set of artisan commands for maintenance, upgrades, and data corrections.
MoneyPrinterV2 is a Python 3.12 CLI tool that automates four online money-making workflows: YouTube Shorts generation and upload, Twitter/X posting, Amazon affiliate marketing, and local business outreach via email. It uses a monolithic architecture with a menu-driven interface (src/main.py) and a headless cron runner (src/cron.py). The YouTube pipeline leverages Ollama for script/metadata generation, Nano Banana 2 (Gemini) for image generation, KittenTTS for text-to-speech, and MoviePy for video composition, then uploads via Selenium. The Twitter bot posts generated tweets via Selenium. Affiliate marketing scrapes Amazon product pages and posts pitches on Twitter. Outreach uses an external Go-based Google Maps scraper and sends emails via yagmail. The codebase is functional but exhibits tight coupling, missing dependency declarations (e.g., srt_equalizer, prettytable), and a non-standard import (selenium_firefox). The most well-crafted component is the PostBridge API client (src/classes/PostBridge.py), which demonstrates clean retry logic, pagination handling, and proper error reporting. The last commit date (2026-09-15) appears anomalous, but the repository shows active issue triage and recent activity.