What we own.
What we ship for clients.
Two registers. Systems we built and own — the Maxor Global LLC product line, in production today. Client modernization mandates — delivered under engagement, with client identities protected by default. Selected references below.
6
Systems built and owned end-to-end
220
Invented systems behind the substrate
100%
Canadian-engineered, bilingual-delivered
0
Client identities exposed without written consent
Seven systems. Six built and owned, one distributed.
Six systems built end-to-end by the Maxor team — one architecture, the Maxor Global LLC product line, a substrate of 220 invented systems underneath : Heisen computes, MaxorConnect governs, TensorYard confines, HullSmith guards the boundary, Sentinel and slopGrade consume the same substrate. Plus one distributed system : CRANEbee®, the multi-crane simulation platform we hold exclusive Canadian distribution rights for. Compression-first. Deterministic-first. Sovereign-by-default.
Heisen
The deterministic computing core — router, engines, grounding screen.
Heisen is the substrate every Maxor product runs on. A home-trained neural router (v11, 55M parameters — not an LLM) classifies each query and dispatches it to deterministic computation engines : 4,200+ domain engines plus 68 code-audit engines. Every run ends at a grounding screen with a verdict — ship or flag. A frontier model is the escalation fallback, never the default path. Computations stay auditable to first principles ; cost stays predictable end-to-end.
- 01Deterministic-first — an answer that can be computed exactly is never handed to a model
- 02Auditable end-to-end — every routing decision logged, dated, signable
- 03Predictable cost envelope — escalation only when warranted, never by default
- 04Grounding screen on every output — an independence check gates the answer before it reaches the client
MaxorConnect
The control plane — governed context, ontology, agents under approval.
MaxorConnect is the control and data plane of the stack : the client's business typed once as an ontology, governed context with masked reads, immutable audit and lineage, deny-default RBAC. Its agents run inside the TensorYard cell and never write directly — every effect lands as a proposal behind a human-approval gate. Twenty-five modules on one plane : Dashboard, Prospects, Companies, Contacts, Deals, Risk Radar, Work, Activities, Tasks, Calendar, Meetings, Email, Chat, Heisen Assistant, Agents, Reports, Delivery, Proposals, Sign, Engagements, Support Tickets, Documents, Contracts, Time Tracking, Marketing.
- 01One ontology — the client's business typed once, reused by every module and every agent
- 02Agents under approval — no agent writes a record ; every effect is a proposal a human accepts or rejects
- 03Multi-org architecture with row-level isolation enforced at the database layer
- 04Bilingual UX (EN + FR) reviewed by native speakers — not machine-translated
TensorYard
The isolation cell — a regulated number, sealed in a signed receipt, replayed bit-for-bit.
TensorYard is our foundry and the containment cell every agent — first-party, third-party, or client — runs inside. A regulated number is computed by a pure engine, sealed in a signed receipt, and replayed bit-for-bit by your auditor, offline, trusting nothing. Proof primitives : canonical encoding, Merkle trees (RFC 6962), Ed25519 signatures, a write-once ledger. Agents reach the outside only through the isolation bus — no direct external socket.
- 01Compute → signed receipt → offline verify — the loop is real and running today
- 02Bit-exact replay at a pinned runtime epoch — a doctored number fails the re-run and is rejected
- 03Isolation bus as the sole conduit to the boundary — no agent holds an external socket
- 04Air-gap deployable — the auditor needs the receipt and the engine, not our servers
HullSmith
The active boundary — the wall, the five gates, and Horizon behind them.
HullSmith is the wall around the cell : five numbered gates and no sixth path. Context in, sanitized ; results out, screened for hallucination and data loss ; tool calls resolved through the substrate ; egress only through a gate. Its verify fabric is deterministic — same input, same verdict, sub-millisecond, at $0, with a replayable receipt. Horizon is the deterministic cybersecurity it vends : one call fuses physics (exfiltration) and grounding (hallucination) at the agent boundary. Deployable standalone, in front of any AI output.
- 01Five gates on the wall — 01 context in · 02 results out · 03 egress · 04 tool ⇄ · 05 dispatch ; if a change draws a path around the wall, the change is wrong
- 02Deterministic verdicts — no model to retrain, no drift, same input → same answer
- 03Signed certificate per decision — the billable unit is a receipt an auditor can re-check
- 04Horizon fusion — exfiltration physics + hallucination grounding in one deny-by-default call
Sentinel
Detect threats one block before they happen.
Sentinel is information-theoretic, unsupervised, predictive threat detection for decentralized finance — oracle manipulation, liquidation cascades, MEV, flash-loan attacks, wash trading — flagged one block before they land. No training data, no rule set : pure entropy, compression distance and long-memory statistics from the Heisen research line, on its own sovereign database.
- 01Unsupervised — no labelled attacks required ; the anomaly is the signal
- 02Predictive — the alert fires on the block before the exploit, not after the drain
- 03Explainable — every alert points to the measurement that moved, not to an opaque score
- 04Free tier, no credit card — ten pairs monitored ; API key for the rest
slopGrade
AI writes your code. slopGrade decides: it passes or it blocks.
slopGrade is the deterministic CI gate for AI-written code. On every GitHub pull request it decides pass or block — 83 gate classes and 123 detectors across injection, crypto, infra, auth, access and supply-chain, calibrated to zero false positives on 5,000+ real repos. A query with no org filter, a hardcoded key, a JWT accepting 'none' stops before merge, not in prod. Extraction runs on your own runner — 0 egress, the code never travels ; keyless OIDC, installed in two minutes. Ten critical classes free and open-source ; blocking from $29/repo.
- 01A required check — red disables the merge, green lets it through ; binary, not a findings list
- 02Zero false positives — every class calibrated on a 5,000+ repo corpus before each release
- 03The cross-tenant leak — an org-scoped query with no org filter, our flagship class, caught before merge
- 040 egress, deterministic — extraction on your runner, the formula not an LLM ; same diff, same verdict
CRANEbee®
Multi-crane simulation · 3D clash detection.
CRANEbee® is the multi-crane simulation platform we distribute exclusively in Canada — built by CRANIMAX GmbH (Germany), deployed on Canadian sites by Maxor. The world's most demanding lift environments use it for site modeling, clash detection, and load-path validation before any field execution. Our methodology layer wraps the platform : every multi-crane plan we engineer is modeled in CRANEbee® before mobilization.
- 01Multi-crane scenario simulation — tandem ops, custom rigging, complex environmental envelopes
- 023D clash detection calibrated to operation envelope — happy path + stress scenarios
- 03Engineered lift documentation generated from the simulation model
- 04Exclusive Canadian distribution — local deployment, training, and integration
Three transformations, under engagement.
Client identities are protected by default — named only with written consent. What's published is the scope, the systems, and the posture. One is named with consent (Cimota) ; the others are referenced by sector.
A new ERP, enterprise-wide AI, one governed stack.
The mandate: one system of record for the whole business — with AI where it earns its place, not bolted on — while the day-to-day never stops.
Cimota is retiring a legacy ERP and rebuilding its operational core on a single governed stack — a multi-year project. Maxor participates as a long-term partner : the ERP transition, enterprise-wide AI woven into the day-to-day workflows, the third-party software integrations that keep operations moving, and the custom systems that fill the gaps no off-the-shelf product covers. Every result is sealed, replayable, and owned by the client.
Stack · MaxorConnect · Heisen · third-party connectors · custom builds
- ERP transition — a long-term project
- Enterprise-wide AI woven into daily workflows
- Third-party integrations for operational support
- Custom software where the catalog doesn't fit
- One governed stack — sealed, replayable, client-owned
A crane operator in Canada
Dispatch, ERP and AI — a next-generation, secure operations system.
The mandate: one operational system for dispatch, the back office and the field — not four disconnected tools bridged by spreadsheets.
For a crane operator in Canada, Maxor is replacing a patchwork of tools with a single operational system. We implement the dispatch platform and the ERP, integrate AI across scheduling and the back office, and connect the operator's existing systems into one next-generation platform — engineered for security and built to run the business end to end.
Stack · Dispatch platform · ERP · AI integration · systems integration
- Dispatch platform — jobs, crews, equipment
- ERP for the back office
- AI across scheduling and operations
- Existing systems integrated, not ripped out
- Security engineered in, not bolted on
A world-class engineering firm
A lift-engineering department, stood up around CRANEbee®.
The mandate: turn a simulation tool into an in-house department — trained, wired into the workflow, and owned by the team.
Inside a world-class engineering firm, Maxor is standing up a lift-engineering department built on CRANEbee®, the multi-crane simulation platform. We don't drop off a licence — we design the workflows, train the team to competency, weave AI into the practice, and integrate CRANEbee® with the firm's existing systems, so multi-crane planning becomes a repeatable, in-house capability.
Stack · CRANEbee® · engineering workflows · AI · systems integration
- CRANEbee® implementation
- Team training to competency
- Engineering workflows, documented
- AI woven into the practice
- Integration with the firm's existing systems
A long-term engagement, in phases.
These are multi-year partnerships, not projects with an end date. We diagnose, then build and run in increments — one senior lead throughout, every irreversible decision documented, every result sealed and replayable. Fixed-price per scoped phase. AI is added where it earns its place, and the client owns and operates what we build together. Identities are protected by default and named only with written consent.
Diagnose & align
Weeks
We map the business and the target state — McKinsey 7S at diagnosis, priorities and constraints named in writing, a phased roadmap before anything is built.
Build in increments
Months
Delivery in slices, never big-bang — each increment engineered to spec, validated, and put in the client's hands. Fixed-price per scoped phase ; every irreversible decision logged as an ADR.
Run & operate
Ongoing
The systems go live and the client operates them — bilingual runbooks, on-call transferred, AI woven in where it earns its place. You run it ; we support it.
Evolve together
Multi-year
The long-term partnership : new capabilities and the next increments as the business changes. Sealed, replayable, client-owned throughout.
Twenty recent lift-plan engagements.
Anonymized snapshot of the kind of work we engineer across Canadian institutional clients — water treatment, cement and aggregates, civil infrastructure, hospitals, energy, steel construction, ports, and engineering firms. Sectors named ; client identities protected by default.
Chute assembly install · Montréal facility
Single pick · Tier I
Process equipment scoping
Pre-engagement · Tier II
Admin building beam install · cote 160
Multi-pick · Tier II
Admin building beam install · cote 170
Multi-pick · Tier II
Culvert replacement program (DD25)
Multi-pick · Tier II
Île d'Orléans bridge construction support
Multi-day · Tier IV
275 t sealed lift · Lanaudière
275 t · Tier III · sealed
Structural lifts · Montréal-area
Multi-pick · Tier II
Turbine nacelle hoist program
Single pick · Tier III
Box-girder beam (caisson) lift program
Multi-pick · Tier III
Facility lift program · 2025.01
Tier III
Facility lift program · 2025.02
Tier III
Facility lift program · 2025.03
Tier III
Structural ironwork install
Sequenced · Tier III
Bus station roof refection · 40 t sealed
40 t · Tier II · sealed
Q4 2025 lift program (multi-engagement)
Multi-pick · Tier II-III
Dec 2025 lift engagement
Tier II
Jan 2026 lift engagement
Tier II
Emergency operator evacuation crane
Emergency · Tier I
Pacific operations lift program
Tier III
Scope a mandate.
The systems above ship as the substrate behind every engagement. The Cimota mandate is the template for client work. Tell us about your modernization — a senior lead responds within one business day. The G1 qualification call is free.