From one sentence to a reviewed app

How NgageCode turns a description into a web and phone app on IBM Maximo, IFS or SAP, and who checks it before your teams use it.

The four stages of every build

Every app goes through the same four stages, from your sentence to your teams’ browsers and phones.

  1. Describe

    You, in plain words

    Say what the app is for and who uses it. NgageCode asks a question only when it needs one.

  2. Generate

    NgageCode, on your ERP

    It finds the right records and actions, then builds the screens and the calls to your ERP.

  3. Review

    A person, before merge

    A person reads the code before it merges. Every commit is scanned for secrets.

  4. Ship

    Your teams, on web and phone

    Technicians open it on a phone at the site. Supervisors approve from a desk.

A requisition app, built on IFS

What NgageCode looked up, the files it wrote and the checks before merge, in an illustrative build on an IFS test environment.

The tool names are NgageCode’s IFS Cloud tools. Files and results are a shortened sample.

The checks on every app it writes

Each check runs on every app, and any finding blocks the merge. Read about security

CheckWhenWhat it means
Human reviewBefore every mergeA person reviews all AI-written code before it merges.
Secret scanning and static analysisOn every commitAny finding blocks the merge.
Production credentialsAlwaysNo coding tool ever holds production ERP credentials.

Which ERPs an app can use, and how

IBM Maximo, IFS and SAP are ready today. For any other application, including a homegrown one, we teach Ngage how it works in weeks.

  • IBM MaximoReady today
  • IFSReady today
  • SAPReady today
  • Any other applicationBuilt in weeksHomegrown or specialist software. We teach Ngage how it works in weeks.
Reads and writes
Through each ERP’s official interfaces. The database is never touched.
Permissions
Every call runs as the signed-in user, never a shared service account.
Two ERPs, one app
One app can read the asset in IFS and the cost in SAP.
On IFS
Nothing is installed in IFS. Mandatory fields and validations still fire.

See the IFS Cloud tools

Questions about how it works

Do we need to know the ERP’s data model?

No. You describe the app in plain words. NgageCode finds the entities, key fields and actions it needs and writes the calls.

How does NgageCode know our ERP?

It works from how IBM Maximo, IFS and SAP are structured: their entities, fields, enumerations and actions. On IFS Cloud it uses 16 tools for metadata discovery, records, actions and documentation search. For any other application, including a homegrown one, we teach Ngage how it works in weeks.

Does it ask questions before it builds?

When it needs an answer, such as who approves a request. Otherwise it works from your sentence and the ERP’s structure.

What does a build need from us to start?

One sentence about the app, the ERP it runs on and access to a test environment. We build it with you on your scenario, in a safe test setup.

Start with one app your team needs

Describe it in a sentence. We build it with you on your scenario, in a safe test setup.