Summary
The splitting-the-bill arithmetic, done where the conversation about the bill is happening.
It keeps one ledger per event and answers the only question that matters at the end — who pays whom, and how much — while still letting you record partial payments as they trickle in over the following weeks.
What it is
A shared-expense ledger for social events: you create a gathering, name its members, log expenses and payments against it, and ask what everyone owes.
What you get
- A named gathering with a member list, created in one call
- Expenses recorded against a member and an amount
- Reimbursements calculated for the whole gathering, rather than worked out by hand
- Payments recorded as they happen, so balances move as people settle
- Member management after the fact — add, remove, or rename someone who went in as unnamed
- The full state of one gathering, or a list of all of them
- Closing and deleting a gathering when the trip is done
Requirements
Node for the server itself and Python on the same machine — the TypeScript server passes each request to a Python backend as a command-line call, so both runtimes have to be present.