PORTWARE AI WORK CONTROL
Every AI At Work, Under Your Control.
Claude Code, Codex, Cursor and PORTWARE Cowork work on your code, PLC programs, CAD, ECAD and documents. PORTWARE ties every session to its task, runs it with the user's own rights, stops it at the gates you set and keeps a record anyone with rights can verify.
The approval inbox in the demo: a change under a protected path and an acceptance review wait for a person, next to the PLM signatures.
HOW IT WORKS
From The Task To Acceptance, On One Record.
-
Start On The Task
The session opens on a ready task: priority, a date, a requirement and its acceptance criteria. The task carries the prompt.
-
Report As It Works
Every step, changed file, commit and test lands on the task's timeline, written so a person can read it.
-
Stop At The Gate
A protected path, an exceeded budget or a release stops the work and waits in one approval inbox, with the reason and the evidence.
-
Accepted By A Person
A reviewer ticks the acceptance list and approves; the person who did the work cannot approve it. Then the task closes.
WHAT IT CONTROLS
Rules Set By The Company, Not By The Client.
Each project gets its rules once; every AI client that connects follows them.
Your Own Rights
Every AI client works in PORTWARE as the person who connected it, with exactly that person's access.
Approval Before Writing
Changes wait for the user's confirmation; invoices, payments and approvals wait for a decision inside PORTWARE.
Protected Paths
Safety firmware, a bootloader or any path you name: a change there stops the session until someone decides.
Separation Of Duties
The person who started or did the work does not approve its gate.
A Budget Per Project
Each project has a monthly AI budget; when it runs out, new work waits for a decision.
A Record That Proves Itself
Each session is a hash-chained timeline: who, when, through which client and model; anyone with rights can verify it.
AI Marks On Revisions
PLM, CAD, ECAD and Office revisions an AI touched carry its mark and its session.
Company Sign-In And Key Vault
AI clients sign in with the company account; provider keys stay in PORTWARE's vault, never on a laptop.
A Control Tower
Running now, waiting for you, approvals, cost, accepted and reworked: one board, read from the same record.
ENABLED PER INSTALLATION
A Workspace In The Browser
Where it is switched on, a session starts from the task in an isolated workspace in the browser: nothing to install, no provider key inside, no network but PORTWARE's gateway.
COMPARISON
Not Only Code. The Whole Engineering Record.
Other kinds of products govern code in one place, AI systems on paper or one vendor's data. PORTWARE ties the task, its requirement, its approval and the AI's change to one record in the business system.
| Question | Coding-agent boards | AI governance platforms | A PLM vendor's own agent | PORTWARE AI Work Control |
|---|---|---|---|---|
| Where the AI works | Code in one forge | Inventories of models and policies | Its own PLM data | Code, PLC, CAD, ECAD, PLM and documents |
| What the work hangs on | A pull request | An AI system register | A BOM change | The task, its requirement and its acceptance list |
| Which AI clients | Agents on that forge | Through connectors | The vendor's own agent | Claude Code, Codex, Cursor, PORTWARE Cowork and other MCP clients |
| Whose rights | Repository permissions | Policy roles | PLM roles | The user's own rights in the business system |
| Who approves | Pull request review | Policy workflows | Confirmation of BOM updates | Protected paths, separation of duties, budget and acceptance, in one inbox |
Kinds of products, not products: drawn from their public descriptions, November 2026.
TRUST PACK
Measured, Not Promised.
The architecture in one line: AI clients reach PORTWARE only through its own connector, as the user, and every report enters a chained record. These are the figures and the limits we measured.
Measured On The Bench
- 2,500 session reports from 500 parallel sessions: 0 errors, 95 % answered within 108 ms.
- 200 of 200 session chains verified after the load test.
- Control tower figures in under one second, with a query count that stays fixed as data grows.
Limits We Accept
- A budget can be passed by the calls already running during one heartbeat, about 15 seconds.
- A client that stays silent for 120 minutes is closed and counted as failed.
PORTWARE Is Built With It
Our own development runs under AI Work Control. Its first day, from the control tower:
- 50sessions on the first day
- 69 %accepted
- 12 %reworked
- 106 minaverage session
14 to 15 November 2026, read from the control tower on 15 November 2026. Failed sessions in that period are silent clients closed after 120 minutes.
Built to support human oversight and record-keeping. PORTWARE does not claim certification under any AI regulation or standard.
Let's discuss your business.
Tell us how your organisation works today, and we will present PORTWARE through your own processes.