Why a fleet is a different thing
The free proof exists so a stranger can try us once. It was never meant to verify an estate.
One free proof is counted against an address and against the machine, every 72 hours. Two machines behind one router share that address, so the second is refused until the cooldown clears — which is correct for someone trying the service and useless for anybody running twenty servers.
So fleet attestation has no free allowance at all. It is billed per device per month, it has no cooldown, and the same account verifies as many machines as you have.
What you actually do
Four steps, and three of them are on this site
One — open an account.
Sign in at your account page. An account is an email address and nothing else; we ask for no company details, no job title and no phone number, because none of them are needed to verify hardware.
Two — add funds.
Verification is prepaid. You add an amount, the card is handled by Stripe and never touches our servers, and the balance sits against your account until devices spend it. Nothing bills automatically and no card is kept on file by us.
Three — mint an API key.
The account page issues keys. A key is shown once, on the response that creates it, and we keep a SHA-256 of it rather than the key — so we cannot show it to you again and cannot leak it back to you later. Revoke one the moment you think it has been seen.
Your software sends it as Authorization: Bearer <key>.
Four — run the agent on each machine.
The agent asks our coordinator for a challenge, has the machine's TPM sign a statement bound to it, and sends that back. You get a signed evidence bundle per machine.
There is no public download yet. Ask us and we will send you the build. When the download is published it will appear here with its digest, because a verification company that ships an unverifiable binary is not one.
What a fleet gets that a single proof does not
No cooldown, a certificate, and a record that persists
Attest whenever you want.
The 72-hour cooldown is a property of the free tier. A funded account has none: attest a machine on every boot if that is what your policy needs.
One certificate covering the fleet.
A verification produces a signed JSON bundle, which is a file. Some people need a document instead — something to hand an auditor or put in a tender. A fleet certificate is one document about the whole fleet and comes with the verification rather than being sold separately, because a certificate without the work behind it is decoration.
The devices stay on your account.
Each verified machine appears on the account page with what it proved and when. Evidence is kept for a published window and then goes, with two notices before anything expires. What we keep, and for how long.
Nothing here is a certification.
SEVEN KG did not manufacture your hardware, does not administer it, and certifies no organisation against any standard. We verify what the hardware proved and we say what that does not cover. The boundary of every claim is published.
Phones
Attested Mobile is the app, not the agent.
A handset proves itself through the SEVEN KG app, which claims the device against your account with a code from the account page. The agent on this page is for machines with a TPM — servers, desktops and laptops. A phone is not attested by running the agent and the app does not verify a fleet.
What it costs
Published, per device per month, with the tiers on one page.
Every rate is on the pricing page and nowhere else. We do not quote a figure in an app, in a binary or on a second page, because a number copied anywhere is a number that disagrees with the price the day either one changes.