Good software outlasts today's technology.
We didn't discover AI last week. We're three enterprise software veterans with more than 50 years of combined experience designing, building, and leading production systems for Fortune 500 companies — now applying that same engineering discipline to AI, from intelligent products and agentic systems to private AI infrastructure. We don't build demos; we build software people can depend on.
- 50+
- years of combined enterprise software delivery
- 3
- principals — no juniors, no middlemen
- $1.2B
- annual-revenue programmes led
- 100%
- yours to own — code, infrastructure & IP
We've seen technology waves before.
- 01Microservices
- 02Cloud
- 03Containers
- 04Mobile
- 05DevOps
- 06Now AI
Every generation brings a new technology that promises to replace engineering fundamentals. It never does. The tools evolve; the principles don't. That's why we care as much about architecture, testing, observability, security, documentation, and ownership as we do about models and prompts.
Why we're intentionally small.
Many consultancies scale by adding layers: sales, account managers, project managers, delivery managers, junior developers.
We chose a different model. Every engagement is led by the people who design the architecture, make the technical decisions, and write the code. Conversations stay direct, decisions happen faster, and context isn't lost between teams.
When specialist expertise is needed, we bring in trusted partners — not anonymous benches of consultants.
Small isn't a limitation. It's how we keep quality high.
Six principles we don't compromise on.
- 01
Solve business problems — not AI problems.
We recommend AI only where it creates measurable value. Sometimes deterministic software is the better engineering decision.
- 02
Recommend cloud when it's the right tool.
Public cloud is excellent for many workloads. We use it where it makes technical and commercial sense — not because it's fashionable.
- 03
Recommend private infrastructure when ownership matters.
When economics, compliance, performance, or data sovereignty matter, we build systems you fully own and control.
- 04
Build software your own team can understand.
Clear architecture, readable code, practical documentation — systems that can evolve without us.
- 05
Document everything.
Architecture, operations, deployment, and decisions. Your team should inherit knowledge, not reverse-engineer it.
- 06
Leave you independent.
No proprietary frameworks, no unnecessary dependencies, no vendor lock-in. We measure success by how little you need us after delivery.
Meet the people who'll build it.
No account managers. No sales engineers. No discovery theatre. From the first workshop to production, you work directly with the people making the technical decisions and building the system.
Péter Dajka
Software architect · Full-stack · AI
Designs and builds software across the full stack, combining Java, JavaScript, cloud platforms, and modern AI. From architecture through implementation, his goal is simple: build systems that solve today's problem without becoming tomorrow's technical debt.
Gyula Pál
Advisor · Strategy & delivery
Nearly two decades leading enterprise software programmes for globally recognised organisations, including initiatives supporting businesses with up to $1.2B in annual revenue. He advises on AI strategy, production systems, agentic architectures, and private AI deployment — helping organisations adopt AI without compromising engineering quality.
Zoltán Domonkos
Principal engineer · Java · AI
Specialises in designing and building production software that scales. With deep expertise in Java, distributed systems, and modern AI architectures, he works across the whole lifecycle — from architecture and implementation to production deployment — always focused on reliability, maintainability, and long-term operation.
Why clients hire us.
Not because we know the latest model — because we've spent decades making technology decisions that businesses have to live with for years afterwards.
- We've seen projects succeed.
- We've seen projects fail.
- We've inherited systems no one understood.
- We've untangled architectures that should never have been built.
- We've watched technologies rise, dominate, and disappear.
That experience shapes every recommendation we make. The newest technology is rarely the hardest part — the hard part is building something your organisation can still trust five years from now.
Talk to the people who'll actually build it.
Your first conversation isn't with sales — it's with the engineers who'd design the architecture, challenge your assumptions, and build the system. If we're not the right fit, we'll tell you. If we are, you'll know exactly how we'd approach it.