Skip to content
Lacren

Security

What stays private?

Lacren checks the machine and software before a private model can run. This helps keep the model weights out of the host's ordinary access. It does not prevent someone from learning about a model by repeatedly using its API.

Model weights

What we guaranteeEncrypted on the owner's device before upload. The key is released only to a runtime that passes a fresh hardware check against an approved software measurement. Ordinary Lacren servers never hold the unwrapped key.
ExceptionsHardware flaws and side channels can still exist. A browser extension on the owner's device can see the file before it is encrypted. Anyone with access can learn about a model by calling it repeatedly.

Customer inputs

What we guaranteeEach model states whether inputs pass through the standard API gateway or are protected to the secure runtime. Lacren does not store inputs or outputs in its ordinary database.
ExceptionsWhen inputs pass through the gateway, the gateway can see them in transit.

Payment data

What we guaranteeFunds sit in an escrow contract on Robinhood Chain. Charges settle against signed receipts that the contract checks.
ExceptionsOn-chain data is public: deposits, withdrawals and settlements are visible to anyone.

Verification

How verification works

Evidence expires. When it does, the model stops taking new requests until a new check passes.

  1. The runtime asks the verifier for a one-time challenge.
  2. It produces a hardware quote that binds that challenge and the runtime's public keys.
  3. The verifier checks the quote signature back to the hardware vendor's root and checks the firmware status.
  4. It compares the measured software with the approved list and confirms the keys match.
  5. Only then is the model key released, wrapped to that runtime's key. Any failed step rejects the runtime.

Trust assumptions

Protection holds only while these are true. We state them so you can judge them.

  • The hardware vendor's attestation and its revocation data are correct.
  • The verifier and key-release service run separately from the main application servers.
  • The approved runtime image does what its published source says.

Known limits

What this protection does not cover, in plain terms.

  • A host can still refuse to run a model.
  • Repeated queries can reveal how a model behaves.
  • Hardware bugs and side channels remain in scope.
  • Runtime evidence shows where a model ran. It says nothing about whether its answers are accurate.
  • Models in demo mode are labelled "Demo — weights are not protected by hardware" and never shown as verified.

Evidence

Inspect a deployment

Every model page links to its proof: the three checks with timestamps, the quote hash, measurements, verifier and policy versions, and downloadable evidence.

Example

How this model is protected

  • Machine verified
  • Software approved
  • Model loaded in protected runtime

Each check shows its own result and time on a real model page.

Report a problem

A security contact will be listed here before mainnet launch.