About

It started as a spreadsheet.

One tab per year, formulas nobody could follow any more, and an evening every month spent sorting bank statements. It worked. It just cost that evening.

What it became

Parendi does what that spreadsheet did, without the evening. The file from your online banking goes into the window, the transactions sort themselves, the reports are there. The numbers stayed the same down to the rounding: savings rate, fixed costs and FIRE calculate the way they calculated in the spreadsheet, because otherwise the figures would suddenly have looked different.

Turning a personal tool into a product mostly means building everything you don't need yourself: the first launch with an empty database, imports from banks you've never seen, an error message instead of a crash, a second language. That is the part that takes the time, and the part that decides whether an app is any good.

What the app refuses to be

Not a budgeting coach
Envelopes, savings goals and a wagging finger when you eat out are not part of it. The app shows you what happened. What follows from it is yours to decide.
Not an account in the cloud
Nothing syncs, you sign in nowhere, and there is no password to forget. The price: a second Mac gets your data from a backup rather than by itself.
Not a subscription
Nothing here costs money monthly, so nothing needs billing monthly.
Not a bank connection
It would be convenient, and it would sit at the top of a privacy policy you then have to word carefully.

Who is behind it

One person, not a team: Missaq Ataschi, based in Solothurn, Switzerland. The spreadsheet further up was mine, and a support mail reaches the same person who wrote the code. The full details are in the legal notice.

Where the name comes from

Parendi is an old Iranian name and stands for abundance and prosperity.

In the Avesta, the scriptures of Zoroastrianism, Parendi is the companion of Ashi, "she who allots what is due". My roots are Iranian, hence the name.

Built for the Mac

Parendi is written in Swift and SwiftUI, stores its data in SQLite and uses Apple Intelligence for categorisation. None of the interface is a reimplementation: menus, keyboard shortcuts, undo, light and dark all come from the system and behave the way they do in every other Mac app.

Try it yourself

30 days, counted from your first import.