Verifying what you received

Everything we hand you is signed with one cosign keypair, so you can check that what you hold is what we built — independent of the channel it arrived through.

Fetch our public key once and keep it:

curl -fsS https://api.backend.<domain>/signing-key > flairos.pub

The compose kit

Your admin received a detached signature next to the file (the dashboard shows it under "Kit signature"). Verify the exact file you are about to run:

cosign verify-blob --key flairos.pub \
  --signature kit.sig --insecure-ignore-tlog=true docker-compose.yml

The model image

The signature lives in our registry beside the image:

cosign verify --key flairos.pub --insecure-ignore-tlog=true \
  registry.backend.<domain>/flp-app-<model>:latest

--insecure-ignore-tlog looks alarming and is not: it means verification trusts the key you fetched above instead of a public transparency log. We deliberately do not publish to one — this is a private deployment, and a public log entry would broadcast internal hostnames. Pinning our key is the trust model.

A verification failure means the artifact is not what we built. Do not run it; contact us with the file and the signature.