Home/Connect/Amazon Q × AS/400 & Mainframe
The agent
The system

Make Amazon Q act in AS/400 & Mainframe — safely

Amazon Q can answer questions about your AS/400 data and trigger terminal-screen transactions — Upware carries out the action, governed, logged, and deterministic, with no API required.

Request a demoSee the platform
Governed by policy & RBAC Full audit trail Outbound-only on-prem bridge No rip-and-replace
The gap

Amazon Q stops at the AS/400 & Mainframe boundary

Amazon Q connects to many apps, but governed, auditable execution in legacy and compliance-heavy systems needs an execution layer purpose-built for it.

Three ways to close it

Only one is governed

Amazon Q alone
Acts in AS/400 & MainframeNo
Governedn/a
Auditedn/a
Custom API glue
Acts in AS/400 & MainframeSort of
GovernedYou build it
AuditedYou build it
Amazon Q + Upware
Acts in AS/400 & MainframeYes
GovernedPolicy + RBAC
AuditedEvery action
In practice

From Q's answer to a mainframe write

A loan officer asks Amazon Q to update a customer's payment arrangement in the core banking system — a green-screen AS/400 application that has never had an API and almost certainly never will. Upware's on-prem bridge replays the exact terminal sequence it learned when a human performed that update: screen navigation, field entry, confirmation. Every keystroke is policy-checked before it lands, and the completed transaction is written to the audit trail with full attribution — agent, user, timestamp, fields changed. Amazon Q reports back a clean confirmation; the core system reflects the change; nothing leaves the network perimeter uncontrolled.

The harness

AI to learn. Deterministic to execute.

Upware learns the process once and encodes it as a mostly-deterministic workflow: system interactions replay exactly, and any LLM steps are wrapped in policy, verification, and audit — so execution stays governed and drift-proof.

O
Observe & Learn
Records the real workflow once, across every system it touches.
G
Generate
Builds the API, data flow, and logic automatically — no integration project.
E
Encapsulate
Wraps it as a governed AI skill over secure MCP or API.
R
Run
Executes deterministically — RBAC, audit, and scale built in.
FAQ

Common questions

Our AS/400 has no API and the vendor is long gone. Can Upware actually work with it?
Yes — this is exactly the case Upware was built for. The platform learns a system by recording a human operator's session: UI events, screen state, data entered, network traffic where available. It generates the integration from that recording, not from documentation or an API spec. If a person can drive the terminal, Upware can encapsulate that workflow as a governed AI skill.
How does Upware enforce SOX and BSA controls when Amazon Q is executing inside a core financial system?
Upware wraps every action in RBAC: the agent can only invoke skills it has been explicitly granted, and each skill is scoped to a specific set of permitted operations. Before any field is written, policy rules are checked. A complete, tamper-evident audit trail records the agent identity, the human who initiated the request, every field touched, and the outcome — the format regulators and internal audit teams expect.
Does Upware send mainframe data to the cloud or to Amazon Q's models?
No. The on-prem bridge runs inside your network perimeter and communicates outbound-only to the Upware engine — no inbound ports, no tunnels. The data used to carry out an action stays on-premises. Amazon Q receives a structured result (a confirmation, a record summary) rather than raw system data, so sensitive fields in the core system are not passed to external models.

Connect Amazon Q to AS/400 & Mainframe

See a governed action go from recorded workflow to live in days.

Request a demo