The origin story
How ReddUp was forged
The origin video is coming soon. No YouTube connection is made today.
01Make The Boss Happy
The birthplace of greatness
I had recently taken on managing the budget for the marketing department at my work. When the boss asked me to make a spreadsheet, I thought to myself, "Why in the world would I make the spreadsheet by hand when I can make a program do it for me?"
And so the zygote of ReddUp was conceived. Its function was simple: take exported CSV files from Quickbooks, allow me to edit them, and then export a dialed in Excel spreadsheet.
At the time, the program was a simple Python file. But I was proud of it. I named it Make The Boss Happy and deployed it as a usable application on my work computer.
02Chasing possibilities
What if I scaled this?
New ideas emerged as I added new features. I developed three separate pages: Import, Editor, and Visuals, breaking down the core function of what was still named Make The Boss Happy. I wanted to see how I could create a program that would help me with my own job as someone who was in charge of keeping records and showing the boss the financial scope.
The start of what is now called ReddUp Command came into fruition, called Deploy at the time. It was only able to export a .dply file that would be importable by a separate program. I loved the idea of securely sending a higher up in a company financial information they need to look over. It keeps them in the loop. When it is time for a deeper financial analysis, then they can utilize the program's exporting capabilities.
It was the first time introducing a Tailwind interface in some areas of the program, but for the most part everything was still in Python. But as I was developing the program, I knew the inevitable had to happen if I wanted to make this program right.
03Facing the truth
Rebuilt from the ground up
Then one day I did the hard thing: I tore it down and rebuilt it as a standalone desktop application. ReddUp now uses a Tauri 2 shell written in Rust, with an interface built in plain JavaScript and Tailwind CSS. Its core financial engine is written in Python and runs locally as a separate process, bundled with the app so there’s no need to install Python separately. Behind the scenes, the Rust shell and Python engine communicate through structured JSON messages over standard input and output.
Months of changes, tests, late nights and early mornings later, ReddUp became the application you see now. I am so proud of what it can do and I am excited to share with the world the inspiration and wonder ReddUp has made me feel.
04The name
Finding the name, “redd”
I spent months on the name. Every cool one was already taken, so I went digging — through Greek, Latin and Hebrew, through history, looking for something that fit.
Then I found a small, almost-forgotten word: redd. I’ve always loved a deep, dramatic red — and as it turns out, “redd up” is a Scots and Northern-English phrase meaning to tidy up, clear out, and set in order. Which is exactly what this program does to your finances.
05Pass the baton
The journey does not end here...
Even though it took months of staying up until two in the morning or cramming a moment here or there to fix bugs or add features, the journey does not end here.
ReddUp was designed to go with you, develop with you, and grow with you. It's your financial companion, a dependable guide. The journey continues with you.