How we prove our work
Before an institution hands anyone something that matters, it asks one question: can we trust them with this? We don't ask for your trust. Every change we make is recorded, so you can check it.
Inspect a record before you trust us
This is what one change looks like on Aspian Cloud: the work item and the scope it was allowed to touch, who approved it and when, the tests and scans it passed, the version confirmed running, and its place in a signed audit chain.
Verify it, then widen the scope and verify again. The example is synthetic and signed with a demo key.
Evidence record chg_2611_0417 · A national licensing body (fictional)
Move licence records from the legacy database to the new records system
WI-212 · Written delivery plan v3, signed 2 Sep 2026
- Work item and allowed scope
AC-14: Every active licence migrated, with counts that reconcile to the legacy system
- records-service
- migration scripts
- read-only access to the legacy database
Out of scope: Payments, Public verification portal
- Approved by passkey
- A. Okafor, Head of Registry Systems, client4 Nov 2026, 09:12 UTC
- R. Mensah, Engagement lead, Aspian Alliance4 Nov 2026, 09:31 UTC
Risk high: moves the authoritative record for every active licence. Backout: point the registry back at the legacy database (one setting); it stays read-only and current until sign-off.
- Tests and scans
- Automated tests: 212 passed, 0 failed
- Security and dependency scan: No new findings
- Migration reconciliation: 184,206 records matched, 0 missing
- Deployed and confirmed running
Production, 4 Nov 2026, 10:02 UTC. Confirmed running records-service 2.4.0 at 4 Nov 2026, 10:05 UTC, the version that was approved (commit 9f3c2e1a7b4d).
- Place in the audit chain
Entry 1,188 of the engagement audit chain, append-only. It follows entry 4b7e19c0a2d35f68 and was signed 4 Nov 2026, 10:06 UTC.
Check it yourself
Your browser checks the signature against the published key. Nothing is sent anywhere.
Verify the record, then widen the scope and verify again.
Check it offline
node -e "const c=require('crypto');const k=c.createPublicKey({key:{kty:'OKP',crv:'Ed25519',x:'l23CoWkqr6jBSMZXPUyr1x4u_ranhZNrPqGWecqIb0g'},format:'jwk'});const ok=c.verify(null,require('fs').readFileSync('aspian-sample-evidence-record.json'),k,Buffer.from('3C0hrjSlnUa0B/l1TrHeI8G032i0jKJalDT88cG45t9NbyCo0KMSZCW7YPvLSvdn8uQHOUvd+Z1pdQKTFyOKDA==','base64'));console.log(ok?'Signature valid':'Signature does not match')"Synthetic example. The institution and people are fictional, and it is signed with a throwaway demo key that cannot sign anything else.
Observe, Gate, Hold
Aspian Cloud governs each system at one of three levels: Observe watches what reaches production on the tools you already use and flags anything that was not approved, and Gate stops any deploy that lacks an approval bound to that exact change. Hold goes one step further, because we hold the deploy credentials, so there is no route to production around the approval.
- Level 1
Observe
Watches what reaches production on your existing tools and flags anything unapproved.
- Level 2
Gate
No deploy goes ahead without the approval bound to that exact change.
- Level 3
Hold
We hold the deploy credentials, so there is no route around the approval.
What you receive at the end
Whether we hand over or keep running the system, the end of an engagement is planned from the start. You receive the handover pack, and proof that our access has ended.
The handover pack
Ownership confirmed
Source code, infrastructure definitions, data and accounts, confirmed in your name.
SBOM and licences
Every component in what we built, and the licence each one carries.
Runbooks
How to operate, recover and change each system, written for your team or your next supplier.
Full change history
Every change from the first day: what it was, who approved it and what it was tested against.
What we don’t do
- We don’t staff out junior teams.
- We don’t sell speculative AI.
- We don’t keep your keys.
A one-page board brief
The same story on a single page, written for the people you answer to: what we do, how every change is proven, what your board can check, and what you hold at the end.
Aspian Cloud is the platform we built to do this, and the one every engagement now runs on. Visit Aspian Cloud