Sealed processing for regulated organisations

Use outside technology.
Keep your data sealed.

Run your most sensitive data through outside AI, analytics and software. It opens only inside machines that prove what they run. The provider can't read it, and neither can we.

KolaPact is a sealed processing platform for organisations and governments in AI, data analytics, pharmaceuticals, healthcare, banking and finance, and the public sector.

  • AI & models
  • Data analytics
  • Pharmaceuticals
  • Healthcare
  • Banking & finance
  • Government

How it connects

Your data. Their machines. Every step checked.

Your data leaves sealed, runs only inside the provider's attested confidential machine, and comes back sealed. KolaPact sits in between and checks the evidence, signatures and receipts. It can't open anything.

Your organisation Provider machines KolaPact · verifies
  • Peopletheir devices
  • SystemsAPI and streams
  • Recordssealed copies
  • AI modelsconfidential machine
  • Analyticsconfidential machine
  • Clinical researchconfidential machine
  • Risk scoringconfidential machine
VERIFIES
NEVER OPENS
  • attestation checked
  • signatures checked
  • receipts signed
  1. 01 · The pull

    Useful tools are often built elsewhere.

    Models, analytics and research tools, often from abroad. To use them today, you send your data in plain text.

  2. 02 · The problem

    Anyone along the way can read it.

    Provider staff, logs, a breach. Contracts make promises, but nothing technical stops them. So a lot of useful work never starts.

  3. 03 · Seal

    Seal it before it leaves.

    It's encrypted on your own device, to one specific machine. Nothing in between can open it.

  4. 04 · Prove

    Open it only where it's proven.

    The machine shows hardware-signed evidence of exactly what it runs, with the provider's software inside. If it doesn't match, your device doesn't send.

  5. 05 · Defend

    Try to break in. Get nothing.

    Intercept it on the way and you hold noise. Pretend to be the machine and the evidence fails, so the device refuses. No key leaves the boundary.

  6. 06 · Return

    Back to you. Only you.

    The result comes back sealed to your device. Everyone else sees ciphertext, timings and counts.

  7. 07 · Stay regulated

    And still on the record.

    On plans that need it, a sealed copy goes to your records officer. Auditors can check receipts offline without seeing any content.

One layer, every industry

Wherever the data is too sensitive to share.

Move closer to any sector to see what stays sealed.

The trust model

Who can read your data?

Two circles. Everyone outside the inner one only ever handles ciphertext, signatures and counts, and the hardware evidence shows it.

Your devices CAN READ
Where data is sealed and results are opened.
  • Hardware attestation
  • Pinned build measurements
  • Receipts you can check offline
  • Seat revocation
CANNOT READ
CAN READ
YOUR DATA

For your admins

Your admins stay in charge.

They decide who and what gets in, and they still can't read anything.

Seats you can revoke

Every seat is a key on a real device. Revoke one and its requests are refused and its open streams stop.

EXAMPLE
M. Okaforlaptop · key 3a1f… ACTIVE
Claims APIservice · key 9be0… ACTIVE
L. Haddaddesktop · key c47d… ACTIVE REVOKED
Records officertablet · key 51e2… ACTIVE

Streams for your systems

Connect services through the API and SDKs, as one-off sealed jobs or continuous sealed streams.

Usage, never content

Reports by team and seat. Counts and timings, nothing more.

EXAMPLE
4,812jobs this month
content visiblenone
  • JavaScript and Python SDKs
  • Command line tool
  • Security keys and recovery codes for admins
  • Certified builds for government
  • Sealed records copies
  • Optional network restriction per organisation

Their technology.
Your data.
Sealed in between.