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
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.
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
Read it the way a request travels : down from the screen to the substrate, and back up through the wall.
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.
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.
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.
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.
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
CRM
Accounts · pipeline · contacts
Data + files
Warehouse · documents · object store
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
Governed context enters the cell sanitized — prompt-injection screened, fields masked to policy.
Gate 02 · Out
Every result is screened for hallucination and data loss before it leaves. Blocked = withheld, and recorded as an incident.
Gate 03 · Out ↑
DLP on the way up to the product surface — what reaches a screen has crossed two gates.
Gate 04 · ⇄
Substrate I/O both ways screened — an agent asks the deterministic engines, never the raw system.
Gate 05 · In
Work enters the cell as a scoped, short-lived task with a scoped token — not a standing session.
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
One pass of a governed request through the stack — the loop every Maxor feature is built on.
01
Policy-filtered, masked to the reader, from your systems — never trusted raw.
02
Sanitized. The contained agents act on it with the substrate's engines through Gate 04.
03
Screened for hallucination and data loss. A failure is withheld and logged, not shipped.
04
Governed context updates. The loop closes — and every step is replayable from the log.
What we distribute in Canada, placed on the layer it actually runs on — with its real status.
L1 · Substrate · Production
The deterministic engine substrate — router, 4,200+ engines, grounding screen. Every product below consumes it.
HeisenL2 + L3 · Control plane · Production
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 · Early Access
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 · Early Access
The wall and its five gates, with Horizon — the deterministic firewall — behind them. Also deployable standalone in front of any model.
HullSmithStandalone · consumes the cascade · Live
The writing-quality grader and CI gate. Grounded locally at $0 first, escalated to the Heisen cascade only on request — the two-brain invariant.
slopGradeEngineering division · distributed in Canada
Multi-crane simulation and 3D clash detection for the lifts that can't fail — the engineering division the same substrate powers.
CRANEbee®The same stack, three postures. Start hosted ; bring it in-house the day your security review or your data-residency rule requires it.
Cloud
Fully managed on Canadian infrastructure. The fastest way to run the stack — nothing to provision.
Self-hosted
Your keys, your infrastructure, your control plane. Data never leaves your network.
Air-gapped
No telemetry, no phone-home. The substrate does not need the internet to be deterministic.
A G1 qualification call is free. Bring your security questionnaire ; we answer it layer by layer, and put the answers in writing.
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.