Currently working on
Budgeting and debt planning
At a glance: Next.js and a .NET API over PostgreSQL, with household-scoped sign-in, manual records, CSV import, and optional bank sync.
A personal project I am spending my time on: an app that helps people budget and manage debt from the accounts, paychecks, bills, and balances a household actually has. In progress.
In progress
What it is
A personal project I am spending my time on. It helps people budget and manage debt from the same records they use day to day: what is owed, what is coming in, which bills repeat, and what a payment does to the month.
What is in the product now
- Signed-in household records: home, accounts, transactions, institutions, categories, budgets, income, bills, and debts.
- Manual accounts and transactions, plus CSV import, so the app is usable before a bank is connected.
- Income covers sources, paycheck schedules, and scenarios. Bills include recurring suggestions. Debts have a summary for recorded balances, this month's interest, minimums, and utilization of known credit limits.
- A connected card or loan can be compared with the debt's recorded balance. The next slice is letting a manual debt follow that synced balance instead of asking for a retype after every payment.
Tech stack
Architecture
The Next.js app talks to an ASP.NET Core API. Financial reads and writes use the household resolved on the server for the signed-in owner. PostgreSQL holds the records through Entity Framework Core. Plaid credentials are optional: without them, manual records and CSV import still work, and bank linking stays off. A separate worker runs one synchronization pass and exits. Plaid access tokens are encrypted before they are stored.
Why it is on this site
This is the personal project I am spending my time on. It is a workflow-heavy application with a typed API, a real database, sign-in, and a careful boundary around bank data.