One engine, a connector for each system.
Boundlane Studio builds automations, and Boundlane Control runs them under policy. Gateway is the second door: the path your people’s own assistants take to your business systems, controlled.
One engine governs every system: each person’s own credential for the system, role-based policy, approvals bound to the exact change, a hash-chained audit trail and entitlement reports. A connector adapts the engine to each system. Oracle Fusion Cloud ERP is the first certified connector, and most of this page describes it.
Gateway works with any MCP client, including an agent your team built. It uses the same Boundlane account, sign-on, approvals inbox, audit chain and bill as Studio and Control.
On Oracle Fusion, each person keeps their own permissions.
Each person connects their own Oracle account once, through Oracle’s own sign-in. The connector cell checks that the Oracle identity matches the person’s email, and that the sign-in finishes in the browser that started it.
From then on, Oracle enforces that person’s roles and data security on every call. The effective right is the intersection of what Oracle permits and what your policy grants, so Gateway can narrow a person’s access and cannot widen it.
Your policy decides which fields and organisations.
Access groups map to Boundlane business roles. Each Oracle operation is granted with explicit fields, business units, legal entities and ledgers, finders, page sizes and daily row allowances. The scope is sent to Oracle with the query, and every returned row is checked again.
Payment, bank, payroll and approval operations are blocked. Removing a person’s Boundlane role removes their access on the next call.
A change needs a second person.
An assistant can only propose an exact change. A different person who holds an approver role decides it in Boundlane Approvals, and the decision is bound to that exact proposal and its digest. The requester then runs it once.
Oracle’s record version is checked before the change applies. On a live Oracle test environment, Oracle refused a change sent with a stale version and changed nothing. After a change, the record is read back. If the outcome is uncertain, nothing is retried: the read-back tells the person what happened.
Each one goes through a proposal and a second person’s decision before it reaches Oracle.
Boundlane holds the people. The cell holds the credentials.
Boundlane is the control plane: people, business roles, the MCP front door your assistants connect to, the approvals inbox and your tenant’s audit chain. Each connector cell is a separate deployment of the engine for one customer. On Oracle Fusion, it holds each person’s Oracle token, applies the data policy and calls Oracle’s published REST APIs.
Cells run in AWS in the EU, in Stockholm (eu-north-1) by default. Boundlane signs a short-lived context token, valid for at most five minutes, for every call to a cell. The person’s assistant token never reaches the cell, and their credential for the system never leaves it.
Tool results return through Boundlane’s MCP front door on their way to the assistant. Boundlane itself runs with the providers and in the locations on the subprocessor page.
No language model sits in Gateway’s data path. Discovery and policy use rules, not a second AI provider.
Evidence on both sides.
Every call is recorded before it reaches Oracle. Each cell keeps a hash-chained audit log, and Boundlane records its head in your tenant’s own audit chain at least every 30 minutes, so a rewrite of either is detectable. Cell archives are configured with S3 Object Lock in compliance mode.
Audit records hold identifiers, decisions and hashes, never Oracle row data. For access reviews, an entitlement report shows what each group and person could do under any past policy revision.
What the Oracle Fusion connector covers.
On 6 November 2026, 39 Oracle operations pass Boundlane’s activation gate. Each has a reviewed usage contract and probe evidence from a live Oracle Fusion test environment no older than 30 days, and the contracts are re-certified after each of Oracle’s quarterly releases.
AP invoices, invoice lines, distributions, holds and payments; purchase orders; suppliers; customer receipts; ledger balances; journal batches, journals and journal lines; currency rates; and reference lists such as ledgers, periods, value sets and payment terms.
An invoice’s description, placing an invoice hold and releasing one.
Receivables invoices and credit memos are not certified on that date.
Onboarding uses your own chart of accounts, as JSON, CSV or an XLSX template, verified against Oracle’s live value sets, together with your resource schemas and organisation references. An assistant can then explain any account string segment by segment, with each segment’s Oracle attribute and value list.
Built on Oracle’s published APIs.
Oracle’s service descriptions of 20 October 2026 allow partner-developed agents that work through Oracle’s published APIs and governance controls. The connector uses only Oracle’s published REST APIs and each person’s own Oracle token. It respects Oracle’s rate limits: it pauses when Oracle asks it to slow down, and it never retries automatically.
Any system with a remote MCP server.
The MCP connector brings the same engine to any business system that publishes a remote MCP server, such as an ERP, HCM, CRM, procurement or service platform: per-person OAuth to the system, per-tool grants with argument limits, approvals for changes and the same audit chain.
As of 6 November 2026, it is proven end to end against a reference system in Boundlane’s test harness. It is not yet certified with a specific vendor’s server. More certified connectors follow design partner demand.
Open to design partners.
Gateway is in a design partner programme. A pilot is quoted for your company and starts with your own connector cell for the system you choose. On Oracle Fusion, that includes your chart of accounts and the business units, legal entities and ledgers you choose.
Design partners are the first to run Gateway on their own systems, with their own people and their own assistants. They have a direct say in what we build next.