Art of Digital Manufacturing Design and run integrations between SAP, cloud applications and your on-premise systems on one platform, and track every message.
The AI agent writes and tests the flow; your specialist reviews and approves it. Flows are readable in the visual designer, so your own team can take over maintenance.
Every message can be found by order or invoice number, so the support team sees the failing step for itself. Failed messages in the queue are not deleted; they are retried.
More than 350 connectors bring cloud services, databases and factory systems together in the same flow, so you don’t write connections from scratch.
Lunex calls SAP functions (RFC/BAPI). You search for a function, see its fields and get a sample request ready to use; your agent works with the same information.
MCP-compatible agents such as Claude Code and Codex work with the employee’s own account and permissions, in the development environment only. They can’t reach production, and every change has a clear owner.
Lunex runs in your own data center or private cloud, and users sign in with their corporate identity. Your flows stay in an open format, in your own Git repository.
The agent opens a project in Lunex and writes the OpenAPI contract and the routes; in the development environment the service returns live exchange rates from the Central Bank of the Republic of Türkiye (TCMB).
Every integration appears as a step-by-step diagram: timer, transformation, decision, target system. You select a step and edit its properties in the right-hand panel; the same flow also opens as YAML.
You run the flow with a sample input and see how the message changes before and after each step. If something fails, it states clearly at which step and by which rule the flow stopped.
You build the OpenAPI contract in a visual editor: paths, operations, schemas, field rules. Each operation is bound to its own flow, and incoming requests are validated against the contract.
From the same screen you send a request to the running development environment and see the response, status code and duration. A request that breaks the contract comes back with the layer that rejected it.
In Message Monitor you search for a message by order, invoice or a business number you define yourself. Which flow it passed through, how long it took and where it stopped are shown on one screen.
Flows are kept as YAML files in your own Git repository. You select the changed files and push them, build the version and move it from development to production from the same source.
Fetch daily exchange rates automatically and write them to SAP right away, with full traceability.
Connect production systems to SAP and other platforms; data in a single real-time flow.
Read the data in certificates and reports with AI and post quality results to the system automatically.
Lunex runs on your own infrastructure, with your own identity system. Flows are kept in an open format in your Git repository, and connections use standard protocols.
On-premise Kubernetes; installation with Helm, offline installation supported.
YAML files versioned with Git; the same source for development and production.
RFC/BAPI calls and transaction management with SAP JCo.
Access over MCP, with the user’s own identity and permissions.
Single sign-on with Keycloak/OIDC, role-based permissions, end-to-end HTTPS.
Persistent queues; failed messages are kept and retried.
Web services, databases, file servers, messaging systems and OPC UA servers on the shop floor come together in the same flow. Try the two-way flow between SAP EWM and an automated warehouse in the ASRS demo.
SAP is a trademark of SAP SE. The SAP JCo library is provided under the customer’s SAP license. Other product names belong to their respective owners.
The guide covers all of Lunex with step-by-step tutorials, downloadable sample projects and troubleshooting topics. Start wherever suits your goal. The guide is currently available in Turkish only.
Full user guide (in Turkish)Create a project, process a message and find the same message in Message Monitor.
API Create your first APIBuild the OpenAPI contract, bind the operation to a flow and test it in the running project.
SAP Connect to SAPSearch for a function, inspect its fields and add the RFC/BAPI call to a flow.
AI Build with your own agentConnect an agent such as Claude Code or Codex to the development environment with your own permissions.
Monitoring Trace a transaction end to endSearch for a message by order or invoice number and inspect the failing step and its history.
Installation Install on your own infrastructureKubernetes installation, external services, corporate identity and operations.
It runs on Kubernetes in your own data center or private cloud. Offline installation is supported for environments without internet access; your data never leaves your organization.
No. Agents work with the employee’s own account and permissions, in the development environment only. Your team always makes the decision to go to production, and every change is recorded with the account that made it.
Yes. There are more than 350 ready-made connectors, including REST and SOAP services, databases, file servers, messaging systems such as Kafka and MQTT, and factory systems over OPC UA.
No. Flows are kept as YAML files in an open format in your own Git repository; they are readable, versionable and stay within your organization.
Write to us for a demo. In the first meeting we review the systems you want to connect and your existing integrations together.