Alongside your business as it grows.
We are a small software boutique. We take on a few projects at a time, so yours gets the attention it deserves.
The market sells speed. Nobody sells endurance.
Before building our own company we spent years inside other people's — different sizes, different clients, different problems. And one pattern everywhere: speed is visible, endurance never is. Until the day it is missing.
A homepage that takes your breath away and a checkout that breaks. A store that works perfectly as long as nobody touches it, where the first update breaks three things. A handover with no documentation, where the next person starts from zero. None of that shows in the pitch; all of it shows in the turnover.
iRox started with no clients. It sounds reckless, but it was the only way to avoid building the company around filling a calendar. When you start with ten projects in hand, the calendar makes your decisions.
Iron oxide. Rust.
The name came from iron, and the x from ox: iron oxide. Rust. It sounds strange for a company until you think about what rust actually is — what happens to iron when you leave it alone.
It does not snap. It decays quietly, from the inside, while the outside still looks solid — until the day you lean on it and it gives. That is exactly what happens to software nobody looks after: it does not collapse, it oxidises. A dependency left years without an update. A temporary fix that became permanent. A piece nobody dares touch any more.
So the name does not say what we sell. It carries the problem we are trying to solve — and reminds us that iron, however solid, needs somebody watching it. It came before the first client, in that order and not the reverse.
Size decides what you can promise.
Small not because small is romantic, but because it is how we keep the promises we make.
Few projects at a time
One finishes, the next begins. We have seen the alternative from the inside: ten projects in parallel, all at 80%, everyone mildly unhappy.
You talk to the person who writes it
There is no layer in between mistranslating what you asked for. The person in the conversation is the person who writes the code.
Straight answers from the start
If something will not fit the timeline or the budget you need, you hear it from us before we start — not halfway through. We would rather have an honest conversation than make a hasty promise.
A few things, in depth.
OpenCart
It is the platform we work with every day. We write and maintain our own extensions for the Greek market, and we contribute to the development of OpenCart itself: the public discussion that led to the project's community governance in 2026 was opened by us.
Tourism systems
Hotels, accommodation and tourism businesses. Presentation, availability, bookings and the integrations needed so the same work is not done twice.
Real-estate systems
Property platforms with listings, advanced search and portfolio management — built around how an agency actually works.
A project that grows does not scare us. The opposite.
There is a view that a project which expands is a burden — something that escaped its original scope. To us it is the point. If your business is growing and the software has to follow, that means the first piece of work landed.
That is why we write code somebody else can read in two years, and documentation that explains the why, not only the what. We want to be alongside the business as it goes, not to hand something over and disappear.
Tell us what you have in mind.
A first conversation commits you to nothing. We will listen to what you need and tell you honestly how we would approach it.
Get in touch