Secure by design
“What if it breaks production?” It won't. That is built into the design, not into a prompt.
Read-only is a tool boundary
- A read-only role physically cannot write.Read tools and write tools are separate sets; read-only roles simply aren't handed the write tools. The boundary is in the code, not a request to the AI to “behave.” Enforced on both sides: the on-device connector and the server broker each refuse writes on a read-only tier.
- The broker checks every call.Every SAP tool call goes through the connector broker; a call outside the current role's set is rejected there and never reaches SAP. For engines without their own allow-list (Codex, Kimi) this is the main and only gate, and it holds.
- SAP object deletion is permanently disabled.
sap_delete_objectis in no role, and the broker blocks it unconditionally. There is no switch to turn it on.
Only Development writes, and only on a dev system. Every Support and Consulting role is read-only. See every role's access →
Two-person gate
No write without a human in autonomous mode. A two-step human gate: a person approves, then separately confirms the apply. How autonomous mode works →
A full audit log
A full audit log. Every tool call (flagged on writes), every connection, error and agent run is recorded and available to the admin.
Everything on your server
Your SAP connection and credentials stay on your infrastructure.
You stand up your own backend, database and SAP connection. The SAP connection, the AI key and the sign-in credentials stay on your server. There is no data path to Makion, the vendor never sees your code. Your code is analysed by your own AI account, on your provider's terms. That's exactly why Makion also works where SAP's cloud tooling falls short: on your on-prem systems and old ECC. For teams whose main objection to AI in SAP is a third party sitting between them and their system, Makion removes the vendor from the middle.
Installed on your server. Your SAP, your AI account, your key. It uses your own AI account, via your API key or subscription (where your provider's terms allow), and runs on your server. Everything stays on your infrastructure. Model keys are a server-side secret: injected only into the agent process, never shown to the client and never logged.
- Your backend, your database. Deployed on infrastructure you control.
- Keys and credentials are a server-side secret. Never shown to the client.
- No third-party SaaS. SAP data doesn't go to a service run by Makion, and your licence is verified offline. No phone-home.
- S/4HANA and on-prem alike. Wherever ADT reaches, where SAP's cloud tooling can't.
Managed in the desktop app
Engines, roles, specs, projects, autonomous mode, model sign-in.
No digging into config files for every little thing. Engines and role methodology, specs, projects, turning autonomous mode on/off, model sign-in: it's all managed right in the desktop app. Isolation follows the principle channel = one developer × one project: each channel has its own SAP connection, its own workspace and its own history. Several developers comfortably share one Makion instance without mixing systems and sessions.
Chat versus autonomous
Questions
What if it breaks production?
It won't. That is built into the design, not into a prompt. Only Development writes, and only on a development-tier system. Read-only roles are never handed the write tools, the broker rejects any call outside the role's set, and SAP object deletion is permanently disabled.
Does Makion see my code?
No. There is no data path to Makion, the vendor never sees your code. Your code is analysed by your own AI account, on your provider's terms. The SAP connection, the AI key and the sign-in credentials stay on your server.
Can the agent delete SAP objects?
No. sap_delete_object is in no role, and the broker blocks it unconditionally. There is no switch to turn it on.
Is there a gate on every write?
In autonomous mode, yes: a person approves the queue item, then separately confirms the apply. In an interactive chat a write-permission role makes the change during the dialogue you're running; you steer step by step. If you need a hard button-gate on every write, use autonomous mode with the ship queue.
Put Makion inside your SAP
Your SAP, your standards, your terms.
Several developers or a client rollout? Teams & enterprise