FOUNDER
Mateusz Rowieński
I am responsible for everything you see here: architecture, code, databases, servers and security. I run every project from scratch, from the database layout to what should happen when something goes wrong.
I am a one-person workshop in the middle of becoming a company. I build things that keep working on their own: a booking system for clinics, a gaming portal, a game in production and Windows programs. All of it runs on servers I set up and maintain myself. Registering the business was deliberately left for last - working products and a portfolio first, paperwork after.
github.com/qpidynoWhat I am responsible for
All of it. System architecture, code, databases, servers and security, but also how a product looks and how it is used: visual identity, screen layout, artwork and concept art. The decision on how a project is laid out, where it runs and what protects it is mine - and so is the decision on what the user sees first.
How I think about projects
Strategically and logically, before the first line exists. First I know what has to be built, who it serves and what sets it apart - then I design the screens, and only then do I write code. That way a finished application does not turn out to be unusable, and a system does not need rewriting at the first major change.
Claude Code is a tool
A tool, not a co-author. It speeds up writing code and takes repetitive work off my hands, which is how one person keeps this many projects running. But the structure, the design decisions, the security and the responsibility for what reaches production stay on my side. I know what has to be built and why exactly this way - AI only shortens the path to a working version.
AI beyond the cloud
MNICH translates game and mod files locally, on the Polish Bielik model running on the user's own graphics card - no text ever leaves their machine. NBB removes image backgrounds the same way: the model runs on the user's side, with no account and without sending photos to someone else's server. I can set a model up locally and wire it into a program so that it does a specific job rather than being decoration.
The workshop
A machine built for long compilations, graphics work and sound. Not a list off the shelf - every part picked for what I do on it. The memory does not run on a box profile - the timings are tuned by hand and squeezed for this exact build.
THE MACHINE
- KARTA GRAFICZNAMSIGeForce RTX 4080 SUPER VENTUS 3X OC16 GB GDDR6X256-bitAda Lovelace
- PROCESORAMDRyzen 9 9950X3D16C / 32TZen 53D V-CacheAM5
- PAMIĘĆCorsairVENGEANCE RGB 96 GB2x48 GBDDR5-6000CL30custom OC
- PŁYTA GŁÓWNAMSIMAG X870 TOMAHAWK WIFIX870Wi-FiPCIe 5.0
- CHŁODZENIEArcticLiquid Freezer III ARGB 420AIO 420 mm3x140 mm
- DYSK NVME ILexarNM790 1 TBM.2PCIe Gen4
- DYSK NVME IILexarNM790 2 TBM.2PCIe Gen4
- KARTA DŹWIĘKOWASound BlasterAE-7
- OBUDOWADeepCoolMORPHEUS
- WENTYLATORYSilentiumPC6x Stella HP RGB 140
- ZASILACZGigabyteUD1000GM PG5 1000 W 80 Plus Gold
DISPLAY AND INPUT
- MONITOR ILGUltraGear 32GS95UE-BOLED32"dual mode
- MONITOR IIBenQZOWIE XL241124"1080p
- MYSZRazerDeathAdder V4 Pro
- KLAWIATURAAttack Sharkx68HE PRO
- PODKŁADKALethal Gaming GearPRO XXL SOFT RED
SOUND
- SŁUCHAWKI STUDYJNEBeyerdynamicDT770 PRO LE
- SŁUCHAWKILogitech GPRO X 2 Lightspeed
- GŁOŚNIKILogitechZ906
- MIKROFONRODENT1 5th
- INTERFEJS AUDIORODEAI-1
How it came about
1997
Born that year
I do not remember a world without computers - they were everywhere before I could take an interest in them.
2005
My first own computer
I am eight and I get a machine of my own. There is no going back from there.
2006
First processor swap
Nine years old and my first hardware repair on my own. The machine went up in smoke, but I found out what sits inside and what you must not do.
2008
First lines of code
Eleven years old and my first program. I did not know yet that it would stay with me for good.
PRIMARY SCHOOL
Scripts that locked the mouse
In sixth grade I write my first programs that actually do something to the system: lock the mouse and keyboard, clear out files. Schoolboy pranks, but that is when I first understand how Windows works from the inside.
SECONDARY SCHOOL
First site in PHP
I put up my first site with a real backend. My computer science teacher says then that I will be a great programmer - and I do not think anyone had told me that before.
YEARS LATER
Nights over code, for the sheer fun of it
For years it stays a pure hobby: I can sit over it for twenty-four hours a day, long before any AI exists.
2024
The first beast
I build a machine meant to stop holding me back: sixteen cores, 96 GB of memory and a card that handles compilation, graphics and an AI model at once. The workshop everything else is made in.
2025
I take it seriously
I stop treating it as an after-hours pastime. I start building my own products instead of only taking on other people's commissions.
2026
A clinic system, games and programs
Podivo goes online, Backhaul enters production and the Windows programs become available for download.
03.2026
Work on Podivo begins
I start building the system for podiatry clinics: bookings, team schedule and patient records.
07.2026
Podivo goes online
The clinic system launches on my own servers. That is also when all the code moves under version control - from then on every change leaves a trace.
09.2026
Windows programs and a gaming portal
NBB and MNICH become available for download, Polski Gaming launches with its PC part configurator.
09.2026
Backhaul enters production
The trucking company simulation gets its map, fleet and drivers with characters of their own.
TODAY
On the final stretch before registering
The company is not registered yet, and that is deliberate: products, portfolio and visible progress first, paperwork last. I plan to register at the start of 2027.
Numbers
The numbers come straight from GitHub and from the data layer repository, including work that is not publicly visible - most of my repositories are private.
355
COMMITS IN 12 MONTHS
21
REPOSITORIES
112
DATABASE MIGRATIONS
33
ON-DEMAND FUNCTIONS
16
LANGUAGES IN USE
3
OWN SERVERS
LANGUAGE BREAKDOWN
- JavaScript 37.5%
- HTML 15.2%
- C# 14%
- Python 13.8%
- TypeScript 9.3%
- PLpgSQL 4.3%
- Shell 2%
- reszta 3.9%
Data read on 2026-09-21
What it runs on
None of this sits on off-the-shelf hosting. Three machines, all configured and maintained by me.
Application server
- sites and client panels
- image and file server
- company mail
- HTTPS encryption
Database server
- databases of three systems
- accounts and sign-in
- live notifications
- daily backups
Home server
- project archive
- independent backups
- network drive
- media library
Traffic from the internet never touches the database directly. The machines talk to each other over a private, encrypted link that is invisible from the outside. All services on the application server fit into about 85 MB of memory, because I pick tools to fit the server, not the other way round.
Worth knowing
ZERO INSTEAD OF SIX HUNDRED
Ready-made statistics cards would show a round zero for my profile, because the product repositories are private. The real commit count is several hundred higher and only shows through the API, with my own token.
85 MEGABYTES
That is the memory taken by all services on the application server together. When I needed company mail, the popular ready-made stacks were out at several gigabytes.
FIVE LANGUAGES, ONE SITE
Every page has its own address in Polish, English, German, French and Italian. Pages are rendered before they are sent, so search engines and screen readers get finished text rather than an empty shell.
DRIVERS WITH CHARACTER
In Backhaul every driver has seniority, languages, pay and morale that can fall for weeks if nobody keeps an eye on it.
Hardware manufacturer names and marks used on this site belong to their respective owners and serve only to identify specific devices. They do not imply any partnership, sponsorship or endorsement.