Security & deployment
The accelerator runs entirely on your infrastructure and touches your SAP landscape read-only. This page describes the posture your vendor-risk team will ask about.
Nothing leaves your environment
The engine is a self-contained C++ binary with a browser-based interface, deployed on a single Linux server you control — on-premises or in your own cloud tenancy. Source code, table data, and generated artifacts remain on that server.
Read-only by design
Two ingest paths, both non-invasive: file-based upload of ABAP source and SE80 dumps, or an RFC connection used for read-only metadata extraction. The engine writes nothing to the SAP system.
No secrets in config files
Connection parameters live in INI files; credentials are supplied through environment variables and are never stored on disk by the engine.
Timestamped, traceable outputs
Every generated artifact, complexity report, and MDM-readiness assessment is timestamped. Advanced mathematical algorithms are used only to indicate whether a separate MDM workstream may be required; the accelerator does not implement or deliver MDM. Duplicate findings include exact counts with anonymized sample records — evidence your auditors can retrace.
Deployment requirements
| Component | Requirement |
|---|---|
| Server | Single Linux server (x86-64), customer-provisioned |
| Reference benchmark host | 8-core, 256 GB Azure instance, 2 TB SSD |
| SAP connectivity | Optional RFC (read-only metadata) — or fully offline via file upload |
| Network egress | None required for operation |
Put it in front of your security team.
We support vendor-risk review as part of every evaluation.
Request a briefing