There is a reasonable way to rate a software studio and an unreasonable one. The unreasonable way is to read the marketing. The reasonable way is to ask what the company has running in production and who depends on it, because production is the only place where the shortcuts show.
So here is our own inventory, written the way we would want to read a competitor's.
Products we run, not just build
Devcity operates its own software rather than only delivering it and moving on. That distinction matters more than it sounds, because a studio that runs what it builds carries the cost of every lazy decision it makes.
- RekordPOS, a point of sale system for restaurants and shops, built to keep taking orders when the connection is not there.
- RekordPlate, number plate recognition and the parking workflow around it.
- Luzo Fleet, vehicle tracking for logistics teams that operate across islands.
- Luzo Suite, a business management platform covering the ordinary back office work every company has.
- Devcity Mail, business mailboxes on your own domain, which we run on our own servers.
- Hosting and domains, including registration and renewal, on infrastructure we manage.
Every one of those has customers on it. That is the part that changes how a team writes software.
What running your own product teaches you
When you only build for clients, a slow page is a comment in a review meeting. When you run the product, a slow page is your phone at seven in the morning. The lesson arrives faster and it sticks.
A few things we do differently because of it:
We check outcomes, not configuration
It is easy to build a system that reports itself healthy. The harder and far more useful thing is to check what actually happened. Did the backup file open and contain messages, or does it merely exist? Did the message actually arrive, or did the server merely accept it? Is the site actually being served on a certificate a browser trusts, or did the setup step merely report success?
We ask the second version of those questions on a schedule, every day, because the first version has been green while the truth was not more than once.
We prefer boring technology
Our stack is deliberately unfashionable. Laravel on a normal server, a normal database, files on disk. It deploys to ordinary hosting, it can be handed to another developer without a training course, and it will still make sense in five years. Exciting technology choices are usually a cost the client pays later.
We write down why, not just what
Every unusual decision in our codebases carries a note explaining what went wrong the day it was made. That is not tidiness. It is the only reliable way to stop the next person, including a future version of us, from undoing a fix and reintroducing an outage.
How fast we actually ship
Honest answer: it depends entirely on how clear the problem is. A well defined internal tool can be in front of staff within a few weeks. A platform with payments, roles, reporting and a mobile app takes months, and any company that tells you otherwise is planning to hand you something you will have to rebuild.
What we can promise about pace is the shape of it. You see something working early and often, rather than a long silence followed by a launch. If a milestone is going to slip, you hear it from us while there is still time to make a decision about it.
What we are not
A fair rating includes the gaps. We are a small studio, so we do not staff a night shift, and we say so rather than implying a service we do not run. We are opinionated about technology choices and we will push back on a stack we cannot maintain. We would rather turn down work that does not fit than take it and do it badly, because in a market this size every project is a reference whether it was meant to be or not.
Rate us the way we asked you to rate everybody
Open something we run. Ask who owns the code. Ask what support looks like on year three. Send us a hard question and see how long the answer takes and whether it is honest when the answer is no.
If that goes well, start a conversation. If you want the detail first, our services and products pages are the plainest description of what we do.