Contract-first
WSDL, OpenAPI, schemas. We don't start an integration before the contract exists. That removes 80% of the "I thought you meant..." conversations.
About iELLO
Since 2003, we've been integrating business-critical systems.
iELLO is an interoperability services team — not a platform vendor. We deliver integrations that hold up in production, from national eGovernment platforms to bank cores, utility grids, and student registries.
22+
years of integration
work
work
216
integration interfaces
across banking, utilities, education
across banking, utilities, education
99.9%
SLA delivered and tested
— Moldova eGov
— Moldova eGov
6
industries: government, utilities,
banking, education, retail, hospitality
banking, education, retail, hospitality
The story, briefly
We started in 2003, back when "middleware" was a word few people used and almost nobody explained clearly. We took on some of the most complex scenarios imaginable — and kept accepting the next one. Twenty-two years later, the discipline is named; the work hasn't changed much.
Since then we built the national interoperability platform for the Government of Moldova — delivered and tested against 99.9% availability and 250 async messages per second acceptance criteria — and contributed to comparable work in Ukraine. We delivered integration fabrics for UniCredit Bank (core banking, card processing, regulatory reporting over 144 integration interfaces), E-On Delgaz Grid (SAP IS-U, smart metering, GIS, OMS across 25 sub-projects), and the Romanian Ministry of Education's Edulib programme (identity federation for hundreds of thousands of students). Shorter engagements for Cora (now Carrefour), Orange Romania and Protel covered retail eCommerce backends, telco back-office integrations, and hotel management connectivity.
We also led SAP rollouts in Moldova and Georgia for Rompetrol — coordinating a team of specialist subcontractors — which wasn't interoperability work, but the same enterprise integration discipline applied at a different layer. Today, APIs and messaging sit at the centre of every digital strategy, especially where time to value is short and internal teams are thin. Our experience lets us design integration architectures that reduce cost and timelines — without rewriting what already works.
“Good middleware is invisible. You only look at it when it breaks — and we build it precisely so you never have to.”
How we work
Six principles we don't negotiate.
Canonical, not point-to-point
One canonical model across N systems. The N×M problem becomes N. When system N+1 joins, it maps to the canonical model — not to N existing ones.
Audit on every message
Correlation ID, timestamp, signatures where relevant. When someone asks "when and why", there's an answer — not institutional memory.
Deterministic replay
A restart doesn't lose messages. A queue with DLQ catches what can't be delivered. The operator knows exactly what has accumulated, and can replay it in order when the backend returns.
Ownership transferred
At go-live, the client operates the platform. Not a black box — a system their team can run. Runbook, training, at least five concurrent administrators.
No rewrite without cause
12-year-old HIS, 8-year-old SAP, CAD from another vendor — they stay. We build around them, not over them. Rewrites almost always cost more than they return.
What we don't do
Five things we leave to others.
NU
We're not a platform vendor
We don't sell licenses for our own products. We recommend what works for your context, even if that means open-source or a competing stack.
NU
We don't deliver and leave
Every implementation includes an operational runbook, training, and knowledge transfer for at least five concurrent administrators.
NU
We don't speak in empty acronyms
If a word doesn't add precision, we don't use it. "Cutting-edge", "synergize", and "leverage" don't belong in a conversation with a serious client.
NU
We don't promise what we haven't delivered
Scenarios on this site marked "Reference scenario" are real capabilities, not delivered projects. We describe them as such.
NU
We don't confuse governance with paperwork
Governance is a property of the platform, not a Confluence space. If you need a weekly meeting to find out what was deployed last Tuesday, the platform has already failed.
The person
Gabriel Popa
Enterprise architect, integration specialist. Twenty-two years of middleware in production. Direct project experience across banking, utilities, government, and education in Central and Eastern Europe.
Technical background in enterprise integration patterns, SOA, ESB architecture (WSO2, SAP NetWeaver Process Integration), messaging (JMS, ActiveMQ, SWIFT MT, HL7, EDXL-DE), canonical modeling, federated identity (SAML, OAuth2, M-Pass, Azure AD, WSO2 IS), and PKI. Hands-on across 216 integration interfaces in regulated sectors — banking, utilities, education, eGovernment.
Single practitioner in Central and Eastern Europe with a direct track record on national eGovernment platforms in two countries (Moldova, Ukraine contribution), a major Tier-1 bank ESB (UniCredit), a national utility grid (E-On Delgaz Grid), and a ministry-scale education identity programme (Edulib).
The product we're building
NexusFabric — an integration platform built from what fifteen years of WSO2 taught us.
After fifteen years of WSO2 implementations across banking, utilities and government, the same problems kept surfacing: fragmentation across six or more products that don't share a model, opaque runtime state that forces post-hoc archaeology to understand what happened, governance applied after the fact instead of by construction, and XML-heavy configuration that nobody reads the same way twice. We're building NexusFabric to address these directly.
NexusFabric is our product work — a consolidated integration platform where governance, audit, and deterministic replay are properties of the runtime, not documents on a wiki. It is not a release announcement; we are sharing the vision now because the problems it addresses are the same problems our clients bring us every month.
Curious? contact@iello.tech
Selected scenarios
What an iELLO project looks like.
eGovernment
The national interoperability platform for the Government of Moldova — delivered and tested against 99.9% availability and 250 async messages per second acceptance criteria. Comparable work contributed in Ukraine.
Read the scenarioUtilities
For E-On Delgaz Grid: SAP IS-U, smart metering (AMR/HES), GIS, OMS and ADMS on a central bus across 25 sub-projects. 95+ XSLT transformations, canonical nomenclatures, ANAF regulatory e-invoicing.
Read the scenarioBanking
For UniCredit Bank: 144 integration interfaces covering core banking integrations, card processing flows, SWIFT MT940/MT103 messaging with persistent store, and regulatory reporting — with signed envelopes and non-repudiation.
Education
For the Romanian Ministry of Education's Edulib programme: federated identity for hundreds of thousands of students, SIIR synchronization, and a public REST API — built on WSO2 Identity Server and Azure AD.
Read the scenarioRetail
For Cora (now Carrefour) we built the integration layer between their Magento-based online sales site — launched during the pandemic eCommerce surge — and their backend estate, including SAP and loyalty systems.
Hospitality
For Protel: integration between hotel management systems and external consumers of the data those systems collect — channel managers, analytics platforms, and corporate reporting destinations.
Telco
For Orange Romania: back-office integrations between internal operational systems. Neutral, factual engagement — point-to-point flows replaced by a consolidated integration layer.
Health
HIS, EMR and lab systems bridged over HL7 v2.x — with FHIR R4 exposure and DICOM routing — for a regional hospital network.
Read the scenarioPublic safety
Police, fire and EMS on one bus through EDXL-DE. Each agency keeps its own CAD vendor — the fabric handles the rest.
Read the scenario
Trusted by
Partners on delivered projects
