How Boundlane maps to an enterprise agentic platform architecture.
An independent reading of the reference architecture published by QuantumBlack, AI by McKinsey, against what Boundlane actually ships — including the layers it does not occupy.
How this maps to an enterprise reference architecture.
QuantumBlack, AI by McKinsey, published one, and it names a structural imbalance behind the gen AI paradox: horizontal solutions are easy to deploy but sit loosely on top of core business processes, which limits their value
, while vertical, workflow-embedded applications can be genuinely transformative
and are the hard ones to scale. Boundlane is horizontal in distribution and purpose-fit in output, so it does not have to take a side of that trade — and the map below marks the layers that are not ours as clearly as the ones that are. An independent reading, not an endorsement, a partnership or an affiliation; the attribution is at the foot of this page.
Where an agent, a workflow or a tool is found and installed.
Agents are not installed on their own: they ship inside a versioned automation, beside the workflow, actions and policy that govern them.
Boundlane Exchange: submission, automated review, a human decision with separation of duties, publication.
58 catalogued business verbs, each carrying its own effect, risk tier and reversal.
The four archetypes an enterprise buys or builds. This row is the customer’s own processes.
Teams across five enterprise functions describe their processes in plain language — conversational rather than canvas-based, with no workflow designer to learn. Business-process automation, not personal productivity.
Developers building on lower-level frameworks and libraries. Boundlane is not a framework and does not replace one.
Designed against the customer's real schema, with live values read from their systems and their own practices taken into account before anything is designed.
An automation is a fixed workflow whose steps may call an agent. Calculations run as fixed rules; judgement is used only where judgement is needed.
Where an agent actually executes.
Durable execution, sandboxed generated code, and credentials and data kept separate per workspace. One runtime among the several an enterprise will run.
Boundlane is a runtime; it is not a replacement for the ones an enterprise already operates.
How anything reaches anything else.
10 vendor systems, generic REST, GraphQL and SQL, and connectors a customer describes for its own APIs. Every call goes only to approved destinations.
Automations reach remote MCP servers only at approved destinations; a tool counts as high-risk until the automation states what it does, and a server that changes its tools is refused. Your people’s assistants reach your business systems through Boundlane Gateway.
All model traffic passes through a zero-retention gateway. The workspace chooses its models, and each run records which model it used.
The same policy decision and the same approved destinations, checked on every redirect as well as the first request. There is no path around them.
What every agentic system above needs and rarely arrives with.
Versioned automations, each fingerprinted at release; Boundlane Exchange for discovery and install.
The 58-verb action catalogue, plus customer-authored connector definitions validated the same way.
A hash-chained, tamper-evident audit trail, a full record of every run, and a record opened before every change to an external system, so an interrupted one is never silent.
Checks before every release, rehearsal that records what a version would do and changes nothing, and replays of a new version against past runs.
OIDC, SAML and SCIM — with business roles kept deliberately distinct from directory groups.
Run history analysed into findings the build agent reads, tests derived from real runs, feedback per run. It changes the automation, not the model.
A policy decision before every action, forbidden actions your administrators define, approval limits, risk levels and gradual rollout.
What the platform stands on.
Boundlane runs on it and does not attempt to be it.
Where the business data already lives.
Boundlane connects to them, reads their real schema and writes back under policy. It is not a system of record and holds no master data.
Spans every layer above rather than sitting in one.
A hash-chained trail whose head can be published outside the platform, and an evidence pack assembled live from the running system.
Personal data redacted before it is recorded, not only when it is displayed; erasure per workspace; a published DPA and subprocessor list.
The model proposes; it never authorises. A forbidden action never runs and no approval releases it, and consequential actions wait for a person.
Rehearsal runs and replays of past cases produce the evidence for widening a rollout, and the reasoning is recorded with the decision.
MarketplaceWhere an agent, a workflow or a tool is found and installed.
3 platform
Where an agent, a workflow or a tool is found and installed.
3 platform
Agents are not installed on their own: they ship inside a versioned automation, beside the workflow, actions and policy that govern them.
Boundlane Exchange: submission, automated review, a human decision with separation of duties, publication.
58 catalogued business verbs, each carrying its own effect, risk tier and reversal.
Agentic systemsThe four archetypes an enterprise buys or builds. This row is the customer’s own processes.
3 customer · 1 outside
The four archetypes an enterprise buys or builds. This row is the customer’s own processes.
3 customer · 1 outside
Teams across five enterprise functions describe their processes in plain language — conversational rather than canvas-based, with no workflow designer to learn. Business-process automation, not personal productivity.
Developers building on lower-level frameworks and libraries. Boundlane is not a framework and does not replace one.
Designed against the customer's real schema, with live values read from their systems and their own practices taken into account before anything is designed.
An automation is a fixed workflow whose steps may call an agent. Calculations run as fixed rules; judgement is used only where judgement is needed.
RuntimesWhere an agent actually executes.
1 platform · 1 outside
Where an agent actually executes.
1 platform · 1 outside
Durable execution, sandboxed generated code, and credentials and data kept separate per workspace. One runtime among the several an enterprise will run.
Boundlane is a runtime; it is not a replacement for the ones an enterprise already operates.
InterfacesHow anything reaches anything else.
4 platform
How anything reaches anything else.
4 platform
10 vendor systems, generic REST, GraphQL and SQL, and connectors a customer describes for its own APIs. Every call goes only to approved destinations.
Automations reach remote MCP servers only at approved destinations; a tool counts as high-risk until the automation states what it does, and a server that changes its tools is refused. Your people’s assistants reach your business systems through Boundlane Gateway.
All model traffic passes through a zero-retention gateway. The workspace chooses its models, and each run records which model it used.
The same policy decision and the same approved destinations, checked on every redirect as well as the first request. There is no path around them.
Shared servicesWhat every agentic system above needs and rarely arrives with.
7 platform
What every agentic system above needs and rarely arrives with.
7 platform
Versioned automations, each fingerprinted at release; Boundlane Exchange for discovery and install.
The 58-verb action catalogue, plus customer-authored connector definitions validated the same way.
A hash-chained, tamper-evident audit trail, a full record of every run, and a record opened before every change to an external system, so an interrupted one is never silent.
Checks before every release, rehearsal that records what a version would do and changes nothing, and replays of a new version against past runs.
OIDC, SAML and SCIM — with business roles kept deliberately distinct from directory groups.
Run history analysed into findings the build agent reads, tests derived from real runs, feedback per run. It changes the automation, not the model.
A policy decision before every action, forbidden actions your administrators define, approval limits, risk levels and gradual rollout.
Cloud and infrastructureWhat the platform stands on.
1 outside
What the platform stands on.
1 outside
Boundlane runs on it and does not attempt to be it.
Systems of recordWhere the business data already lives.
1 outside
Where the business data already lives.
1 outside
Boundlane connects to them, reads their real schema and writes back under policy. It is not a system of record and holds no master data.
GovernanceSpans every layer above rather than sitting in one.
4 platform
Spans every layer above rather than sitting in one.
4 platform
A hash-chained trail whose head can be published outside the platform, and an evidence pack assembled live from the running system.
Personal data redacted before it is recorded, not only when it is displayed; erasure per workspace; a published DPA and subprocessor list.
The model proposes; it never authorises. A forbidden action never runs and no approval releases it, and consequential actions wait for a person.
Rehearsal runs and replays of past cases produce the evidence for widening a rollout, and the reasoning is recorded with the decision.
Boundlane against each of the four agentic-system archetypesThree of the four definitions Boundlane answers. The fourth is somebody else’s, and the definitions are quoted rather than paraphrased.
Enterprise productivity agents
Boundlane builds thisHorizontal applications with low-code interfaces bringing AI agents and workflow automation to the broader organization.
Boundlane is horizontal: it comes with five domain packs — finance, HR operations, IT operations, customer support and revenue operations — and the interface is conversational rather than canvas-based, with no workflow designer to learn. A person describes the process in plain language; nobody assembles nodes on a canvas.
One boundary, stated rather than blurred: this is business-process automation for the organisation, not personal productivity. It does not summarise your inbox or draft your email. It answers the workflow half of this box and not the personal-copilot half. For that half, Boundlane Gateway governs what your people’s own assistants may do in your business systems, without becoming one.
Highly custom agents
Out of scopeAgents built on lower-level software frameworks & libraries that provide developers control and customization to solve the most complex problems.
Outside Boundlane’s scope. That box is developers building on frameworks and libraries, and Boundlane is neither a framework nor a replacement for one. An automation can include generated code, which may calculate anything but can act only through the actions the automation declares, under the same policy as everything else — the opposite of the unconstrained control this archetype is defined by.
Purpose-fit agents
Boundlane builds thisPre-built and custom agentic capabilities, with tight integration into the application's core functionality and tailored based on domain expertise.
Each domain pack carries that function's own approval roles and a recommended list of actions an automation may never take, which the organisation's administrators confirm or change. Every automation is designed against the organisation's real schema, with live picklist values read from its systems rather than assumed, and with the workspace's own practices and rules taken into account before anything is designed.
Workflow automation
Boundlane builds thisSolutions focus on process automation with determined workflows but can increasingly invoke agentic capabilities as optional step.
The closest literal match in the whole diagram. A Boundlane automation is a fixed workflow whose steps may call an agent. Calculations run as fixed rules rather than being left to the model — an automation that sets a limit nothing calculates against is not released, because the model would then be doing the comparison — and judgement is used only where judgement is genuinely needed.
Bring the architecture review.
Every claim on this page is a behaviour of the platform as built rather than a roadmap item. Tell us which one you want to see enforced first.
The reference architecture read on this page is Creating a future-proof enterprise agentic platform architecture, published by QuantumBlack, AI by McKinsey. The article, its diagram and the framing of the gen AI paradox are the authors’ work and remain their copyright. Short quotations above are theirs and are marked as quotations.
This page is an independent reading of that published work by Boundlane. It is not an endorsement, a partnership, an affiliation or a joint publication, and nothing here should be read as McKinsey or QuantumBlack assessing, recommending or validating Boundlane. Their diagram is not reproduced, embedded or re-drawn here; the map above is our own drawing, and the layer names it uses are the ordinary descriptive vocabulary of platform architecture. McKinsey & Company and QuantumBlack are trademarks of their respective owners, and no logos, branding or colours of theirs appear on this page.