Brisk Budget - Moses Yebei

The Problem

Managing personal finances can be a headache. Most apps are bloated, require subscriptions, or just don’t meet basic needs. If you’re looking to track your expenses without dealing with a convoluted interface or a database, you’re in trouble.

What This Does

Enter Brisk-Budget. This lightweight, JSON-based finance tracker lets you manage accounts, transactions, and even recurring payments—all from your local machine. The app lives in public/index.html, with the frontend powered by vanilla JavaScript in public/js/app.js. No frameworks to learn, just straight-up JS that you can read and modify.

Data storage happens in simple JSON files, eliminating the need for a database. The server/utils/data.js handles data retrieval and storage, making it straightforward to back up or transfer your financial info. Need a new category? Just tweak the settings in the app, and you're good to go.

Real-World Use

Imagine you’ve got a couple of accounts—checking, savings, and maybe a loan. You want to track where your money goes without fuss. You fire up the app, categorize your transactions in public/js/categories.js, and set up recurring payments in public/js/recurring.js. Want to see your net worth trend? Just check the dashboard analytics, and you’ve got a clear picture.

If you want to deploy it, just run the provided shell script in deploy.sh. It sets up everything, including a systemd service for auto-start. Easy-peasy.

The Bottom Line

Brisk-Budget is a no-frills solution for personal finance tracking. It’s lightweight, easy to deploy, and requires minimal setup. If you're looking for something simple and self-hosted, this is worth a shot. Just don’t expect it to replace your enterprise-level finance software—it's not that kind of beast. But for personal use? It gets the job done.

What the analyser found

Deployment readiness

2/7

Container image
CI pipeline
Lockfile committed
Test suite
README
License
No committed secrets

Composition

0 files

JavaScript23
JSON2
Markdown1
Shell1
CSS1
HTML1

Module dependencies

The 10 most depended-upon modules of 23, from static import analysis. Red outline marks a module in an import cycle.

graph LR n0_server_config_paths["paths"] n1_server_utils_helpers["helpers"] n2_server_routes_backup["backup"] n3_server_config_defaults["defaults"] n4_server_router["router"] n5_server_routes_categories["categories"] n6_server_routes_accounts["accounts"] n7_server_routes_payees["payees"] n8_server_routes_recurring["recurring"] n9_server_routes_settings["settings"] n4_server_router --> n1_server_utils_helpers n4_server_router --> n6_server_routes_accounts n4_server_router --> n5_server_routes_categories n4_server_router --> n7_server_routes_payees n4_server_router --> n9_server_routes_settings n4_server_router --> n8_server_routes_recurring n4_server_router --> n2_server_routes_backup n6_server_routes_accounts --> n0_server_config_paths n6_server_routes_accounts --> n1_server_utils_helpers n2_server_routes_backup --> n0_server_config_paths n2_server_routes_backup --> n1_server_utils_helpers n5_server_routes_categories --> n0_server_config_paths n5_server_routes_categories --> n3_server_config_defaults n5_server_routes_categories --> n1_server_utils_helpers n7_server_routes_payees --> n0_server_config_paths n7_server_routes_payees --> n1_server_utils_helpers n8_server_routes_recurring --> n0_server_config_paths n8_server_routes_recurring --> n1_server_utils_helpers