Security and data handling
The box runs in your network and never connects to SAP. The only write to SAP is your developer's own pull of approved code. It makes one optional outbound call, to the model endpoint you configure with your own key. Nothing goes to us. The independent security review and penetration test have not been carried out yet.
At a glance
What a security architect asks first, with the answer as the product stands in the pilot release.
- Deployment
- One container on one Linux VM that you run, in your network.
- SAP access
- None. The box holds no SAP credentials and opens no connection to any SAP system. A developer pulls approved code into S/4, under their own transport.
- Outbound calls
- One, optional: the model endpoint you configure. Leave it unset and the box makes no outbound call. Sync to your Git provider, when it is released and you switch it on, adds a second: to the repository address you enter. Roadmap
- Model key
- Yours. Held on your VM and sent only to your endpoint. The box removes it from the log lines and error text of its model calls.
- Telemetry
- None. Nothing is sent to the vendor.
- Licence check
- Offline. A signed file checked on the box. No network call.
- Identity
- Local accounts with four roles. Each SAP system has its own access, limited to what it needs. Single sign-on is on the roadmap.
- Audit
- Every Retrofit, decision and edit is kept, with an audit export for each approved Retrofit.
- Data retention
- The box keeps everything and has no purge. Deleting data at the end of a contract is an action on your own VM.
- Independent testing
- Not yet carried out. A security review and penetration test are scheduled before production use.
Where data moves
Everything stays inside your network except one optional call. The box never calls SAP, and a person does the one thing that changes SAP.
The box has no connection to either SAP system. SAP systems call the box, never the other way round. The model endpoint is outside your network unless you point it elsewhere, and the private endpoint option is on the roadmap.
| Flow | What moves | Protection |
|---|---|---|
| ECC to box | ABAP source and its change history for each BAU change, exported automatically. | HTTPS. ECC has its own access, which can deliver BAU changes and cannot change the S/4 code line. |
| S/4 and box | Your converted code, given to the box from S/4. Approved code, when the developer pulls it. | HTTPS. S/4 has its own access. The pull is a person's action, under their own transport. |
| Box to model endpoint | Optional. One ABAP file at a time, only when the box cannot settle it on its own. Detail in the AI section below. | Your key, sent only to your endpoint. The answer is checked like any other change. |
| Reviewer to box | The review queue in a browser: Retrofits, differences, approvals. | HTTPS. Local accounts and roles. A reviewer cannot approve a transport they authored. |
| Box to SAP | Nothing. | No connection exists. The box holds no SAP credentials. |
| Box to vendor | Nothing. | No telemetry. The licence is checked offline. |
What the box never does
Each line is a fixed behaviour of the product, not a setting. The pilot acceptance plan includes a check that SAP's own transport logs show no writes by the box.
- It never connects to an SAP system.
- It never writes to SAP. The only write is a developer's own pull of approved code.
- It never sends code or data to the vendor.
- It sends no telemetry.
- It never phones home for the licence. The check is offline.
- It never stores the model key in logs, reports or exports.
- It never applies an AI result it is not confident in, or one that fails a check.
- It never purges records. Every record is kept.
AI and data handling
The model is optional and it is yours. With a hosted provider, the ABAP source in each call leaves your network. We say that plainly because it is the one place your code goes outside it.
With Anthropic, OpenAI or Azure OpenAI, the file text in each call, and what the box found in it, travel to that provider's service. A private OpenAI-compatible endpoint, which would keep the call inside your network, is on the roadmap and is not available today.
Roadmap Private OpenAI-compatible endpoint
What is sent
ABAP source files only, one file at a time, and only a file the box could not settle on its own. The call can carry the versions of that file, its path, the target S/4HANA release name and what the box found in it. The full text of the file is sent, not excerpts. A very large file is not sent.
What is never sent
- SAP table data, or anything read from an SAP system.
- Transport numbers, transport descriptions and commit messages.
- Commit authors and SAP user ids.
- Dictionary and metadata files.
- Other files, other objects, other transports.
- Retrofit history, approvals, the licence file and any credential.
Your key
You bring the key and pay your provider directly. It sits on your VM and is sent only to the endpoint you configure, never to any other address. The box removes it from the log lines and error text of its model calls. You can rotate it at any time.
Providers
Anthropic, OpenAI and Azure OpenAI. You choose the provider, the endpoint and the model name. How a provider stores or uses what it receives is set by your agreement with it, which you should read before enabling the model. We make no statement about it. The box accepts only an HTTPS endpoint. With any other address it makes no model call, and what it cannot settle goes to a person as it does without a model.
Confidence and checks
The model returns a confidence figure, which is its own estimate and not a measured accuracy. Where the box is not confident in an answer, nothing is written and the object goes to a person, with the confidence shown. Every AI result is then checked like any other change, and one that fails is not applied. No AI result reaches your S/4 code until a reviewer approves it.
With no key
Supply no key and the box still runs. Its own rules and checks apply, and what they cannot settle goes to a person.
Access control
Each SAP system has its own access to the box. Accounts and roles decide who can review and approve.
Four roles
Administrator, Developer, Reviewer and Retrofit team. Accounts are local to the box. Single sign-on is on the roadmap. Roadmap
Separate access for each system
ECC and S/4 each have their own access to the box, limited to what that system needs. ECC cannot change the S/4 code line, and S/4 cannot change the ECC one.
Shown once, never stored readable
The box shows an access credential once, when it is created, and never stores it in a readable form. A revoked credential is refused on its next request.
Results cannot be forged
Only the box writes a Retrofit result. Neither SAP system's access can create or change one.
History cannot be rewritten
The box refuses any attempt from outside to rewrite or delete the main ECC and S/4 code lines it holds.
Reviewer is never the author
The author of a transport cannot approve its Retrofit. The box enforces it.
Licence, audit and retention
The licence cannot lock you out of your own code, and the record of what happened is not something the product deletes.
Offline signed licence
A signed licence file, verified on the box and bound to your installation. The check makes no network call.
Never locks your code in
An invalid, expired or missing licence stops new changes being processed. It never stops you taking your code out.
Every decision is kept
Every Retrofit, decision and edit is recorded, including who approved and which edits were made in review. An edit made in review joins the approval and the audit trail.
Audit export
An exportable record for each approved Retrofit: inputs, outcomes, rationale and approver. In the pilot release nothing in the product changes or removes an audit event, and that rests on the product's own code.
Tamper-evident log Roadmap
The audit log will carry a cryptographic check, so a later change to any record shows, and it will export in a form your auditor can verify without the box. It is tamper-evident, not tamper-proof. Built and tested, not yet in a release.
No retention purge
Every result and every record is kept. Nothing in the product deletes a repository or a Retrofit.
Deletion is yours
The box sends no data to the vendor, so deleting data at the end of a contract means removing the data volume and every backup archive on your own VM.
Operations
A single container on a VM you control. The parts you secure are the ones you already know how to secure.
Container on a Linux VM
One container, run with Docker, on one Linux VM in your network. Everything the box holds lives on one data volume.
TLS at the reverse proxy
A reverse proxy on the VM terminates TLS and forwards to the box. Nothing outside the VM can reach the box directly. We supply an example configuration for the proxy.
Backup by archiving the volume
Stop the box, archive the data volume, start it again. A restore keeps existing access working. The box does not encrypt the volume or the archive: disk and backup encryption are yours.
Logs and health
The container logs start-up, accepted changes and errors. A health address reports that the box is up and which version it runs, and no customer data.
Installer and support bundle
Installation is from a runbook by your Basis team. A guided installer and a support bundle are not built yet. Roadmap
Your side of the line
You own the host, its patching and hardening, the firewall, the DNS name and certificate, the admin credential, the configuration file and who can read it.
Open items
What is not done, stated before you have to ask.
The independent security review and penetration test have not been carried out. They are scheduled before production use. The build has its own automated tests, and those are not a substitute. Until the review is done, treat this page as the vendor's description of the product, not as independent assurance. We claim no certification or compliance.
| Item | Status | What it means for you |
|---|---|---|
| Single sign-on | Roadmap | Accounts are local to the box until it ships. |
| Private OpenAI-compatible model endpoint | Roadmap | Until it ships, a model call always goes to a hosted provider, or you run without a model. |
| Hosted tenant | Roadmap | The box runs only on your own VM. |
| Installer and support bundle | Roadmap | Install from the runbook. Collect logs yourself. |
| Reach of the admin API | Your decision | The admin interface is reachable wherever the box is, and an admin credential protects it. Restrict it at the proxy or the firewall to operator networks if you do not want that. |
| Vulnerability disclosure process | To be agreed | The reporting contact and process are agreed with you before the pilot starts. |
The full security whitepaper and the AI and data handling statement are available on request, with the interface and data inventories behind this page. Ask for them when you request a pilot.