Independent hardware.
A shared purpose.
SEVEN KG LLC is building a network of independently operated compute resources, coordinated by SEVEN KG. Operators own the hardware; our intended role is to verify devices and place compatible workloads.
Our focus starts with phone racks. Datacenter GPUs are part of our research roadmap, with individual consumer phones also under consideration.
We aim to offer predictable, fiat-denominated payments rather than a cryptocurrency token. Operator enrollment, compute rental, and payments are not publicly available yet.
Predictable prices, in ordinary money.
We intend to price in fiat and keep rates stable, so an operator can plan and a customer can budget. There is no token, no wallet, and no chain. Operator enrollment, compute rental and payments are not available yet, and no rate has been published.
Private
Workload privacy is a design goal. We will document the protection and threat model of each supported environment before making confidentiality claims.
That applies to operators, not only customers. A TPM’s endorsement key is a permanent hardware identifier, burned in at manufacture and impossible to change or reissue. We have decided never to store one: it is replaced by a keyed hash before it reaches our database, so our records cannot be matched against any other system that has ever seen the same machine. Decided and written; not yet running.
Decentralized
Hardware is intended to be owned and operated by independent participants. SEVEN KG coordinates the service; this does not make every layer decentralized.
Verifiable
Evidence should explain what was checked, which policy was applied, and the limits of the resulting decision.
Our commercial direction
Predictable rates. No cryptocurrency token.
We are developing a fiat-based pricing and earnings model, with charges tied to recorded runtime and defined handling of unsuccessful jobs. Final rates and payment availability will be published before launch.
The current billing engine calculates customer charges, operator earnings, and platform margin. Those ledger records do not collect money or complete a payout.
Development snapshot · 14 September 2026
Built so far. Work ahead.
Implemented describes code in the prototype, not public availability or a production guarantee.
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. One job has run end to end on our own hardware. Returning results to customer storage is written but has not been exercised.
AWS Nitro verifier
ImplementedAppraised against a real Nitro enclave attestation document and registered in the coordinator.
TPM 2.0 appraisal
PartialEndorsement certificates from both a discrete and a firmware TPM appraised first-hand against pinned vendor roots. Deliberately not yet an attestation verifier: an endorsement certificate carries no challenge, so presenting a copy proves only that a copy was obtained.
Apple App Attest verifier
Validation pendingWritten and tested against a synthetic certificate chain. No Apple device has been tested, and it is not yet registered in the coordinator.
GPU attestation
ResearchNo GPU has produced evidence. 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.
Public access & payments
Not availableCustomer onboarding, operator accounts, deployment, and payment collection and payouts.
Follow the evidence.
We will publish methods, observations, and limitations as the system develops. Questions, operator enquiries and security reports are welcome at [email protected].
Explore the hardware research →