About us
We connect the dots for you
PannonRex Kft. is a Budapest-based engineering company working with small and large organisations, and with nonprofits, across Europe, the United States, the Middle East and Australia. The work ranges from a two-week technical review to a platform we have run for years.
Position
Small enough to care, senior enough to be useful
Most of our engagements begin because something important is not going well: a system nobody wants to touch, a project that has slipped twice, a board asking what the company is doing about AI. Those conversations need someone who has seen the failure mode before and will describe it plainly.
That is the whole proposition. We are not the cheapest option, and we are not a body shop that will send whoever is on the bench. You get senior engineers who have shipped systems under real constraints, who will disagree with you when it matters, and who write things down so your team can take over.
We work in English and Hungarian, across CET, UK and US business hours, and we are happy to operate inside your process — your board, your review standards, your release train.
The microcomputer years
Where the habits came from
Our senior engineers started on systems where a bad deployment meant a physical visit and a long night. That is where the emphasis on testing, rollback and honest estimation comes from.
The web and enterprise era
Forty million lines later
Banking cores, judicial systems, automotive configuration and industrial tooling — written, ported, re-engineered and kept running for clients across four continents.
Today
AI, with the same discipline
We treat AI systems the way we treat every other system that matters: measured, monitored, documented and owned by the client at the end of it. The technology is new; the engineering is not.
- Years in software engineering
30+
Years in software engineering
Delivering since the microcomputer era, through the web, to AI systems.
- Lines of code written and re-engineered
40M
Lines of code written and re-engineered
Across banking, automotive, public sector and industrial systems.
- Lower cost than the in-house effort
40×
Lower cost than the in-house effort
A clean-room re-implementation, for two per cent of what the client had already spent.
- Continents served
4
Continents served
Clients across Europe, the United States, the Middle East and Australia.
Principles
How we prefer to work
Four things clients can hold us to. They are also the reasons some engagements are not a fit.
We tell you what we think
Including when the honest answer is that your plan will not work, or that the project should not happen. A vendor who only agrees with you is an expensive way to be wrong.
We build for the handover
Every system we write is meant to be maintained by someone else eventually. Documentation, tests and naming are written for the engineer who arrives after we leave.
We stay for the boring part
Anyone can enjoy the first sprint. The value shows up in year three, when the system is still comprehensible and the nights stay quiet.
We work in your constraints
Your compliance regime, your legacy system, your procurement process. Ignoring those does not make them go away; it just moves the problem to the end of the project.
The team
Every role the work needs, under one roof
We staff engagements from our own people rather than subcontracting the gaps. Most projects draw on several of these roles at once; we size the mix to the work and tell you plainly what it needs.
Project and product managers
One person accountable for scope, budget and the schedule you were promised — and for telling you early when any of the three starts to move.
Business analysts
They turn what your business does into something engineers can build, and find the edge cases before the code does.
Senior developers
Engineers who have shipped systems under real constraints, and who will tell you when an approach is going to cost you later.
UX designers
Interfaces built around the work people are actually doing, tested with them before the build rather than after it.
Manual testers
People who use the system the way your users will, and who find what an automated suite was never told to look for.
Test automation engineers
Regression coverage that runs on every change, so the system can keep moving without quietly breaking what already worked.
DevOps engineers
Pipelines, environments, monitoring and releases — the machinery that makes shipping routine instead of an event.
Where a project calls for a role that is not on this list, we say so and bring in the specialist rather than improvising.
How we work
The same four steps, every time
Whether the engagement is a two-week review or a three-year platform build.
01
Understand
We start with your constraints, not our catalogue: the systems you have, the deadline you are held to, the risk you cannot take.
02
Scope honestly
A written plan with the trade-offs visible. What we will build, what we will not, and where the estimate is genuinely uncertain.
03
Ship in slices
Working software in front of real users early and often, so course corrections cost days rather than quarters.
04
Hand over
Documentation, tests and pairing so your team owns the result. We stay available; you are not dependent on us.
Come and test the claim
Book a free consultation and describe the problem. If we are not the right people for it, we will say so and, where we can, point you at someone who is.
Typical reply within one business day · Initial consultation is free