Security & trust

Built to survive a bank's security review.

Montora runs some of your most sensitive code and produces evidence your risk and audit teams will rely on. Here is exactly how we keep it safe, and how we let you prove it.

Run record·LOANPAY
Example

Isolation boundary

  • Networknone
  • Filesystemread-only
  • Privilegesdropped
  • Secretsnot passed
  • Workspacedestroyed after run
Signed sha256 4b7e…a90cVerifiable by anyone

Sandboxed

Zero network egress

Independent

Held out from training

Signed

Verifiable results

Human-gated

Every change

Your code runs in a locked box.

Untrusted migrated code is never executed in our control plane. It runs inside an isolation boundary and comes back as plain data, so a hostile or buggy program cannot reach anything it should not.

Control plane
  • Untrusted migrated code is never executed here
  • Control-plane secrets are never passed to the runner
  • Results come back as plain data
Isolation boundarymigrated codeplain datasecretsMigrated code crosses into the runner, plain data is the only thing that comes back, and secrets never cross.
Sandboxed runner
untrusted migrated code
  • Zero network egress: no exfiltration, no phone-home
  • Read-only filesystem, ephemeral workspace destroyed after each run
  • Dropped Linux capabilities, non-root, no-new-privileges
  • CPU, memory, and process caps stop runaway or fork-bomb code

It refuses rather than fake it.

A certification-grade run requires a real isolation boundary. If one is not available, Montora refuses to run rather than silently drop to a weaker sandbox and imply a guarantee it cannot make.

  • Certification never runs in a non-boundary sandbox
  • Every result records exactly how and where it was executed
Certify 3200-CALC-INTEREST.
Certification run·3200-CALC-INTEREST
Example
Isolation boundarynot available
Weaker sandboxnot used
Scorenone issued

refused: no isolation boundary

Nothing was run, so nothing is claimed.

Recorded: how and where it was attemptedkept

Safe to run.Possible to prove.

01

The proof cannot mark its own homework.

Certification evidence is held out from the data that produced the migration. A passing score is therefore independent of what created it, which is exactly what a model-risk function asks for.

teaching datakept disjointcertification evidence
  • Teaching data and certification evidence are kept disjoint
  • No result can certify a migration it helped create
02

Every result is signed and verifiable.

Results are sealed with a cryptographic signature and a reproduction key, so your risk and audit teams can verify them independently, long after the run, without trusting us.

sha256 4b7e…a90cpublic key, no shared secretrevoked when the engine changes
  • Third-party-verifiable signature (public key, no shared secret)
  • A reproduction key ties the result to its exact inputs
  • A change in the engine automatically revokes affected results
03

Nothing ships without a person.

A human approves every change. The finalise gate blocks shipping on an unresolved, reachable, critical divergence, and every override is recorded with a reason.

ApproveEditRejectfinalise blockedcritical divergence unresolved
  • Per-change approve, edit, or reject
  • The gate blocks a real critical divergence until it is resolved
  • Overrides are audit-trailed, never silent bypasses
04

Designed to run inside your walls.

Montora is a separate data-plane engine, built to deploy inside your own environment, so your source and data never have to leave your control.

private cloudon-premair-gapped
  • Runs in your private cloud, on-prem, or air-gapped
  • Owner-scoped access with no cross-tenant reach
  • Bounded APIs that never leak internal detail

Want the full security pack?

We will walk your security and risk teams through the architecture, the isolation model, and the evidence, and share the detailed documentation under NDA.