Most providers ask you to trust a badge. We show signed evidence, computed from the platform itself, with the time it was observed and what it covers. Here is how that works, who is responsible for what, and where your data goes.
Check a signed snapshot yourself.
Your browser rebuilds the exact bytes that were signed and checks them against the published key. Change one figure and the check fails. That is what an auditor gets: evidence they can verify without asking us.
Kings Guards
Trust Page, all production apps. Signed 6 Nov 2026, 11:22 UTC
Residency
Current14 volumes, 9 backups, logs and build artefacts stored in Lagos
Observed 6 Nov, 11:16 UTC, 6 min before signing
Includes: guard-roster, client-portal, reports, backups, log store, build artefacts
Excludes: WhatsApp and email alert processors (disclosed separately)
Source records: inv_7c1e20, inv_7c1e21, bkp_cat_3302
Recovery
CurrentRestore drill: 48 s of data loss, restored in 9 min 12 s, checksums match
Observed 3 Nov, 02:40 UTC, 3 days before signing
Includes: roster-db, portal-db, reports-db
Excludes: Files uploaded in the last 15 minutes before the drill
Source records: drill_rst_0912, cert_rst_0912
Change control
Current37 production changes this month, each approved by 2 named people
Observed 6 Nov, 10:22 UTC, 1 h before signing
Includes: Production deploys, Settings changes, Database migrations
Excludes: Preview deploys
Source records: audit_seq_18240-18311, appr_batch_11
Reliability
CurrentAlerts reaching a person within 60 s: WhatsApp 98.9%, SMS 99.8%, email 100%
Observed 6 Nov, 11:00 UTC, 22 min before signing
Includes: All alert channels, last 30 days
Excludes: Voice, not enabled for this tenant
Source records: msg_rcpt_2026-10, msg_rcpt_2026-11
Exit
StaleLast export drill passed. It is past its 30-day window
Observed 26 Sep, 09:30 UTC, 41 days before signing
Includes: guard-roster export bundle
Excludes: External credentials, DNS, Third-party services
Source records: exp_drill_0926
Access review
MissingNo access review recorded in the last 90 days
No record in its window
Includes: Tenant memberships, Approver list
Source records: none found, so it is shown as missing
Attested by partner
Signed by the partner, not observed by the platform
Physical protection
Attested by partnerGuarding and monitoring of the cell facility
Physical protection partner (synthetic). Valid to 31 Mar 2027
Check the signature yourself
Your browser rebuilds the exact bytes that were signed and checks them against the published key. Nothing is sent anywhere.
Board pack, read-only
ActiveShows this frozen, signed snapshot to one audience until it expires.
10:00
Opens for anyone with the link until it runs out or you revoke it.
Who is responsible for what.
Regulators ask for a clear split of duties. This is ours, and it goes into every service agreement. The service applies to Business edition and above, within the coverage agreed with you.
| Layer | Examples | Aspian | You |
|---|---|---|---|
| Platform operations | Regions, backups, recovery, patching, the control plane | Runs and answers for it | Choose the region and the recovery targets you need |
| Application operations | Restarts, scaling, settings, first response to an app fault | Oversees, steps in on escalation, leads serious incidents | Your authorised operators run the runbooks they are trained for |
| Application changes | Fixing a workflow, new features | Builds them when you ask, scoped separately | Decide what changes; your developers can build them too |
| Business decisions | Approving business-impacting changes, accepting risk, data-controller duties | Gives advice and evidence | Decide and approve. Aspian’s approval never replaces yours |
Where your data is stored, and who else touches it.
We separate what the platform observes from what is configured and what is processed elsewhere. Anything that leaves your region is listed, not hidden. The named list of providers is part of your agreement.
- Platform-observed
Application databases, volumes and backups
Stored in the region you choose
- Platform-observed
Logs, metrics and build artefacts
Stored in the region you choose
- Platform-observed
Audit records
Stored in the region you choose, with signed checkpoints kept on write-once storage
- Disclosed
WhatsApp messages
Processed by Meta outside Nigeria and the UK. Nigerian organisations’ messages carry only an alert code and a link
- Disclosed
SMS, voice and email
Processed by the providers we name in your agreement, some outside your country
- Disclosed
AI agents you connect
Processed wherever that agent runs. Agents only see what their risk class allows, never secret values
How we keep it that way.
- Passkeys, not passwords
- People sign in and approve with passkeys tied to cloud.aspianalliance.com, so a look-alike site can’t use them.
- Two-person control
- Changes that matter need two different named people, and never the person who asked.
- Secrets you can’t read back
- Values are written once and injected into the running app. No screen, log or agent can display them.
- Signed images only
- Every build carries a bill of materials and scan results. Unsigned images are refused.
- A record nobody can quietly rewrite
- Each organisation’s audit trail is a signed hash chain, checkpointed every hour outside the database.
- A tested way out
- Exports to Terraform, Helm and Docker Compose are rehearsed. Credentials, DNS and outside services still need moving.
Certifications
We will list certifications here once an independent auditor has issued them, with dates. Until then we publish evidence instead of badges: signed snapshots, restore drill certificates and evidence packs mapped to NDPA 2023, UK GDPR, ISO/IEC 27001 and the NHS DSPT.
Bring us the system you can't afford to get wrong.
We are opening Aspian Cloud to organisations in stages. Create an account and we will set up your workspace, or talk to us about the systems you run today.