We connect Claude, Gemini and OCI to the ERP your team already uses.

What decides whether a project reaches production is not the model — it is the wiring to what already exists. That is the work we do first.

The model is the small slice of the work. What decides whether a project reaches production is the connection to what already exists: authentication, permissions, transactions, logging, failure tolerance and the habits of the people who use it.

Why pilots never reach production

A prototype runs on a laptop against exported data. A production system runs against the real database, with concurrent users, per-profile permissions, maintenance windows and a plan for when the external service does not respond.

The distance between the two is not about modelling — it is engineering. It is the work we do first, not what we leave until the end.

What we connect to

• Databases. Oracle, SQL Server, PostgreSQL — read access with the application's permissions, not a shared administrator account.
• ERP and management systems. Through the API where one exists, through the supported integration layer where it does not. Never by writing directly into tables that are not ours.
• Internal applications. Angular, .NET, older Delphi or AS/400 systems — the interface stays the one the team is used to.
• Queues and events. Kafka, message queues and scheduled jobs, so AI enters the flow without blocking it.

Architecture principles

• The model is replaceable. It sits behind our own layer, so switching provider is a configuration change rather than a rewrite.
• Failure is planned for. If the AI service does not answer, the process degrades to the manual path instead of stopping.
• Everything that decides is logged. Input, context used, answer, confidence and who confirmed it.
• Cost is visible. Consumption per process and per period, with an alert before the invoice surprises anyone.

What you get

• The integration working in a production environment, with tests and monitoring.
• Documentation of the architecture and the connection points, so your team can maintain it without depending on us.
• Support through the first weeks of real use, which is when the cases nobody anticipated show up.

Frequently asked questions

Do you work with legacy systems?

Yes, that is where most of the useful work is. We have experience with Oracle, AS/400 and Delphi applications still in production. The approach is to connect without touching what works.

Do we need to migrate to the cloud?

Not necessarily. There are fully on-premises architectures and mixed ones. The choice follows from your data requirements, not from a preference of ours.

Who owns the code?

The client. We hand over code, documentation and access. We do not build vendor lock-in by design.

← All services