Your ERP’s rules still apply

Each app sees and does only what its user may. A person reviews all AI-written code before it merges.

No AI-written code merges unreviewed

Secret scanning and static analysis run on every commit, and any finding blocks the merge.

NgageCode Merge blocked

Parts request app: add a stock check from SAP

Waiting for review

3 files changed

  • src/api/stock.ts+18
  • src/screens/NewRequest.tsx+32 -4
  • src/screens/Requests.tsx+6 -1
  1. Secret scan No keys or tokens in the change Passed
  2. Static analysis No findings Passed
  3. Review by a person Required before merge Waiting
Merge stays blocked until a person approves.
Illustrative example. The values are samples.

Apps act as the signed-in user

An app never has more access than the person using it.

Their own ERP permissions
Every call runs as the signed-in user, never a shared service account.
Their own sign-in
Single sign-on through Microsoft Entra ID or OIDC. Your MFA still applies.
Official interfaces only
Apps read and write through each ERP’s official interfaces. The database is never touched.
You choose which writes need approval
A write you mark waits for a person to approve it before it runs.

No coding tool ever holds production ERP credentials

NgageCode builds against your test environment. Production access stays with your people.

What we have verified on IFS

On SAP and IBM Maximo, apps use each ERP’s official interfaces.

Installed in IFS
Nothing. No schema changes, no customisation.
Reads
Through IFS OData projections.
Writes
Through official OData actions.
Business rules
Mandatory fields, validations and state checks still fire.
Bad requests
IFS rejects invalid values, sites and unauthorised operations, verified in testing.

Questions a security review asks

Who owns the apps?

You do. The code is yours.

Where do the models run?

Ngage enterprise deployments use Google Cloud Vertex AI, with zero data retention configured.

Can we pick the region?

Yes. You choose it.

Bring your security review

We go through each point with your security team, one by one.

What a review covers

  • Sign-in and permissions
  • The ERP interfaces each app calls
  • The checks before code merges
  • Which writes wait for approval