Risky changes go to the people you named, on their phones. Every decision lands in a tamper-evident record, and that record becomes evidence your board, auditors and regulators can check for themselves.
An approval is a decision, not a tap on a link.
When a change touches production, Aspian Cloud asks the approvers you named. The message only starts the request. The decision happens in your own browser, with a passkey, against the exact plan you read.
- 1
A message starts the request
WhatsApp first, then SMS or email if it isn’t delivered. It carries a summary and a single-use link.
- 2
The link opens in your phone’s browser
Never inside the chat app. Opening a link preview doesn’t use the link up.
- 3
You review the plan
What changes, what it affects, how it rolls back, and who asked for it.
- 4
You confirm with a passkey
Face ID, a fingerprint or a security key. The approval is tied to that exact plan.
cloud.aspianalliance.com
Your approval is needed
Expires 18:00Add patrol exceptions to incident log
guard-roster, production, Kings Guards
- What changes
- Adds one field to the incidents table and releases the new app version.
- Disruption
- None expected. 10% of users first, rolls back if errors pass 2%.
- Data impact
- Adds one field. No existing records change.
- Who
- Asked by Tunde Adeyemi, developer. Needs you and Emeka Obi.
Plan 7Q2F 8KD2 51C0. Your approval applies only to this plan.
The approver sees what changes, what it affects and who asked before the passkey step.
- Two different people
- Regulated and dedicated organisations need two approvers for risky changes.
- The requester can’t approve
- Whoever asked for a change is never one of the people who approves it.
- Used links are refused
- So are expired ones. A change still needed comes back as a fresh request.
- Low-risk work stays one step
- Preview deploys and rollbacks never wait for an approver.
cloud.aspianalliance.com
Kings Guards
Good morning, Ngozi
Friday 6 November, updated 10:40
Are our applications running normally?
Yes, 3 of 3 healthyguard-roster, client-portal and reports are responding normally.
Does anything need my decision?
1 change waiting for youAdd patrol exceptions to incident log
Needs you and Emeka Obi, expires 18:00
Review and decideIs anyone handling an incident?
1 open, being handledSMS alerts delayed on one network. Minor, WhatsApp unaffected.
- Handled by
- Aspian, Ifeoma N.
- Next update
- By 11:30, here and on WhatsApp
Is our evidence current?
1 item staleThe reports database was last restore-tested 9 days ago. A drill is booked for tonight.
Your phone answers four questions first.
Owners don’t need a dashboard of graphs. When you open Aspian Cloud, it answers what you came to ask, in this order. Deployments and logs are a tap away if your role allows.
- 1
Are our applications running normally?
One answer for all your apps, then the detail if you want it.
- 2
Does anything need my decision?
Changes waiting for you, who else must approve, and when each expires.
- 3
Who is handling the incident?
A named person, how serious it is, and when you’ll hear next.
- 4
Is our evidence current?
What is stale or missing, and what is already booked to fix it.
The Trust Page shows what the platform saw, and when.
It is computed from the records of the platform that runs your software: storage inventory, restore drills, the audit trail and telemetry. Nobody types a fact into it, including us.
Kings Guards: evidence of control
Scope: whole organisation, 3 production apps
Snapshot signed today 11:22
Verify offline with key 3F9A C21E
Residency
Databases, volumes, backups, logs and build artefacts for 3 apps stored in Lagos
Observed today 10:00
All production resources. Messaging providers outside Nigeria are listed, with what they receive.
CurrentRecovery
reports-db last restored from backup on 28 Oct, checked row by row
Observed 9 days ago
3 databases. roster-db and portal-db drills are within their 7-day window.
StaleChange control
3 production changes in November, each with its required approvers. 1 blocked agent attempt
Observed today 11:06
Production only. Previews are excluded.
CurrentReliability
guard-roster up 99.97% over 30 days. 99.6% of alerts reached a person within 60 s
Observed today 11:00
Measured from inside the cell and from one external probe.
CurrentAccess
No access review recorded for client-portal this quarter
No record
Named users and operator grants for all 3 apps.
MissingExit
Export drill on 21 Oct: guard-roster ran from its export on an independent server in 38 min
Observed 16 days ago
Not covered: DNS changes, moving the WhatsApp number, re-entering external credentials.
Current
Partner-attested, not observed by the platform
Attested by partnerSigned by the partner. Aspian checks the signature and the dates, not the underlying service.
- Private connectivity to the Lagos cellValid 1 Nov to 31 Jan, signature valid
- Physical protection of the cell facilityValid to Mar 2027, signature valid
Share links
| Audience | Shows | Status | Expires |
|---|---|---|---|
| Board pack, November | Signed snapshot, 6 Nov 11:22 | Active | 30 Nov |
| External auditor | Live page | Expired | 1 Nov |
| Regulator review | Signed snapshot, 14 Oct 09:00 | Revoked | 14 Nov |
- Observed, with coverage and freshness
- Each fact says when it was observed and what it includes. Against its window it reads current, stale or missing. Nothing old is carried forward quietly.
- Signed snapshots
- Freeze the page for an audit. The snapshot is signed, so an auditor can verify it offline against our published key.
- Links that expire
- Share a live page or a snapshot with your board, auditor or regulator. Each link has an end date, and you can revoke it sooner.
Facts that come from partners, such as connectivity or physical protection, are signed by the partner and kept in their own section. We check the signature and dates, and say so.
A record that shows if anyone edits it.
Every plan, approval, rejection and change joins your organisation’s audit trail in order. Each entry carries a hash of the one before it.
- Editing or removing an entry breaks the chain, and verification shows where.
- Every hour the chain is anchored to write-once storage, so a database administrator can’t rewrite history quietly.
- The Trust Page and evidence packs are built from this trail, not from notes.
Audit trail, Kings Guards
Chain verifiedChange applied to guard-roster production
#4182, 11:06
hash 4b7a 19e2 follows c03f 77d1
Approved with passkey by Emeka Obi
#4181, 11:05
hash c03f 77d1 follows 81aa 0b5c
Approved with passkey by Ngozi Okafor
#4180, 10:42
hash 81aa 0b5c follows e5d0 3a94
Plan 7Q2F submitted by Tunde Adeyemi
#4179, 10:31
hash e5d0 3a94 follows 2c61 f80e
AI agents get the same rules as your staff, and some more.
Agents work through plans, like everyone else. Each action has a risk class, and the class decides who must approve it. These rules apply in every edition.
- 1
Read
Logs, metrics, settings, costs
Runs automatically
- 2
Reversible
Preview deploys, scaling within budget, rollback
Runs automatically and is logged
- 3
Production change
Production deploys, settings, database migrations
Behind a canary that rolls itself back, or with a person’s approval
- 4
Irreversible
Deleting data, turning off backups, moving data between countries
A person’s passkey. Two people for regulated organisations
What the agent has read follows its plans.
Logs and customer content can carry instructions planted by someone else. Once an agent has read them, its plans need a person before they can touch production.
- Secrets stay out of sight
- An agent can use a secret through a handle. No tool returns its value, with or without approval.
- Limits on how fast it can act
- Each agent key has a cap on plans per hour. Three failed attempts in a row pause the key and alert the owner.
- 1Marked
The agent reads the reports-db logs
Anyone can write text into a log, so the session is marked as having read untrusted content.
- 2Still marked
It opens a new session
The mark travels with the agent’s plans, so a fresh session doesn’t clear it.
- 3Sent for approval
It plans a change to reports-db
A marked plan can’t make a production or irreversible change without a person’s approval.
- 4Not run
Emeka Obi rejects it
Nothing runs. The blocked attempt appears under change control on the Trust Page.
Evidence packs, mapped to the frameworks you answer to.
An evidence pack gathers platform records for a period and maps them to a framework’s requirements, so your assessor starts from records instead of screenshots.
| Framework | Records the pack draws on |
|---|---|
| NDPA 2023Nigeria Data Protection Act | Storage locations, disclosed processors outside Nigeria, access records and change approvals. |
| UK GDPRUK General Data Protection Regulation | Storage locations, disclosed international processing, access control and restore evidence. |
| ISO/IEC 27001Information security management | Records for change management, backup, logging and access control. |
| NHS DSPTData Security and Protection Toolkit | Backup and restore drills, access records and incident history. |
A mapping helps an assessment; it doesn’t replace one. Whether your organisation meets a framework is for you and your assessor to establish. We don’t claim it for you.
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.