For utilities
One evidence layer per utility — never shared between them.
It sits beside the systems a utility already runs and gives every value a source, a time, a quality and a receipt. Each utility runs its own copy, in its own country, under its own keys.
What it does
Three things, and nothing that writes back.
Every value keeps its proofCopies arrive as signed batches and are answered with receipts. A correction is a new record beside the old one, never an overwrite.
Every asset gets a permanent addressAn identity under the utility's own namespace that never changes or gets reused. The QR plate on the equipment opens it — on the utility's own host.
Anyone can check, without usAn auditor, regulator or vendor checks a receipt or a sealed export against the utility's public key — in a browser or offline.
See it on synthetic data: three demo tenants (UAE, Oman, Qatar), each asset with its address, QR plate and verified history.
Onboarding a new utility
The same steps for every utility, in every country.
Week 0
ScopeOne conversation: the country, one department, one asset class and the file list. A non-disclosure agreement before any file moves.
Weeks 1–6
The six-week auditOn exported sample files, in your building, for a fixed fee. How the audit works.
Pilot start
Your tenant is createdA tenant identity and namespace of your own. Signing keys are generated on your hardware; a certificate authority of your own issues every connection's certificate. Local time zone, date format, currency and units are set once, for your tenant.
Pilot
Read-only connectorsHistorian or CSV exports, lab results, maintenance records — one department, two or three source systems, one restore drill. On your side of the network boundary; nothing writes back.
Pilot end
Plates and proofQR equipment plates for the pilot assets, printed from your tenant. Your own auditor verifies a sealed export without us.
After
The next departmentEach further department, asset class or commodity is the same steps on the same tenant.
The audit is fixed at six weeks. The pilot's length and price are set in the statement of work, after the audit — never before it.
Security and data residency
Where the evidence lives, and what may leave.
| Certifications held | None. We say so first, before any claim below. |
|---|---|
| Where evidence lives | On infrastructure the utility controls, in its own country. One tenant per utility, with its own ledger chain; no table, query or aggregate spans two tenants. |
| What may leave | Only proof: receipts and hashes the utility chooses to hand over, and its public key. A receipt carries hashes, counts and a control total — never the readings. |
| What this website holds | Each tenant's public key, and the synthetic demo evidence. No running system depends on it: if verifiedsubstation.com is offline, nothing at a utility stops. |
| Connections | TLS 1.3 with a client certificate chained to the utility's own certificate authority. Plain HTTP is for a developer's own machine only. |
| Toward source systems | Read-only. There is no write path to SCADA, SAP or protection in the code. |
| Approvals | Humans only. The approval endpoint refuses every machine. |
| People | Recorded in the ledger by pseudonym. The map from pseudonym to name is encrypted per tenant and can be erased. |
Talk to us about your utility.
Tell us the country, the department and the asset class. We reply with the audit figure and the file list.