Engage · How you start
It starts with a conversation, not a contract.
Every engagement begins small and stays under your control:
a briefing, a working session, a contained pilot on a single component. Then production — only once it has earned its place. You decide the pace. You own the result. Our role is to make sure you get what you came for.
The problem
The infrastructure decisions made today are harder to reverse than they appear. Not because the technology is wrong — but because the commercial model around it is designed to make leaving cost more than staying. Add unilateral pricing changes on token and subscription models, and the architecture question becomes a financial one before anyone planned for it.
The answer
E-Group builds on open standards with no proprietary lock-in. The architecture runs in your environment — on-premise, private cloud, or sovereign cloud — under your jurisdiction, observable and auditable at every layer. Pricing is predictable because the infrastructure is yours. You own the result. You can leave with it.
The PROOF
KAÜ
Authenticates every Hungarian citizen across every government service since 2003. Architecture the state controls completely — no external pricing decisions, no dependency on a vendor's roadmap.
Ambiti8n
Thirteen components, eight organisations, four countries, demonstrated live before European Commission representatives in Rotterdam — built in four months.
The next step
An architecture studio session with the CTO and the team behind the deployments. No slides. The actual system, explained by the people who built it.
The problem
The business case for AI infrastructure looks straightforward until you model the full picture. Most organisations price the monthly bill. Few price what the bill becomes when the vendor decides to change it — or what it costs to leave once the data is in.
The answer
Six cost categories worth putting on the model before any AI infrastructure commitment:
Exit cost: migration once data gravity sets in. Compute delta: owning at fixed cost versus renting at variable rates you do not set. Pricing exposure:: unplanned subscription or token increases mid-contract. Repricing risk: contract changes over a three to five year horizon on critical operations outside your jurisdiction. Compliance overhead: retrofitting governance and data residency onto infrastructure not designed for it. Governance liability: the board-level exposure of running critical operations on infrastructure you cannot fully audit
The PROOF
CORPEX / Crédit Agricole
30 years, five Central European countries, every regulatory cycle survived — PSD1, PSD2, GDPR, and the full digitisation of European banking.
UnionPay / OTP
400,000+ transactions daily at 99.99% reliability without interruption since 2011.
The next step
A structured working session to build the business case: your cost categories, your planning horizon, your numbers. The output is a model you own, not a proposal we wrote.
The problem
Digital sovereignty is not a procurement preference. It is a policy mandate with consequences. The risk is not choosing the wrong vendor — it is building critical public infrastructure on a foundation that another jurisdiction controls, and discovering the exposure only when it matters most.
The answer
We build infrastructure that belongs to the institutions that run it — legally, technically, and operationally. Every deployment is jurisdiction-compliant by design, auditable at every layer, and built to EU regulatory standards from the ground up rather than retrofitted to meet them. European programmes, European standards, European ownership of the result.
The PROOF
KAÜ + MyD Wallet
Every Hungarian citizen authenticated across every government service since 2003. MyD Wallet passed every published EWC eIDAS 2.0 testbed scenario ahead of the December 2026 EU member-state rollout deadline.
DOME Marketplace
E-Group leads payment subsystems and trusted identity framework for Europe's first federated cloud marketplace — 38 partners across 14 EU countries under the Digital Europe Programme.
The next step
A policy and programme dialogue with the founding leadership — not a sales conversation, a substantive exchange on what sovereign digital infrastructure requires and what we have already built
The problem
The graveyard of enterprise AI is full of pilots. Impressive demonstrations, enthusiastic sponsors, credible vendors — and then nothing. The model never made it to production. The data was never clean enough. The integration was always six months away. The organisation moved on. The fear is not that AI does not work. It is that your name ends up attached to another initiative that proved a concept and changed nothing.
The answer
We do not run pilots for the sake of pilots. Every engagement is designed from the start with production as the only acceptable outcome — the architecture, the data governance, the organisational integration, and the scale path defined before the first model trains. We call this POC to production. It is not a methodology. It is the only way we work.
The PROOF
HeliX
€9.2M EU-funded federated health AI platform connecting 14 partners across Portugal, Italy, Poland, and Hungary. Advancing from TRL 6 toward full commercial deployment by September 2028. Live and progressing, not waiting for the next funding round.
Bosch / FedX
FedX's first automotive deployment — optimising hydrogen fuel cell performance for Bosch commercial trucks through federated learning. Cross-vertical portability proved in production. The first deployment outside healthcare.
The next step
A co-creation session — not a demo, not a presentation. We bring the architecture, the deployment track record, and the researchers. You bring the problem. We leave with a defined path from where you are to something real in your environment.
The problem
The advisory value of a consulting firm depends entirely on the quality of what it can put in front of clients. Recommending a vendor that cannot deliver at the complexity, security, and scale a regulated European enterprise requires is not a neutral mistake — it is a credibility event. The risk is not choosing the wrong technology partner. It is being seen to have chosen the wrong technology partner, in front of a client who trusted your judgment.
The answer
We are not a vendor looking for a channel. We are a technology partner looking for firms that want to build something together — joint go-to-market positioning, co-developed client offerings, shared intellectual property, and the ability to put thirty years of sovereign European AI infrastructure in front of clients who need exactly that and have nowhere else in Europe to find it. The depth is real. The references are named. The delivery is ours to stand behind.
The PROOF
ESA / Galileo
E-Group as Prime Contractor for the Galileo ground station AI programme — predictive maintenance across 26 GNSS stations using two validated AI pipelines, all milestones formally accepted, continuation to full operational deployment under discussion.
Virt8ra / IPCEI-CIS
FedX operating across eight sovereign European cloud providers in six countries through a single federated processing layer — IONOS, Arsys, CloudFerro, OKTAWAVE, and four others — with zero data crossing any national boundary.
The next step
A structured conversation between senior leadership on both sides — about where your client pipeline overlaps with what we build, what a joint offering could look like, and whether the fit is real. We do not do non-disclosure agreements before the first conversation. If the fit is not there we will say so.
Not sure which fits?
Describe your situation. We will point you to the right conversation.
Ask the Concierge. Describe your situation in plain language and it will route you to the right section, the right case study, or the right person.