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 package, beside the workflow, tools 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 probed from their system and their own skill library read before anything is designed.
A package is a deterministic workflow whose nodes may be agents. Arithmetic runs in tools; judgement is used only where judgement is needed.
Where an agent actually executes.
Durable execution, sandboxed tool calls, per-tenant credentials and data. 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 defines by probing its own API. Every call passes an explicit egress allowlist.
Remote Streamable HTTP, JSON-RPC over the egress-guarded fetch. The binding pins a digest over the tool set; drift is refused.
All model traffic through a zero-retention gateway, with a deterministic per-turn router that records its choice and its price.
The same dispatcher and the same allowlist, enforced on redirects as well as the first request. There is no path around it.
What every agentic system above needs and rarely arrives with.
Versioned Automation Packages, pinned by hash; Boundlane Exchange for discovery and install.
The 58-verb action catalogue, plus customer-authored connector definitions validated the same way.
Hash-chained append-only audit with external anchoring, full run traces, a receipt opened before every external write.
The promotion gate, the shadow stage, and backtests that replay a candidate against every past run.
OIDC, SAML and SCIM — with business roles kept deliberately distinct from directory groups.
Run history analysed into findings the build agent reads, evals derived from real runs, feedback per run. It changes the package, not the weights.
The policy dispatcher, forbidden actions that never execute in any stage, risk tiers, staged 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.
PII redacted when recording rather than when displaying, tenant-scoped erasure, a published DPA and subprocessor list.
The model proposes; it never authorises. Forbidden verbs are absent rather than gated, and consequential writes wait for a person.
Shadow runs and backtests produce the evidence a stage advance is argued from, and the argument 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 package, beside the workflow, tools 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 probed from their system and their own skill library read before anything is designed.
A package is a deterministic workflow whose nodes may be agents. Arithmetic runs in tools; 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 tool calls, per-tenant credentials and data. 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 defines by probing its own API. Every call passes an explicit egress allowlist.
Remote Streamable HTTP, JSON-RPC over the egress-guarded fetch. The binding pins a digest over the tool set; drift is refused.
All model traffic through a zero-retention gateway, with a deterministic per-turn router that records its choice and its price.
The same dispatcher and the same allowlist, enforced on redirects as well as the first request. There is no path around it.
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 Automation Packages, pinned by hash; Boundlane Exchange for discovery and install.
The 58-verb action catalogue, plus customer-authored connector definitions validated the same way.
Hash-chained append-only audit with external anchoring, full run traces, a receipt opened before every external write.
The promotion gate, the shadow stage, and backtests that replay a candidate against every past run.
OIDC, SAML and SCIM — with business roles kept deliberately distinct from directory groups.
Run history analysed into findings the build agent reads, evals derived from real runs, feedback per run. It changes the package, not the weights.
The policy dispatcher, forbidden actions that never execute in any stage, risk tiers, staged 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.
PII redacted when recording rather than when displaying, tenant-scoped erasure, a published DPA and subprocessor list.
The model proposes; it never authorises. Forbidden verbs are absent rather than gated, and consequential writes wait for a person.
Shadow runs and backtests produce the evidence a stage advance is argued from, and the argument 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: five domain packs ship today — 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.
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. Generated code does exist inside a package — it may compute anything — but it acts only through injected, declared capabilities, which is 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 its own list of actions an automation may never take. Every automation is designed against the tenant's real schema, with live picklist values probed from their system rather than assumed, and a per-tenant skill library the build agent reads before it designs anything.
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 package is a deterministic workflow whose nodes may be agents. Arithmetic is forced into deterministic tools rather than left to the model — the promotion gate refuses a limit that no rule tool reads, on the grounds that whatever is comparing against it must then be the prompt — and judgement is used only where judgement is genuinely needed.
Bring the architecture review.
Every claim on this page is a behaviour of the running platform 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.