—About
Why JOURNY works the way it does.
Most finance apps do not explain themselves. JOURNY is built around one belief: a number you cannot trace is not worth showing you, no matter how it was produced.
The AI is not allowed to do the maths
It sounds like a strange rule for a product built by someone who works in generative AI every day. It is the rule anyway, and the two facts are related, not opposed. Spend enough time making AI models produce convincing things and you learn exactly how confidently they can be wrong. That is not a reason to keep AI away from your money. It is a reason to put a wall between what it is allowed to touch.
So in JOURNY, every figure you see was worked out by ordinary code doing ordinary arithmetic on what you recorded. The AI narrates. It never calculates. It is handed an answer that already exists and given one job: say it in a plain sentence. If it ever produced a number of its own, that would be treated as a bug, not a quirk.
An estimate never gets to look like a fact
The same instinct shows up in how JOURNY is designed, not just how it computes. A projection about your future spending is drawn differently from a total of what already happened: dashed, a different colour, labelled plainly as a guess. A historical number is solid, because it is not a guess. A chart can mislead faster than a sentence can, so the fix has to be visual, not a footnote underneath it.
That is the whole philosophy in one habit: show the working, mark what is uncertain, and never let the interface sound more confident than the maths underneath it actually is.
Who
JOURNY is designed and built by Jagesh Pandey, an independent creator based in India, working at the intersection of Generative AI, technology, and creative direction.
Reachable at hi@jageshpandey.com, and elsewhere below.
Why I built this
I started thinking about JOURNY because I often found it difficult to understand where my money was actually going. Existing tools either felt like spreadsheets, or, in the case of Notion, weren’t really designed for quickly handling a long history of transactions or helping me see the patterns behind my money: where it was coming from, where it was going, and how things were changing over time.
As a freelancer, my income can have good months and difficult months, and sometimes it isn’t easy to look back and understand what really happened financially. I wanted something that could help me make sense of that story, rather than simply record a list of transactions.
I also started seeing something personal in keeping track of money. To me, a transaction can be a little like a photograph or a memory. Looking back at it can remind you of where you were, what you were doing, who you were with, and sometimes even what that period of life felt like. The numbers are only one part of the story.
With the technology available today, I feel lucky that we can take ideas we’ve carried in our heads and actually try to build them. I’ve spent much of my life tinkering with technology, design, and creative tools, and JOURNY is my attempt to bring those interests together into something genuinely useful.
I’m still learning, and JOURNY is very much a work in progress. But I’ve tried to build it with the knowledge, curiosity, and creative perspective I’ve gathered over the years, and to make it as thoughtful as I can.
— Jagesh
Two more decisions you can check
It never connects to your bank.
No net-banking credentials, no account aggregator, no read access to any institution. It is more work for you at the start, and it is the reason there is nothing stored here worth stealing.
Nothing on the server does maths on your money.
Your totals are worked out on your own device. The database stores rows and hands them back, and never computes over your balances. The security page explains what that buys you, including where the limits are.
Where it is up to
JOURNY is early, and honestly so: free, no paid tier, no investor and no advertising business behind it. That last part is why the privacy policy can say your data is never sold without that being a promise someone else could later overrule. If something is broken or missing, saying so genuinely changes what gets built next.
Say something
A bug, an idea, or a question about how a number was worked out. The contact page reaches the same inbox as hi@jageshpandey.com, and a person reads every message.