Open Splitwise

Link: https://splitwise.ankitchouhan.dev/

Splitwise is excellent at the social part of money: who paid, who owes, settle up. It is less excellent when you want to ask your own data questions — “how much coffee with this group last year?”, “export everything”, “show me balances across friends without clicking forever.”

Open Splitwise is the layer I wanted on top: sync expenses into Postgres you control, then explore them in a web UI you host. Entry and settlement stay in Splitwise. This app is read-focused ownership, not a clone.

Why it exists

I kept bouncing between mobile Splitwise and spreadsheets. Search was shallow. Exports felt temporary. Insights were something I rebuilt by hand.

The bet was simple: if the data lives in my database, the UI can be honest. Full-text over descriptions and comments. Filters and saved views. CSV when I need a spreadsheet. Balance views across people and groups. One deployment can serve multiple Splitwise accounts with per-user isolation.

How it feels to use

• Connect with OAuth — the token stays on the server
• Sync into Postgres; browse Home, Explore, and Insights
• Showcase mode runs on sample data with zero config (Railway / Docker) so you can kick the tires before wiring credentials
• A mask toggle swaps between live sync and fixtures — useful for demos without disconnecting

Stack-wise it’s a Next.js app with a real sync path, not a thin API wrapper. Optional AI bits help with narratives and category suggestions when you want them; the core product works without that.

What it is not

It is not a Splitwise replacement. Friends still add expenses where they already do. Open Splitwise is for the moments after: query, remember, export, understand.

Source: splitwise.ankitchouhan.dev · GitHub.