Problem

Integration gets handled only once it starts to hurt

The most common path to integration looks like this: export a CSV, write a script to load it elsewhere, and over time a second script, a third webhook, and a fourth manual copy-paste get added "because it wasn't finishing overnight." The result is integration with no architecture — it works until one of the systems changes, and then nobody knows what all it will break.

The other extreme: buying an expensive integration platform (ESB, iPaaS) that promises to solve everything — and itself becomes yet another system that needs managing, licensing, and integrating. Neither is a solution. Integration should be an architectural decision, not a technical detail bolted on at the last minute.

❌ Integration with no architecture

A web of scripts nobody wants to open

× Every system has its own version of the "truth" about the same data
× Connections break with every change on one side
× Nobody knows exactly what feeds into what, or in what order
× Error states are handled manually, if someone happens to notice

✓ Integration as architecture

One model, several systems as projections

✓ A clearly defined source of truth for each type of data
✓ Contracts between systems that can be tested and monitored
✓ A new integration gets added, not layered on top of existing rewrites
✓ Errors and mismatches are visible, not hidden in a log

What I actually do

From design to a working connection

I design integration as part of the overall architecture, not as an isolated technical task. Depending on the situation, it's design, delivery, or both.

Integration analysis and design

I map out where the data actually originates, what's the source of truth and what's just a copy, and design how to connect the systems — via API, batches, or federated querying across sources with no need to physically copy the data.

Federated data connections

Connecting across diverse sources (SQL, LDAP, API, file storage) into a single reporting or operational view — with no need to build and maintain your own data warehouse.

APIs and data contracts

Designing interfaces between systems so they can be verified and tested — not just hoping the other side sends what's expected. A contract as an enforceable agreement, not a comment in the code.

Delivery and second opinion

I either build the integration myself, or oversee the vendor building it for you — just like with IT construction oversight: I make sure the connection can handle three more systems on top of it.

When to call me

Five situations where integration gets handled like a fire drill

✓ The same number (revenue, stock, attendance) comes out differently in every system

✓ The connection between systems depends on one person's script that you're afraid to let go on holiday

✓ You're introducing a new system and need it connected to existing ones without vendor lock-in

✓ You want to connect AI agents and automations to your data without building a new data warehouse

✓ Your integration vendor claims there's no other way — and you need an independent assessment

Why me

Integration I've already built once before

I was already designing federated connections across diverse data sources (SQL and LDAP in one query) back in the d.reporting tool in 2007 — and today I'm reviving that idea as ARIS, part of the Atra/Atrust platform. To me, integration isn't a one-off engagement, but a discipline I keep developing long-term as a product of my own, not just as a service.

16+

years in production

The d.process low-code platform — deployed in 2010, still running in public administration today

2007

first federated integration

d.reporting — connecting SQL and LDAP in a single query, revived today as ARIS

years of experience

From 1990, through proprietary languages and virtual machines, to AI pipelines · Ing., ČVUT FEL

Bonus for companies with 25+ employees

Integration work can be drawn under an alternative performance scheme

I am a registered provider of alternative performance under § 81 of Act No. 435/2004 Coll. The same money you'd otherwise pay the state with nothing in return can fund the design and delivery of integration between your systems.

How alternative performance works →

Next step

One source of truth.
As many systems as you like.

The introductory consultation is free of charge and takes place online: we'll go through what systems you have and what actually needs connecting, and I'll design what the integration should look like.

Request a system integration →

Jakub Lebeda · Company ID (IČO) 19074671 · +420 607 720 317