Shared expenses
An expense splitter for the group trip, the flatshare and the book club. Everything Splitwise puts behind Pro, without the Pro — and without the ads.
What it is
A week in Lisbon turns into forty small payments and one group chat where nobody remembers who covered the Airbnb. Splitwise handles the arithmetic, then puts recurring expenses, itemisation, currency conversion and charts behind Pro, and shows everyone else ads.
Wise Split takes the same ledger — who paid, who owes, in which currency — and runs the whole group's debt graph through a minimisation pass before it tells anyone to pay anyone. Splitwise nudges pairwise. This collapses the cycles first, then names the transfers.
Settle up
The dashboard nets what you are owed against what you owe, per currency, and lists every person you have an open balance with. Settle-up runs the group's debt graph through a minimisation pass instead of nudging each pair separately.
Charts
Your share of the last fourteen days, plus a category breakdown of the same period. Both charts are hand-rolled SVG. There is no charting library in the dependency list and no raster image anywhere in the app.
Dark mode
Light, dark, or follow the system. The theme is set on the document before first paint, so there is no white flash on load. A manifest and a service worker make it installable, and the shell loads from cache with no network.
How it works
Four steps, in the order a first-time visitor actually meets them.
01
There is no sign-up wall. The published build seeds a ledger in your browser so you can poke at real balances straight away.
02
Press N, or type "dinner with sam $48 yesterday" into quick add and let the parser fill in the amount, the date and the people.
03
Equal, percent, share-based, or exact amounts. Money is stored as integer cents plus an ISO currency code, then formatted with Intl.
04
The balances view collapses the group's debt graph and names the payments to make. Reminders open a mailto draft or the system share sheet.
Features
Equal, percent, share-based, or exact amounts, chosen per expense rather than per group.
Substring, fuzzy through Fuse.js, and raw regular expressions across every expense, group and friend.
Type one sentence and the parser pulls out the amount, the date and the people involved.
Minimises the number of transfers a group needs instead of settling every pair separately.
Amounts held as integer cents plus an ISO 4217 code, rendered with Intl.NumberFormat.
Command palette, slash to search, N for a new expense, and G-then-letter to jump around.
A custom manifest and service worker; the app shell loads from cache when you are offline.
Every icon, chart, illustration and avatar is vector. There is no raster image in the repository.
Zero analytics, zero third-party scripts, zero ads. There is nothing to opt out of.
Built with
A static export, deployed to GitHub Pages by Actions and mirrored on Vercel. The published build keeps your ledger in the browser's local storage, so nothing leaves the device. Supabase Google sign-in and Postgres with row-level security are in the source but not switched on for this deploy. MIT licensed, so you can fork it and point it at your own Supabase project.
FAQ
Yes, and there is no paid tier to upgrade to. The licence is MIT, so you can fork it, host it and rebrand it. Self-hosting costs whatever your own Supabase project costs, which on the free tier is nothing.
Not on this build. It runs in demo mode with a seeded ledger, so there is no sign-up step. Google sign-in through Supabase exists in the source but is not enabled on the published copy yet.
Nowhere. No analytics, no third-party scripts, no ads. On the published build everything stays in your browser's local storage. Self-host it against your own Supabase project and it goes to your Postgres, behind row-level security.
Yes. It ships a web app manifest and a service worker, so you can install it to the home screen and the shell still loads without a connection. There is no App Store or Play Store build.
No. The app is SVG-only by design, which means it has no image upload path at all. That was a deliberate trade, not an oversight. Attach a note to the expense instead.