Connects with everything your factory already runs — without replacing what works

The premise: don't replace, connect

Mid-large Brazilian industry has already invested heavily in ERP — Protheus, SAP Business One, Sankhya, Senior. It has MES/WMS/CMMS running for years on the shop floor. It has CRM in some areas. The common scenario is the customer already paid a lot to deploy all this, and each system works well at what it does.

The pain isn't lack of system. It's that the systems don't talk to each other. The same customer exists in two different registries. The production order leaves PCP but the ERP takes 2 hours to register. The QMS inspection report doesn't reach the technical proposal. And when applied AI is asked, it bumps into this fragmentation — there's no way to read the complete operation.

KORE's premise is simple: your ERP stays, your CRM stays, your MES stays. KORE enters as a layer that connects everything, consolidates what lives in multiple places, and enables AI to apply judgment with the complete view.

The architecture, in one diagram

In one figure: KORE talks above the customer perimeter; Connect Agent sits inside the customer's datacenter; system credentials (ERP, CRM, MES, shop-floor) never cross outside.

Connect Agent — what it is

Connect Agent is an IRIS Interoperability service that runs inside the customer's perimeter. It works as the bridge between KORE and internal systems:

• Credentials stay in the datacenter. ERP username and password, MES access certificate, each system's API key — everything loaded into Connect Agent, inside the customer's network. F7 doesn't access. Industrial secret stays.
• Typed adapters, not raw SQL. Each integration is modeled as an adapter with defined schema, input validation and log of each call. Not generic DB-link — controlled data flow.
• Multi-protocol on the same agent. REST, SOAP, RFC, direct DB, OPC-UA, MQTT, Modbus, file-drop — all orchestrated by the same interoperability engine. No additional iPaaS stack per protocol.
• Audit of every call. Who did it, when, with what input, with what response. Under LGPD: native traceability of personal-data access.

When the model is SaaS managed by F7, Connect Agent still exists (installed at the customer's perimeter) — only the "application" part of KORE runs in our dedicated instance. Data sovereignty is preserved in both models.

ERPs covered today

Native adapters with pre-built mapping for the most common registries (customer, vendor, product, invoice, batch, order). Grouped by tier so you scan fast:

Looking for yours? Protheus · SAP B1 · Senior · Sankhya · RM · Omie · Bling · Conta Azul · other

Enterprise

Mid-market

SMB

Another ERP? New customer with ERP outside this list enters as an assisted-deployment case — adapter modeling inside Connect Agent fits within the implementation timeline, with no separate iPaaS charge.

CRMs and commercial tools

When industrial operation connects with commercial operation — sales, relationship, pipeline. Salesforce/HubSpot/Pipefy have prebuilt adapters; the main Brazilian CRMs enter as on-demand adapters inside the deployment (no separate project).

Prebuilt adapter

On-demand adapter

Shop-floor protocols

When KORE needs to reach the shop floor directly — sensor, PLC, production line:

• OPC-UA — industrial standard for read/write to modern PLCs. Covers most new automation systems.
• MQTT — IoT pub/sub protocol for distributed devices. Covers distributed sensing.
• Modbus — legacy but ubiquitous in industrial control. Covers machines with 15-20 years on the floor.
• Structured file-drop — for systems that only export CSV/TXT to a shared folder. KORE detects, validates, ingests.

Legacy administrative systems

• AS/400 / IBM i — administrative Brazilian mainframe still common in mid-large industry. Adapter via native DB2 or web services exposed by the RPG application.
• Legacy ECM — old document repositories via protocol-aware adapters (FileNet, Documentum, M-Files).
• Custom MES/WMS/CMMS — when the customer has a proprietary system or one from a small Brazilian vendor, Connect Agent models it as ad-hoc adapter.

Digital signature and messaging

• Digital signature — DocuSign, Clicksign, ZapSign, Autentique. Adapter for send + receive + audit of each signature per ICP-Brasil.
• Messaging — WhatsApp Business Cloud, Microsoft Teams, Slack, Telegram, Email. The channel through which Kris talks to operator, technician, end customer.

And when the legacy system's API doesn't really work?

Worth saying honestly: in some Brazilian factories there's a legacy system, sometimes the customer's own, where the "official" API simply doesn't cover what's needed. The screen works, the integration doesn't. This scenario isn't exception — it's frequent.

For these cases, KORE offers two paths:

• Assisted schema import. The customer uploads CSV, JSON or a document describing the legacy system structure, and KORE — with Kris applying our integration team's judgment — proposes the mapping to canonical registries. The TI person reviews, adjusts, approves. Reduces days of manual mapping work; the size of the reduction varies by system and source quality, but the gain shows up from the first adapter onwards.
• Connect Agent with ad-hoc adapter. For integration requiring direct read/write into the legacy system (DB, file, RPA), F7 models the adapter inside Connect Agent, inside the customer's perimeter — without exposing the legacy system to the outside.

The same customer, in many places, becomes one registry

Common real case: customer XYZ has a record in the ERP, in the CRM and in a post-sales spreadsheet. Each place with a slightly different name, a tax-ID sometimes formatted sometimes not, an email that changed last semester. When the sales rep calls, they don't know if XYZ is already an active customer. When billing calls, they don't know if the invoice was issued. When support replies, they don't know that XYZ bought another product 6 months ago.

KORE consolidates this. For each relevant registry (customer, vendor, product, equipment, batch, etc), there's a KORE canonical model — standardized common fields — and the system reconciles what comes from each origin into a single consolidated record. When systems disagree, there's a clear rule of who wins per field (tax-ID comes from the fiscal ERP, email comes from CRM, etc).

The result: Kris answers with confidence when you ask "is customer XYZ on track?" — because it sees the consolidated view, not each system separately. And the executive dashboard shows one number, not three that don't match.

Data sovereignty, in one line

In the on-prem model, the entire KORE runs in the customer's datacenter; F7 doesn't access except explicitly contracted support. In the SaaS model, the application runs in F7's dedicated instance in a contracted region (default Brazil), but Connect Agent stays at the customer's perimeter — ERP/MES/CRM credentials never leave. Every external data access is recorded in immutable audit, ready for DPO/LGPD/ISO 27001.

What this changes in operation

• No additional iPaaS project. Customer doesn't need to buy MuleSoft/Boomi/Workato separately. Connect Agent + adapters come inside KORE.
• No ETL to data warehouse. Consolidation happens in real time, on the same platform where Kris acts.
• No "wait 3 months for IT to integrate". When the vendor already has a prebuilt adapter, time between buying and having integration active is days, not months.
• No rewrite of what works. Current ERP remains the source of fiscal/accounting truth. KORE talks to it — doesn't compete.