Skip to content
ERP Preflight

Prevent · Explain · Govern

Know what will break before production does.

The deterministic safety layer before SAP change, migration and production: one verdict with evidence across transports, code, interfaces, extensions, forms and authorizations.

Run a PreflightExplore free tools

Or open the demo sandbox

  • Same input, same result
  • SHA-256 evidence for every finding
  • Artifacts, not your SAP password
Illustration with sample dataIllustration of the findings view with sample data: four findings with severity, finding code, engine and confidence class, the evidence of the selected blocker with file, line, code snippet and SHA-256 hash, and the release gate verdict.

Why preflight

Changes fail in production for reasons that were visible before

Most production incidents after an SAP change are not mysteries. The missing decision table row, the transport imported without its predecessor, the custom field that never reaches the form — the evidence existed in configuration and code before go-live. It was simply not checked systematically.

  • Output is not created because a BRFplus determination step has no matching rule.
  • A transport is imported before the dictionary change it depends on.
  • Custom code writes directly to standard tables and blocks a clean core target.
  • A Fiori app returns 403 because a service authorization is missing from a role.

One safety layer, three jobs

Prevent what would break. Explain what did. Govern what ships.

ERP Preflight is the deterministic safety layer before SAP change, migration and production. You bring the artifacts of a change, a migration or an incident — you get one answer with evidence, not a list of tools to choose from.

  • Prevent

    Stop the change that would break production

    Change Preflight is one gate before production for everything a change touches. Migration Preflight shows what your ECC configuration and custom code become in the target release — before cutover.

    • Transports and software collections
    • ABAP code and Clean Core
    • APIs, IDocs and change pointers
    • Custom fields and extensions
    • Output determination and forms
    • Migration artifacts: configuration and custom code
    • Authorizations (IAM)
    How Prevent works

  • Explain

    Find the first cause, not a thousand symptoms

    When something already broke, you need the cause that started it — not a longer error list. ERP Preflight traces findings back to the exact source rows and separates primary causes from their consequences.

    • Findings on the same SAP object grouped under one root-cause candidate
    • Warehouse telegram replay: the first causal divergence in MFS logs and the minimal sequence that reproduces it
    • SAP error logs (e.g. migration or application logs) reduced to the few primary causes, with affected objects, source rows and a fix order
    How Explain works

  • Govern

    Decide with evidence — for people and AI agents

    A vendor-neutral gate for releases and AI coding agents: approve, request changes or block. Every decision carries the findings, rule versions and artifact hashes it was based on.

    • Gate decisions for agent proposals and releases, with separation of duties
    • Reports and audit history that reference the same evidence
    • Access for agents through the REST API and an MCP server
    How Govern works

Products

Three products on one platform

Each product uses the same ingestion, evidence model, findings workflow and reports. Choose the job you need done — the engines underneath are selected for you.

  • Prevent · Govern

    ERP Preflight Change Gate

    One gate before production for transports, code, interfaces, extensions, forms, migration artifacts and authorizations. One verdict per change — approve, request changes or block — with the evidence behind it.

    You provide
    Transport lists, ABAP sources, API specifications, configuration and form exports
  • Prevent · Explain

    ERP Preflight Migration Intelligence

    What your ECC configuration, custom code and interfaces become in S/4HANA Cloud: configuration without a cloud counterpart, obsolete transactions, custom code to remediate and fit-to-standard gaps.

    You provide
    IMG/SPRO exports, custom code, ATC and readiness check results
  • Explain

    ERP Preflight MFS BlackBox

    Explains warehouse automation incidents from Material Flow System telegram logs: the first causal divergence between warehouse management and automation, and the minimal telegram sequence that reproduces it.

    You provide
    MFS telegram logs

Example gate verdict

One decision for the whole change

A change rarely stays in one domain. The gate checks everything it touches and returns one decision, with the evidence for every part of it.

Illustration with sample dataExample of a gate verdict with illustrative data: one change checked across seven domains. A blocker in ABAP and Clean Core and two findings to review in APIs and authorizations lead to the decision Block.
Change
Material status update, transport bundle for production
Target release
SAP S/4HANA Cloud Public Edition 2408

Result per domain

  • TransportsPassNo finding
  • ABAP & Clean CoreBlockerCLEAN_CORE_DIRECT_DB_MUTATIONDirect write to an SAP standard tablezcl_material_status.clas.abap:42
  • APIs & interfacesReviewAPI_BREAKING_REQUIRED_PROPERTY_ADDEDNew required propertymaterial_status_srv.edmx:118
  • Custom fields & extensionsPassNo finding
  • Output & formsPassNo finding
  • Migration artifactsNot affectedNot part of this change
  • Authorizations (IAM)ReviewFIORI_AUTH_OBJECT_MISSINGAuthorization check failed (SU53)su53_trace.txt:7

Decision:

Block

1 blocker to resolve, 2 findings to review

Possible decisions

  • Approve
  • Request changes
  • Block (decision for this change)

Rule versions and artifact hashes are recorded with the verdict.

Artifact-first

Artifacts, not passwords

Start with zero SAP access: give us the exports you already have, not your SAP password. Deepen with a connector or a local agent later — only if and when you want to.

  1. 1. Start with exports

    Configuration and decision table exports, ABAP sources, transport lists, API specifications, ATC and readiness check results, logs. No system connection and no installation for the first result.

  2. 2. Checked before any rule runs

    Files are identified by their content, scanned for malware and unpacked within strict limits. Secrets are redacted before a snippet is stored as evidence.

  3. 3. Deepen when it pays off

    Connectors start read-only and need an explicit permission step before any write. For private networks, a local agent (in pilot) collects and redacts exports on your side and only calls out.

Which exports each check readsHow the local agent works

Deterministic by design

Same input, same result

A gate is only useful if it gives the same answer twice. Findings come from deterministic parsers and versioned rules, and every result can be traced back to the byte it came from.

  • Fixed rule versions: every finding records the engine version, rule version and knowledge snapshot it was produced with
  • SHA-256 hash of every analysed artifact, with file, line, column and snippet for each finding
  • Explicit confidence classes from VERIFIED to UNKNOWN — AI can explain, but never raises a finding above INFERRED
  • Tamper-evident audit history: a verifiable hash chain per organization
  • Predictions checked against what SAP actually did: upload the SAP log afterwards and see precision and recall per rule
Which checks apply to which release

The evidence chain of a finding

  1. ArtifactStored in your tenant with its SHA-256 hash.
  2. RuleDeterministic, versioned, with a finding code.
  3. FindingSeverity, confidence class, file, line and snippet.
  4. ReportEvery export references the same evidence.

Transparency

Under the hood: domain engines

You do not need to know which engine answers your question: a preflight routes your artifacts to the engines of the affected domains. For transparency, this is what runs underneath — grouped by area, each with its rules, accepted inputs and remediation guidance.

All solution areasBrowse the engine reference

Security

Built for customer artifacts from day one

SAP exports contain configuration, code and sometimes personal data. These controls are implemented in the platform today — not on a roadmap.

  • Row-level security per tenant

    Every tenant table is protected by forced PostgreSQL row-level security, enforced by the database for each query.

  • Malware scanning with ClamAV

    Uploads are identified by file signature, scanned by ClamAV and quarantined when infected. Archives are unpacked with limits on size, ratio, nesting and paths.

  • Secret redaction

    Passwords, keys and tokens are redacted before a code snippet is stored as evidence.

  • Tamper-evident evidence

    Findings reference the SHA-256 hash of the analysed artifact, so every result can be verified against the original file.

  • Tenant-scoped storage

    Artifacts are stored under a tenant- and project-specific path; download links expire after 15 minutes at most.

  • Account protection

    Argon2id password hashing, optional two-factor authentication, single sign-on and revocable sessions.

Security detailsTrust Center

Open by design

Open interfaces

Use the results where your team already works: a documented REST API with OpenAPI description, webhooks, a Model Context Protocol (MCP) server for AI agents, report exports and work item sync to delivery tools such as Jira and SAP Cloud ALM.

How ERP Preflight is organised

The three pillars, the three products and how the domain engines fit underneath them.

Read the overview

Documentation

Engine reference, evidence model, API and MCP integration.

Documentation

From the knowledge base

Reviewed explanations of the SAP topics behind common change failures.

Open the knowledge base

Pricing

Plans for single projects and whole landscapes

Start with a free sandbox and move to a plan when your programme needs more projects and analyses.

  • Free sandbox for evaluating the engines on your own exports
  • Paid plans from €29 per month
See pricingStart free

FAQ

Frequently asked questions

Do I need to connect ERP Preflight to my SAP system?

No. The engines analyse exported artifacts that you upload, such as configuration exports, code and logs. No system connection is required to run a preflight. A connector or the local agent can be added later if you want to automate the collection.

Do I need to know which engine to run?

No. You start a preflight for a change, a migration or an incident and upload its artifacts; the platform routes them to the engines of the affected domains. The engines are documented for transparency, not as a menu you have to choose from.

How do Change Gate, Migration Intelligence and MFS BlackBox differ?

They are three products on the same platform. Change Gate checks a change before production and returns one verdict across the domains it touches. Migration Intelligence assesses what your ECC configuration and custom code become in S/4HANA Cloud. MFS BlackBox explains warehouse automation incidents from telegram logs.

Does AI decide which findings are reported?

No. Findings come from deterministic parsers and rules. AI is only used for optional explanations and its contributions are capped at the INFERRED confidence class.

Which SAP releases are supported?

Each engine declares its target releases. The public release matrix lists them per engine.

Is ERP Preflight an SAP product?

No. ERP Preflight is an independent product and is not affiliated with, endorsed or sponsored by SAP SE.

Find out what will break — before go-live

Create a workspace, upload your first export and review evidence-backed findings.

Run a PreflightExplore free tools
ERP Preflight — Know what will break before production does