Enterprise track
Integration between software systems
The new system connects to what exists. Nothing has to be replaced.
Most projects do not fail on the development — they fail on the connection. A core system with no documentation, a vendor no longer available, a file format from the nineties. That is where it becomes clear who really knows how to work in an enterprise environment.
We connect through what exists: databases, SOAP and REST services, files, identity systems and archives. Where there is no interface — we build a wrapper around what is there. The only thing we require of the existing system is that it keeps working as usual.
Connections running in production
Against a hospital scheduling system
Appointment booking at Sheba works against the hospital’s existing scheduling system — the patient books, the existing system manages.
Read the caseAgainst the bank’s systems
The correspondence system at the First International Bank group performs actions and produces documents from the bank’s own systems.
Read the caseAgainst clearing and reporting
GabaiNet connects to card clearing, bank standing orders and the required reporting — as a routine part of the system.
Read the caseQuestions that keep coming up
We have an old system with no API — can you connect to it?
Almost always. The connection can go through the database, through files, or through a service wrapper around what exists. The route is chosen at specification — after seeing the system, not before.
How does this work with the vendor of the existing system?
Alongside them, not against them: the interface is defined together and each side’s responsibility is written down. That is how we worked against bank systems, a hospital and clearing providers.
How is the connection kept secure?
Minimal permissions, encrypted transport and a log for every call. A connection to a core system gets exactly what it needs — and nothing more.
Check an integration
Tell us which systems need connecting — we will come back with an honest assessment.