Trust & security

Check it yourself.

Your compliance team can check what KolaPact claims from hardware evidence and signed receipts, offline, without anyone seeing your content.

CHECKING A NODE BEFORE SENDING
  • Hardware signatureAMD SEV-SNP
  • Build measurementmatches pin
  • Certified buildin force
  • Seat keyvalid
  • Sealed tothis machine only
Nothing outside an attested machine or your own device ever receives readable content, or a key that opens it.

What makes it checkable

Six things your auditors can check themselves.

Hardware attestation

Each machine shows evidence, signed by the chip maker, of exactly what it runs. AMD for SEV-SNP machines and NVIDIA for H100 GPUs in confidential computing mode. Intel TDX is next.

Pinned build measurements

Your devices only send to builds whose measurements they pin. A node running a changed image is refused.

Pins on your device

Your client trusts only the chip makers' roots, the build measurements and the admin key it holds itself.

Sealed end to end

Content is encrypted on the device to one attested machine, with HPKE (RFC 9180).

Signed receipts

Every job ends with signatures from the machine and the platform that anyone involved can check offline.

Append-only records

Receipts and dispute verdicts are written once. Nothing decided is edited later.

Who sees what

Every party, and exactly what reaches them.

What each party can see
PARTYCONTENTKEYSMETADATA
Your devices✓ reads✓ holdsyes
Attested machine✓ inside only✓ inside onlyyes
Provider operatorsnevernevercounts, timings
Cloud hostneverneverciphertext only
KolaPactneverneverwho, when, sizes
Your IT adminneverneverseats, usage
Auditorneverneverreceipts, builds

Honest limits

What version one doesn't hide.

Here's what it doesn't do, or doesn't do yet.

Usage is visible

The platform sees who ordered, when, sizes and counts. Version one hides content. It doesn't hide usage patterns.

Quality can't be proven blind

Disputes cover integrity and delivery. Whether a result is good needs ratings on top.

Hardware is part of the trust

We rely on the chip makers' attestation. Proofs that need no special hardware only work for tiny models today.

Some checks are still to come

Publishing build measurements for anyone to check, and a security test by an outside firm, aren't done yet.

Where it stands

What has run where.

There are no customers yet. This is what we have built and where we have run it.

ON CONFIDENTIAL HARDWARE IN AZURE

  • AMD SEV-SNP machines answering sealed requests
  • NVIDIA H100 GPUs in confidential computing mode running a real model
  • A node with a changed image refused
  • The dispute arbiter running in an attested machine
  • Organisations, seats, revocation and the browser console

BUILT AND TESTED ON A LAPTOP

  • Streams through the edge
  • JavaScript and Python SDKs and the command line tool
  • Records copies and certified builds for government
  • Admin security keys and recovery codes
  • An optional network restriction per organisation
  • Intel TDX images, not yet run on hardware

NOT BUILT YET

  • Single sign-on and SCIM
  • Published build measurements
  • An outside security test
  • An on-premises kit

Measured so far

Numbers from our own test runs.

32.7 ms Platform time added to a sealed request, p95, one at a time. Azure, ordinary VMs, model time near zero, not yet through the edge.
0.1 to 1.2 s Per sealed request answered by a small model on an NVIDIA H100 in confidential computing mode, then opened and checked on the device. Azure, three requests.
2.0 million Stream records a second through the edge, at p95 2.98 ms. Laptop.
10 s For the registry to refuse a node whose measurements weren't in its policy. AMD SEV-SNP on Azure.

Targets for production: at most 50 ms added per request at p95 through the whole path, and a revoked seat's open streams stopped within 2 seconds.

Bring your compliance team.

We'll walk them through attestation, builds and receipts, and show them how to check it all without us.