Independent hardware.
A shared purpose.
SEVEN KG LLC coordinates compute that other people own. The operators hold the hardware. Our job is to check that a machine is what it claims to be, and then to place work that fits it.
Phone racks come first, and they are most of what is running. Datacenter GPUs have stopped being research: two confidential GPU machines are in the pool and have carried billed work. Whether a single consumer phone belongs in this at all is a question we have not settled.
Operators will be paid in ordinary money at stated rates, not in a token. The customer side is open: attestation, certificates, evidence retention and compute each carry a published rate and each bills. The operator side is half built — machines enrol, attest and earn, and the cashout that turns those earnings into a payment is the next thing we owe.
Predictable prices, in ordinary money.
Rates are set in dollars and held steady, so an operator can plan and a customer can budget. No token. No wallet. No chain. Every rate we charge sits on the pricing page before it is charged, which is the page to read rather than this one.
Private
Every TPM carries an endorsement key: a serial number burned in at manufacture that can never be changed or reissued. Keep one and you have created a permanent way to recognise that machine forever, so we decided not to keep one. It becomes a keyed hash before it ever reaches our database, which means our records cannot be matched against any other system that has seen the same hardware. The design is settled, written and in force: it has run in production since 21 September 2026, when the first TPM enrolled.
Workload privacy is the harder question, and we would rather earn that claim than assert it. Before we describe any environment as confidential, we will publish what protects a workload there and what does not — including what the operator of the machine can see, not only what we can.
Decentralized
The hardware belongs to the people who run it. Operators own their machines and decide what work to accept; our part is to coordinate the network and verify what joins it.
That coordinating layer is ours, and it is centralised. We would rather say so plainly than stretch a good word until it stops meaning anything.
Verifiable
A result you cannot check is only an assertion. Every record we issue says what was examined, which policy it was measured against, and — the part most reports leave out — what the decision does not establish.
You should finish reading one knowing exactly where its boundary sits, rather than having to go looking for it.
How we charge
Predictable rates. No cryptocurrency token.
Charges follow recorded runtime, and a job that fails is handled by a rule we publish rather than settled case by case. The rates are on the pricing page, and they went up before anyone could be charged rather than afterwards.
The billing engine records customer charges, operator earnings and platform margin. The customer half of that moves real money now: an invoice carries a payment link and is collected through Stripe. The operator half stops at the ledger — earnings are recorded and nothing has been paid out of them, because the cashout is not built.
Development snapshot · 1 November 2026
Built so far. Work ahead.
Implemented describes code running in production. It is not a promise that every part of it is self-serve.
Android attestation
ImplementedPhysical-device testing documented. Public observations are available in Hardware Tests.
Policy evaluation & placement
ImplementedRequirements, freshness checks, queue explanations, and capacity limits.
Signed verification records
ImplementedExportable Ed25519-signed bundles. Inspect a synthetic example.
Persistence & billing calculations
ImplementedSQLite storage and recorded charges and earnings. Payment settlement remains separate.
Node agent & job execution
ImplementedOutbound registration, periodic re-attestation, and sandboxed container execution. Jobs have run end to end on our own and on rented hardware, including GPU jobs through the production coordinator, and a result has been written back to object storage and read out again.
AWS Nitro verifier
ImplementedAppraised against a real Nitro enclave attestation document. Which roots the live service accepts is listed on attestation roots, which is the one page that answers that.
TPM 2.0 attestation
ImplementedEndorsement certificates from both a discrete and a firmware TPM appraised first-hand against pinned vendor roots. Enrolment binds an attestation key to an appraised endorsement certificate, and the verifier then checks each quote against that enrolment record — because an endorsement certificate carries no challenge, and presenting a copy of one would prove only that a copy was obtained.
Apple App Attest verifier
ImplementedVerified against a real iPhone 14 Pro on 2 October 2026, having first been tested against a synthetic certificate chain. Seven more attestations followed on 13 October across six Apple devices, iOS 17 to iOS 27, one of them a tablet.
GPU attestation
ImplementedNine GPUs have attested across two rented confidential machines, one Blackwell and eight H100. Two of our own jobs have run on one and billed; no customer workload has. NVIDIA implements confidential computing on datacenter parts only; consumer cards cannot attest at all. See what we cannot do.
Private workload execution
In developmentEncrypted workload delivery and the complete result-return pipeline.
Operator payouts
In developmentCustomer payment collection is live and runs through Stripe. What is missing is the other direction: operator earnings are recorded to the ledger, and nothing has yet been paid out of it.
Follow the evidence.
As the system develops we will publish how it was tested, what came back, and where each result stops. Questions, operator enquiries and security reports are welcome at contact@svnkg.com.
Explore the hardware research →