Your ERP stays the system of record. Nothing is written without a person approving it.

AiPEX connects to your ERP through a documented set of read-only views that form a stable interface between the ERP and the application. Analysis, dashboards and every screen a buyer works in are served from that read path.

Because the read path cannot write, nothing a user does while reviewing, sorting, filtering or asking questions can alter an ERP record.

Connection

IBM i Access ODBC driver from the AiPEX application server to Db2 for i.

Interface

A documented set of read-only SQL views, not direct table access from the UI.

Typical data

Sites and warehouses, items and inventory balances, vendors and contacts, buyers and planners, purchase orders, manufacturing orders and customer orders.

User machines

Nothing is installed on individual PCs. Users reach AiPEX through a browser.

Reading and writing are deliberately separate systems, and the separation is the control.

When someone acts on a recommendation in AiPEX, that action does not go to your ERP. It enters an approval queue. A named person reviews it there and either approves or rejects it. Only approved changes are written back.

Every written change carries an audit trail recording what changed, who approved it and when. That means an ERP update made through AiPEX is more traceable than the same update keyed directly into a green screen, where the only record is the changed value itself.

Your ERP stays the system of record. AiPEX holds no decisions outside it, so there is no shadow system to reconcile.

Default behaviour

No change is written without a human approval step.

Audit trail

What changed, who approved it, and when — retained for every written change.

Rejected changes

Never reach the ERP. The recommendation stays in AiPEX.

Most manufacturers run AiPEX on a Windows VM inside their own network, close to the IBM i. For customers who would rather not manage an application server, AiPEX can be hosted in AWS instead. The software and functionality are the same either way.

Containerized deployment is supported for teams who prefer that architecture.

On-premise

A Windows Server VM inside your network. Your data never leaves your environment except as described in section 04.

Hosted

AiPEX-managed hosting in AWS, for customers who prefer not to run the application server themselves.

Containerized

Supported for customers standardised on containers.

Government cloud

For customers with government or defense security requirements, AWS Bedrock/GovCloud can be evaluated as part of the deployment architecture.

In an on-premise deployment with AI features switched off, nothing does. AiPEX runs inside your network against your IBM i, and needs no outbound connection at all.

With AI features enabled, AiPEX needs outbound HTTPS to a large language model, which runs through Anthropic or AWS Bedrock. Your ERP database is not copied or uploaded. For each request, AiPEX sends only the specific information that request needs in order to be answered.

All core AiPEX functionality continues to work with AI disabled. Dashboards, workbenches, planning screens and Report Writer do not depend on it, so declining AI is a supported configuration rather than a degraded one.

AI disabled

No outbound connection required. Nothing leaves your network.

AI enabled

Outbound HTTPS only, to Anthropic or AWS Bedrock.

What is sent

Only the information a specific request requires — never a copy of the ERP database.

AiMEE's access

AiMEE's tools operate through the same controlled, read-only data layer the rest of the application uses. The assistant cannot write to your ERP.

AiPEX signs users in with the Microsoft account they already have, so access is granted and revoked in your directory rather than in a separate AiPEX user list. There is no additional password for your team to manage or for you to clean up when someone leaves.

Microsoft GCC High is supported for defense and aerospace customers.

Single sign-on

Microsoft single sign-on. Access follows your existing directory.

GCC High

Supported for customers on Microsoft's government cloud.

Licensing

AiPEX is not licensed or sized by user count, so security posture never has to trade against seat cost.

A typical on-premise installation needs the following. Most teams have it provisioned in an afternoon.

Application server

A Windows Server VM, roughly 4 vCPU, 16 GB RAM minimum and 50 GB of disk.

Database

SQL Server 2019 or newer for AiPEX application data. SQL Server Express is sufficient for many installations.

Driver

IBM i Access ODBC driver.

ERP account

An IBM i user profile for the AiPEX connection.

Network

Browser access to the AiPEX application, plus optional outbound HTTPS if AI features are enabled.

Stack

C#/.NET server, Angular/TypeScript interface, SQL views over Db2 for i. No Java dependency.

Something here your policy does not cover?

Send the question. If the answer is no, we will say so — an evaluation that stalls three months in over something we could have told you today helps neither of us.