Who builds KIPRI

A factory floor, then code

My name is Roman Porfirievsky and I live in Minsk, Belarus. Before programming I worked at the Minsk Automobile Plant. At some point it became clear that this road was taking me somewhere I did not want to go, so I changed direction and, with it, most of my life.

I am in my sixth year in software now, writing both front end and back end. KIPRI is the first project that is entirely mine, from the database to the way a button looks.

Why build my own product

For a long time I wanted to stop delivering other people’s tasks and run a product of my own: grow it, give people something genuinely useful, and hear back about what worked and what did not. Build a system I would not be embarrassed by.

Employment does not offer that. You do one piece of somebody else’s plan well, and the decisions belong to someone else.

Why an assistant, specifically

The reason was mundane. I kept forgetting birthdays, not out of indifference, but because dates live in your head right up until the moment you need them. My notes were spread across three apps and a chat with myself, and pulling them into one place never happened. And some personal things I did not want lying around in the open, with nowhere sensible to put them.

That is where the shape of KIPRI comes from: birthdays get their own section with their own calendar, notes live in one place together with checklists and attachments, and anything not meant for other eyes sits in a private section behind a fingerprint.

I wanted a personal assistant rather than another to-do list. So Kipri has a character: he greets you by time of day, celebrates what you finish, and sends one short digest in the morning instead of a queue of notifications.

My goal is simple: KIPRI should bring calm. Everything is written down, nothing gets lost, and you no longer have to hold it all in your head.

What I am not willing to compromise on

First, everyone should be able to use the app. So almost everything in it works for free, with no ads and no "subscribe to continue" walls. Plans exist because servers and services have to be paid for: a place in the App Store alone costs 100 dollars a year. A paid plan gives more volume and cloud storage for attachments. KIPRI will never become fully paid.

Second, security. I keep things in KIPRI that I do not want to lose and do not want shown, so I treat this with as much caution as I can. Data is tied to your account and locked down by policies at the database level: nobody sees anyone else’s records, other users of the app included. The private section opens with your device biometrics. Exporting your own data works on every plan, the free one included.

Third, usability, starting with my own. I use KIPRI every day, and whatever annoys me in it gets fixed first. It is not the most scientific way to prioritise, but it works: an app that is awkward for its own author will never be comfortable for anyone else.

Where the project stands

I have been working on KIPRI since December 2025 and I have no plans to stop. This is not a two-month experiment: I use it myself, I depend on it myself, and I intend to use it for the rest of my life, so it keeps getting built.

The app already has tasks with a calendar, notes with attachments, birthdays, reminders with repeats, habits with streak counters, and voice input. What comes next depends largely on what people ask for.

There is no artificial intelligence in KIPRI yet: it understands commands through rules written in advance. I want to change that and turn it into a real personal assistant, my own "Jarvis". The plan for the next year: make the app noticeably more convenient, add what people are missing, and make Kipri feel more alive.