What is the enterprise stack?
The architecture practice · Checked 12 Oct 2026
The enterprise stack is the board we build every workload on. It has five layers. Every workload, from a portal to an AI agent, plugs into the same sockets: one sign-in, one gateway that checks and records every action, your business terms, and one record. Each new workload reuses what the last one built, so the fifth costs far less than the first.
Every workload we build plugs into the board. We don't build a second way into your systems, because that's where audits fail and agents go wrong.
Chapter 1 · the problemWithout a board, every new system adds its own connections
Most companies add software one project at a time. Each project wires itself to the systems it needs, with its own sign-in, its own error handling, and its own log. Every system you add makes the next one more expensive, and an AI agent ends up with many ways in instead of one.
Without the board
With the board
fig 1 · tangle-vs-boardChapter 2 · the ideaWe lay one board first, and everything plugs into it
The board has five layers, and each one has one job. People reach the work through one sign-in. The work happens in workspaces, portals, apps, and agents. The control plane in the middle decides who may act and what they may touch, and it records every action. Under it sit one customer record and the systems you already run.
fig 2 · the-boardChapter 3 · how a workload plugs inA new workload needs four sockets, and nothing else
Before we build a portal, an app, or an agent, we check which sockets it needs: one sign-in, the gateway, your business terms, and the record. It never gets a sign-in of its own or a private way into your data.
fig 3 · plug-inChapter 4 · what it savesThe next workload starts where the last one stopped
The first workload builds the vocabulary, the gateway rules, the correction log, and the tools. The second adds a few terms. By the fifth, a workload mostly brings tools. So we start small and grow on the same board:
- First 90 days: one workflow, with one gateway and one record.
- The next two quarters: one department. More processes reuse what the first one built.
- After that: the whole business. New systems plug into the board, not around it.
fig 4 · reuseChapter 5 · one action, end to endEvery action crosses the control plane once, and leaves a record
- A request arrives, for example a broker's email with a submission.
- It's matched to your business terms, so the agent knows what a submission is.
- Sensitive data is held back. Only what the agent needs reaches the model.
- The agent plans and picks the tools it needs.
- The control plane checks each call and stops the agent at its limit.
- The change lands in your system, with its record, so you can prove who did what.
fig 5 · one-actionChapter 6 · where it goes wrongFive ways this goes wrong, and how we avoid them
| The mistake | What we do instead |
|---|---|
| Starting with the agents | We draw the board first. Without it, agents guess. |
| Building what a vendor already sells | We buy the parts that are a commodity. |
| Giving an agent a second way in | Every action goes through the control plane. |
| Trusting what an agent reads | Limits live in the control plane, not in a prompt. |
| Funding an agent for a query | If a report answers it, we build the report. |
Chapter 7 · what you keepThe board sits on what you already run
| What you already have | What happens to it |
|---|---|
| An integration platform (an iPaaS, an ESB, or API management) | It stays and keeps the transport, mappings, and retries. The control plane sits in front of it. |
| The applications you subscribe to | They stay. Around three dozen is normal. Each one's rate limits and seat pricing decide how much an agent can do, so we price that before the pilot. |
| Your core system | It stays in the bottom layer. Workloads reach it only through the control plane. |
| Your business terms | We write down only what one workflow touches, in weeks, not a company-wide program. |
Questions architects ask
Do we have to replace our core system?
No. Your core stays in the bottom layer, and workloads reach it only through the control plane.
Does the board replace our integration platform?
No. The control plane sits in front of it and adds what it was never built to do: an identity per agent, limits read from your business terms, and one record per action.
How big is the first step?
One workflow, end to end, in production with real users on real data. A pilot that never leaves a sandbox proves nothing about your controls.
What about the agents our software vendors ship?
They become clients like any other. They reach your other systems through the same control plane, under their own identity, and write to the same record.