NgageCode

What it is

NgageCode is an AI app builder for IFS Cloud, part of the Ngage Suite by EX10. The company's FAQ defines it this way: describe the application, form, report or integration you need, and it generates a complete, IFS-connected app, covering the UI, the APIs and the business logic, "validated against your live IFS data model." It is for IFS teams who want to close the gaps standard IFS leaves to custom development, without a long programming project. It is not a general-purpose builder, since it is built only for IFS. The pages say the product reaches general availability in Summer 2026, with early access open now, and they do not give a company location.

What you build and how

You work from a plain-language request. The homepage calls the idea "Vibe code IFS-integrated apps," and the site breaks the output into four kinds of thing.

Custom IFS apps are complete, full-stack applications: the interface, the OData REST integration and the business logic, generated in one pass. Custom forms are connected data-capture forms with the right field types, dropdowns, date pickers and lookups "pulled straight from your IFS metadata." Custom reports find the right entities, build the OData query and render the output from a request in plain language. Integrations and APIs are correct OData REST calls for reading, writing and running actions, with authentication. Dashboards for live operational data and "industry accelerators," meaning vertical IFS solutions, round out the menu of what you can build.

What separates this from pointing a general AI coding tool at an API is the toolset. The company says "Generic AI coding tools treat IFS like any other API and produce code that does not run." NgageCode has 16 native IFS tools for metadata discovery, live OData create-read-update-delete, bound actions such as release and approve, list-of-values lookups, and semantic search across official IFS documentation. The homepage shows the agent working through them, searching IFS pages, finding a PurchaseRequisition projection and reading an entity's API spec. It discovers your projections, resolves enums and required fields, and handles ETags and concurrency, then validates the result against the data model before it ships. Every call is checked for IFS API accuracy and data-model compliance.

The workflow runs as four steps, ending in "Validate & deploy." The company puts the result as days from prompt to a deployed IFS app, "not quarters," and says the apps are 100% IFS-native. It also says there is no rip-and-replace and no core modification: the apps layer onto your existing IFS Cloud through standard OData REST APIs, so you keep a clean upgrade path.

Security follows IFS. Generated apps authenticate through IFS and honor your IFS permission model, so users only see and do what their IFS access allows. Hosting is either self-hosted or managed, and the company says you can self-host so ERP data stays in your environment. The homepage adds that NgageCode runs in your cloud and your data stays yours.

The use-case pages show where the company expects teams to start:

• Manufacturing, covering shop-floor apps, capture forms and production reports.
• Maintenance and EAM, covering work-order apps, asset forms and maintenance dashboards.
• Field service, covering mobile apps for technicians.
• Supply chain, covering inventory, purchasing and order apps.
• Projects, covering capture apps, progress forms and reports for project and contract work.
• Finance, covering approval apps, capture forms and reports.

The field service page is the most detailed. It offers sample prompts such as building a mobile app for technicians to see today's service tasks and close them, an on-site form to record parts used and time against a work order, and an app to check van stock and request a part from IFS. The apps it describes are a technician day view, on-site capture of work performed, parts used and time, service reports with a customer signature, and parts and stock checks against IFS inventory. On phones, the page says generated apps are responsive and mobile-ready, and points to NgageEase in the Ngage Suite for offline-capable capture.

NgageCode sits alongside other suite products: NgageChat for conversational AI on IFS, NgageFlow for agentic AI workflows on IFS Cloud, NgageEase for no-code AI forms that work on mobile and offline, and NgageConsult, an AI co-pilot for IFS implementation.

Evidence from the pages

The site publishes no prices. Its navigation carries a Pricing entry described as packaging and early access, and the homepage invites you to book a demo, in which the company generates a working app against a real IFS scenario, or reserve early access ahead of general availability in Summer 2026. So the practical route to a number is a conversation with the vendor.

The concrete claims are about capability. There are 16 native IFS tools. Validation happens against your live data model. The apps use standard OData REST APIs and IFS authentication. Hosting can be self-hosted or managed. The pages do not name a compliance standard, a hosting region, a customer count or a founding year.

The company behind it is EX10, which also lists IFS Consulting among its offerings. The footer shows a 2026 copyright and the line that NgageCode is part of the Ngage Suite, an EX10 product line. The company says it is "built by people who have delivered IFS," which is a claim about the team, not a metric. Support is described only as the demo route, with no response times given.

Who it suits and who it does not

NgageCode suits an organization that already runs IFS Cloud and has a backlog of small custom needs: a shop-floor capture form, a technician app, a purchasing approval screen, a live dashboard. The people best placed to use it are those who know their IFS processes well enough to describe them, such as an IFS administrator, a functional consultant or an operations lead. A team that wants delivery in days rather than a multi-quarter custom build is the target the company names.

It does not suit anyone without IFS. The whole value is the IFS tooling, so a team on another ERP or a founder building a consumer product should look at general builders. It is also early. General availability is Summer 2026, so a team planning a critical rollout should confirm what is live today in the demo. And the pages describe no drag-and-drop canvas or template gallery, so this is a prompt-driven builder for people comfortable reviewing generated apps against IFS rather than a point-and-click tool.