Edit Template

Pilot

Try it in a sandbox first.

Two sandbox steps make up the pilot. A small real rollout comes after, when you decide to move on.

No live customer data sits on UniKey systems. We review each request by hand.

Sandbox run summarystep 2, your sandboxIllustrative

What your verifier decided

  1. Signed, in-scope actionsvalid, unused, inside what was signedAPPROVED
  2. Changes with no approver packetheld until a person signsREVIEW
  3. Replayed packetsnonce already usedREFUSED
  4. Requests outside the signed scopea payee, an account or a table differsREFUSED

A run summary in words. It shows no counts because none are claimed. Synthetic or test data only.

01 · Request access

Start in our sandbox.

  • We review each request by hand.
  • A person replies with a sandbox invitation or a question.
  • No live customer data is needed at any step.

02 · Three steps

From our sandbox to your environment.

One to two weeks

Explore in our sandbox

Discovery, your use cases and a review, in UniKey’s demo and pilot environment.

Two to three weeks

Run it in your sandbox

Your engineers stand up a verifier in your own sandbox. We play the good agents and the bad ones.

After the pilot

Go small and real

When the pilot is done and you’re ready: a few real trading partners or one business unit, in your environment.

03 · What you’ll see in step 2

Good agents get through. The rest are held or refused.

In your sandbox, we send the actions your process expects, plus ones it shouldn’t accept. Your verifier decides each one, and every decision lands in the Authorization Ledger.

  1. A signed action arrives. Valid, unused and in scope, so it runs.

  2. A change without an approver arrives. It’s held for a person to confirm.

  3. A replayed packet arrives. It is refused, and the refusal is recorded.

  4. You read the ledger. Every allow, every hold and every refusal, with the packet that decided it.

Authorization Ledgeryour sandbox verifierIllustrative
ChainRecordActionSenderVerdictCommits to
al_000416update_supplier_bankap.supplier.example.comREVIEW
Approver packet missing
prev ex-9d02hash ex-a41f
al_000417approve_supplier_bankapprover.buyer.example.comAPPROVEDprev ex-a41fhash ex-c3b8
al_000418update_supplier_bankap.supplier.example.comAPPROVEDprev ex-c3b8hash ex-e52d
al_000419update_supplier_bankap.supplier.example.comREFUSED
Nonce already used
prev ex-e52dhash ex-f09a

Each record commits to the hash of the record before it, so a changed or missing row shows. Sample ids and hashes.

04 · What each side brings

Two teams, one sandbox.

You bring

  • One process you’d protect first
  • An engineer who can stand up a verifier in your sandbox
  • Someone who can approve the move to step 3

We bring

  • The UniKey demo and pilot environment
  • Good agents and bad ones to test against
  • A review of what the ledger shows

05 · What a pilot does not touch

Synthetic or test data only.

Answers for a vendor review
  • Pilots use synthetic or test data only.
  • No production funds move in a pilot.
  • Production, when you choose it, runs in your own environment.
  • Production can start in observe mode and move to enforcement.

06 · Land and expand

Sending is free. Verification is where value is exchanged.

Anyone can send Trust Packets. Your verifier is where you decide what runs. Start with one process and add more on the same verifier.

Next step

They verify the agent. UniKey verifies the action.

Watch one action get checked on sample data, or start with a sandbox pilot.






    No live customer data sits on UniKey systems.
    We review each request by hand.

    A UniKey property. © 2026 Swoop In Technologies LLC

    Edit Template