Systems that talk to each other
Interfaces & APIs
Data where it is needed.
Inventory, shop, accounting, marketplaces, custom applications: most businesses run several systems side by side, but not together. I connect them through interfaces and APIs.
That way data no longer has to be moved by hand, typing errors disappear, and every system is up to date.
Why interfaces
Each program on its own usually does exactly what it was bought for. The problem lies in between: when data moves by hand from one system to the next, it costs time and leads to errors and duplicate maintenance.
An interface makes systems exchange data automatically. Orders land in the inventory system, stock in the shop, figures in the report, without anyone copying.
I build interfaces to existing systems as well as custom APIs for applications others should connect to, all the way to machines in production.
Request a projectInventory, shop, accounting, marketplaces
Connecting existing systems
I connect inventory, shop, accounting, marketplaces and third-party services, so data flows automatically. I am especially at home with JTL-Wawi and JTL-Shop.
One example: a module that puts quotes and orders straight from the shop into the Wawi, as if a real user had created them.
More on JTL-Wawi & Shop
For your own applications
Custom REST APIs
If your application should be connected to by others, it gets its own REST API: clearly documented, secured and built so other developers understand it quickly.
For NexoVirt, for example, I built an API you understand in an afternoon, instead of the clunky interface Proxmox itself ships with.
View NexoVirt
Software meets production
Connecting machines
Interfaces are not only between programs. In furniture manufacturing every machine knew via an interface which board to cut, mill and edge how.
In the same way I connect machines, scanners and microcontrollers to your systems, so production data is processed automatically.
More on automation
When there is no ready-made interface
Straight on the database
Not every system comes with a suitable interface. Where it makes sense, I work cleanly on the database directly, for example on the Microsoft SQL database behind JTL-Wawi.
The rule: as little intervention as possible, clearly documented, so system updates do not break anything.
More on my technologies
For ChatGPT, Claude and co.
Interfaces for AI
AI assistants need interfaces too. NZ GEO Visibility includes a read-only access (MCP) that can be added as a connector in Claude or ChatGPT.
Secured with access keys and rate limiting, without any write access. So AI systems can work with your data without you giving up control.
More on AI visibility
How your interface comes together
-
Look at the systems
We clarify which systems are involved, which data should flow and in which direction.
-
Concept & fixed price
I check the existing interfaces and plan the data flow. You get a binding fixed-price quote.
-
Build & test
I build the interface and test it with real data before it goes live.
-
Operation
On request I monitor the interface, so errors get noticed before they have consequences.
What does an interface cost?
The price depends on how many systems are involved and what they offer. Small interfaces start in the low four figures, larger integrations well above that.
After a short conversation you get a rough estimate, after the concept a binding fixed-price quote.
Request a project
Tell me what is not working for you.
Describe in a few sentences what it is about and what is missing today. The more concrete, the more useful the answer. First response usually the same day.