The story
About Ledgerly
Why a ledger?
Most budgeting apps want to gamify your money — streaks, confetti, pie charts in brand colors. Ledgerly goes the other way. For a few hundred years, people kept perfectly good track of money with a bound book, two columns, and a running balance. That discipline still works; it just needed a login screen.
So Ledgerly behaves like the book: every transaction is an entry, money out sits in the debit column in red, money in sits in the credit column in green, and the balance carries forward so you always know the figure at the foot of the page. Budgets are monthly allotments you draw down. Pots are reserves, set aside and kept out of the running balance — the digital version of an envelope in a drawer.
Who builds it
Ledgerly is designed, built, and run by Atin Roy — one person, end to end: the Spring Boot API, the Next.js frontend, the PostgreSQL schema, and the server it all runs on. It is a real, working product and also a working demonstration of how I like to build software: typed contracts, migrations under version control, CI/CD on every push, and no telemetry I wouldn’t want pointed at me.
The entire codebase is public. If you’d rather audit than trust, the books are open: github.com/atin-roy/ledgerly.
What it deliberately doesn’t do
- No bank linking. Ledgerly never asks for bank credentials and never talks to your bank. You enter what you spend — that friction is the point; it’s what makes you notice.
- No ads, no analytics, no resale. Your entries exist to show you your balance, nothing else.
- No advice. Ledgerly shows you the figures. What you do about them is your business.
The stack, for the curious
Spring Boot 4 (Java) behind the /api path, Next.js 16 with CSS Modules in front, PostgreSQL with Flyway migrations underneath, all shipped by GitHub Actions to a Linux VPS behind Caddy. Details and decisions live in the repository’s documentation.
Ready to keep your own books? Open an account — it’s free.