Five layers.
Five gates.
No sixth path.
This is the stack every Maxor system runs on — from the machine it sits on to the screen your team uses. Every autonomous agent works inside a containment cell and can only reach your data, your products or your systems through a wall with five numbered gates. Read it in four minutes ; verify it in a G1 call.
The deployment schematic
Open full screenFull 1920 px board — opens in a new tab. Swipe to pan, pinch to zoom.
Walk the stack with the engineer who runs it.
A G1 qualification call is free. Bring your security questionnaire ; we answer it layer by layer, and put the answers in writing.
01 · In writing
Layer-by-layer answers to your security questionnaire — not a slide deck.
02 · Three postures
Canadian-resident cloud, your perimeter, or a disconnected site. Same stack.
03 · Honest figures
v11 router, 55M parameters, 4,200+ deterministic engines. A model is the fallback, never the path.
04 · No training loop
No customer data in any training loop. Agents propose ; a human approves the write.
Top to bottom, what runs where.
Read it the way a request travels : down from the screen to the substrate, and back up through the wall.
5
layers, sovereign hardware to product surface
L0 → L3
5
gates on the boundary — and no sixth path
HullSmith · 01–05
4,200+
deterministic engines under every answer
counted live in the substrate
3
deployment postures — cloud, self-hosted, air-gap
Canadian-resident cloud by default
Product surface
The screen your team works in — records, workflows, agent tasks. Nothing here writes to your data directly ; every write is a policy-checked proposal that crossed the wall.
MaxorConnect — the agentic control plane. CRM-first, twenty-some modules, one ontology.
Containment + boundary
Every autonomous agent — ours, a third party's, yours — runs inside an isolation cell with no direct external socket. The cell's only exit is a wall with five numbered gates. Horizon, the deterministic firewall, secures the confined agents : syscalls deny-default, lateral movement blocked, tools scoped, egress through a gate only.
TensorYard — the cell : a regulated number computed by a pure engine, sealed in a signed receipt, replayed bit-for-bit. HullSmith — the wall and its gates, with Horizon behind them.
Control + data plane
Your business typed once as an ontology. Governed context — a single source of truth with field-level masked reads. An immutable, append-only audit + lineage log. Identity and policy enforced per call, deny-default. The agent runtime lives here too, and never writes a table directly : its terminal effect is a proposal a human approves.
MaxorConnect — governance plane · the Heisen agent runtime — execution plane, $0-first cost router, hard per-job cap.
Deterministic substrate
Heisen Core routes every computation to a deterministic engine : a home-trained v11 router (55M parameters, 98.6 % accuracy, under a millisecond) in front of 4,200+ provable engines. A grounding screen ends every run with a verdict — ship, or flag. A language model is an escalation fallback, never the path.
Heisen — the substrate every product above consumes. Also deployable at the edge, inside a client's production machine.
Sovereign hardware
The machines it runs on. Sub-second, and deployable on-prem or fully air-gapped when your data-residency rule, your regulator or your security review says so.
Yours or ours — Canadian-resident cloud, your own environment, or a disconnected site.
ERP
SAP · Dynamics · Odoo — masked reads only
CRM
Accounts · pipeline · contacts
Warehouse
Analytical reads, masked to the reader
Documents
Object store · classified files
Identity
SSO · per-call RBAC · deny-default
Lineage
Append-only audit, every decision replayable
Five gates. If a change draws a path around the wall, the change is wrong.
Every line entering or leaving the containment cell transits one of these. There is no sixth path — not for our agents, not for a vendor's, not for yours.
Gate 01 · In
Context in
Governed context enters the cell sanitized — prompt-injection screened, fields masked to policy.
PASS · sanitized, field-masked context
BLOCK · prompt-injection or unmasked field
Gate 02 · Out
Results out
Every result is screened for hallucination and data loss before it leaves. Blocked = withheld, and recorded as an incident.
PASS · grounded result, no data loss
BLOCK · hallucination or DLP hit · incident
Gate 03 · Out ↑
Egress to the surface
DLP on the way up to the product surface — what reaches a screen has crossed two gates.
PASS · DLP-clean payload to the screen
BLOCK · residual leak toward L3
Gate 04 · ⇄
Tool call, resolved
Substrate I/O both ways screened — an agent asks the deterministic engines, never the raw system.
PASS · engine call, typed I/O
BLOCK · raw system or unscoped tool
Gate 05 · In
Task dispatch
Work enters the cell as a scoped, short-lived task with a scoped token — not a standing session.
PASS · scoped, short-lived task token
BLOCK · standing session or broad token
Invariant
No contained agent reaches a product, the control plane, the substrate or a client system without crossing HullSmith.
✕ BLOCKED — hallucination or DLP hit — withheld, recorded as an incident
Detect. Act. Verify. Close.
One pass of a governed request through the stack — the loop every Maxor feature is built on.
01
Detect
Governed context assembles the truth
Policy-filtered, masked to the reader, from your systems — never trusted raw.
02
Gate 01 + 04
It enters the cell through Gate 01
Sanitized. The contained agents act on it with the substrate's engines through Gate 04.
03
Gate 02
Results leave only through Gate 02
Screened for hallucination and data loss. A failure is withheld and logged, not shipped.
04
Verify · close
Audit + lineage sign it ; the write is policy-checked
Governed context updates. The loop closes — and every step is replayable from the log.
Every product on one substrate. Nothing bolted on.
What we build and run in Canada, placed on the layer it actually runs on — with its real status.
L1 · Substrate · Production
Heisen
The deterministic engine substrate — router, 4,200+ engines, grounding screen. Every product below consumes it.
HeisenL2 + L3 · Control plane · Production
MaxorConnect
Your business typed once as an ontology ; governed context, audit + lineage, agents under human approval, and the screen your team uses.
MaxorConnectL2.5 · Containment cell · Production
TensorYard
The deterministic-compute authority : a regulated number computed by a pure engine, sealed in a signed receipt, replayed offline by your auditor.
TensorYardL2.5 · Active boundary · Production
HullSmith
The wall and its five gates, with Horizon — the deterministic firewall — behind them. Also deployable standalone in front of any model.
HullSmithStandalone · CI gate · Production
slopGrade
The deterministic CI gate for AI-written code — pass or block on every pull request. Slop and cross-tenant leaks never reach main ; the code stays on your runner, 0 egress.
slopGradeEngineering division · distributed in Canada
CRANEbee®
Multi-crane simulation and 3D clash detection for the lifts that can't fail — the engineering division the same substrate powers.
CRANEbee®Cloud, your perimeter, or a disconnected site.
The same stack, three postures. Start hosted ; bring it in-house the day your security review or your data-residency rule requires it.
Cloud
Canadian-resident, managed
Fully managed on Canadian infrastructure. The fastest way to run the stack — nothing to provision.
- Residency
- Canadian-resident infrastructure, managed by us.
- Network
- Public HTTPS. You bring users, not racks.
- Telemetry
- Ops telemetry only. No customer data in any training loop.
- When
- Fastest G1. Start here unless a rule forbids it.
Self-hosted
Inside your environment
Your keys, your infrastructure, your control plane. Data never leaves your network.
- Residency
- Your region, your network, your keys.
- Network
- Stays inside your perimeter. No data egress.
- Telemetry
- Optional, and never a training loop.
- When
- The day the security review or data-residency rule requires it.
Air-gapped
Fully disconnected
No telemetry, no phone-home. The substrate does not need the internet to be deterministic.
- Residency
- A disconnected site. Yours end to end.
- Network
- No internet. No phone-home. No standing tunnel.
- Telemetry
- None. Determinism does not need a network.
- When
- Classified, OT, or a regulator that forbids a wire.
What your security review will ask — answered by the architecture, not by a promise.
Deny-default identity
Every call authenticates and authorizes. No standing session, no implicit trust across the wall.
Replayable audit
Append-only audit + lineage. Every decision can be replayed bit-for-bit by your auditor.
No training loop
No customer data in any training loop. The substrate is engines plus a 55M router, not your corpus.
Deterministic verdicts
Same input, same answer. A language model is the fallback, never the path.
Human-approved writes
Agents propose. A human approves the write. The surface never writes your tables directly.
Masked ingest
SAP · Dynamics · Odoo — field-masked reads, never raw dumps into the cell.
Signed receipts
A regulated number is a pure-engine result sealed in a signed receipt, replayable offline.
Three postures
Canadian-resident cloud, self-hosted, or air-gapped. Same five layers, same five gates.
Walk the stack with the engineer who runs it.
A G1 qualification call is free. Bring your security questionnaire ; we answer it layer by layer, and put the answers in writing.
The stack, answered
From the bottom up : L0 sovereign hardware ; L1 the Heisen deterministic substrate (a home-trained router in front of 4,200+ provable engines and a grounding screen) ; L2 the control and data plane (governed context, ontology, immutable audit and lineage, identity and policy) ; L2.5 the containment cell and its boundary (TensorYard, HullSmith, Horizon) ; L3 the product surface (MaxorConnect). Every Maxor product runs on this stack.
No. Every autonomous agent — ours, a vendor's or yours — runs inside a containment cell with no direct external socket. It can only reach a product, the control plane, the substrate or a client system through HullSmith, a wall with five numbered gates. If a change draws a path around the wall, the change is wrong ; that is the invariant the stack is built on.
It is withheld and recorded as an incident — never shipped. Gate 02 screens every result for hallucination and data loss before it leaves the cell, and Gate 03 applies data-loss prevention again on the way up to the product surface. A blocked result is a logged event your auditor can query, not a silent drop.
Three postures : a managed cloud on Canadian-resident infrastructure, self-hosted inside your own environment with your keys, or fully air-gapped with no telemetry and no phone-home. The substrate is deterministic without an internet connection, so the offline posture loses nothing.
No customer data enters any training loop. The substrate is deterministic engines plus a small home-trained router ; a language model is only an escalation fallback, and the governed context feeding any agent is masked field by field to the reader's policy before it enters the cell.