Services
System integration
If somebody in your company retypes the same data from one system into another every day, that is not a discipline problem — it is a missing integration. It is also usually the cheapest IT project you can commission, because none of the existing systems has to be replaced.
First we establish where the data actually lives
Before connecting anything, we determine which system is the source of truth for each set of data and which merely holds a copy. Without that, an integration spreads contradictory information through a company faster than any human with a spreadsheet ever could.
We build connections that survive failure
An integration spends most of its life in unusual situations: the other side is down, the file arrived incomplete, the same document arrived twice. Retries, queueing and duplicate detection are designed in from the start, because adding them later usually means rewriting the whole thing.
- Safe retries that do not duplicate documents
- Visible state: what went through, what is waiting, what needs a human decision
- Alerts routed to people who can actually act on them
Legacy systems count too
Not every system has a modern API — sometimes it is a file export, a database, or a protocol older than the team using it. We have worked both with modern platforms such as ServiceNow and Steam, and with systems that needed a connector written from scratch.
Common questions
Our system has no API. Can it still be integrated?
Usually yes. If it can export data or its database is reachable, there is something to work with. In the Skins Guard project the Steam integration was written in C#, because that was the only way to handle that platform’s protocol properly.
How long does an integration take?
A straightforward exchange between two systems is a matter of weeks rather than months. The duration grows with the number of edge cases, not the number of systems — most of the work is deciding what to do with records that fit no rule.
What happens when one system goes down?
The integration should hold and wait, rather than lose a document or send it twice. We design that explicitly: a queue, retries, and a visible state for every document being processed.
Tell us what you need built
A short description of the problem is enough to start. We reply within one working day with concrete questions, and for new clients the estimate is free.