Carbon & asset evidence for field operations

Evidence your auditor can sign, captured where the work happens.

IFRS S2 reporting becomes mandatory in Ghana from 2027. ZEA AssetOps turns the work your technicians already log into signed evidence packs anyone can verify.

Activate your invite

Invite-only during pilot onboarding — book a demo and we'll send one. 14-day trial, no card.

A technician in a hard hat and hi-vis vest at a diesel generator, logging the work in the ZEA AssetOps app on his phone.

The ZEA AssetOps technician view: today's work orders, leak counts and one-tap scan, report fault, new work order and raise leak actions.

Every pack is Ed25519-signed — verify one yourself.

The public key is served from this domain. Checking a pack needs no account and no call to us.

Public signing key How to verify a pack

Hash-chained audit log

The database rejects edits and deletions outright.

Offline-capable field app

Work logs without signal, syncs on reconnect.

Priced and billed in GHS

Cedi pricing, collected by mobile money.

How it works

Capture in the field. Control the record. Prove it to an outsider.

The pack an auditor reads is generated from work that already happened — nobody assembles it at quarter end.

The technician app's quick actions — scan, report fault, new work order, raise leak — above today's assigned work order for a generator. — Technician app

Capture

Scan the asset, photograph the evidence

A scan opens the asset's record; a photographed document is read, its values offered for confirmation.

One-tap scan, fault, work order, leak
Queues offline, syncs on reconnect
Photos hashed (SHA-256) at upload
Receipt, bill, meter, nameplate — read, you confirm

Control

Approvals on a tamper-evident chain

Every change lands in an append-only audit log where each row carries the hash of the one before it.

Append-only at the database level
Hash chain re-walked nightly
Actor, timestamp and values on every entry

The reports surface, generating evidence packs with content hashes and cryptographically signed PDFs alongside JSON exports. — Reports — signed packs

Prove

Signed packs your auditor can check

Packs export as signed PDF plus JSON, prepared with reference to IFRS S2 and VSME.

Detached Ed25519 signature in a sidecar
Factor source and GWP set printed in the PDF
Verifiable offline with openssl

One record, end to end

How a work order becomes a signed emission record.

Not a case study — every step below is something the platform does today.

1
Scan
A technician opens the asset, not a form
A QR scan raises the work order against the generator on the spot — with or without signal.
2
Work
Everything lands on one record
Diagnosis, photos, run hours and diesel land on the same asset — the receipt is read, litres offered, driver confirms.
3
Convert
Litres become Scope 1, with provenance
Fuel volume × a versioned emission factor — source, version and GWP set printed beside the figure.
4
Sign
The pack is signed, and checkable without us
Export yields a PDF and a signed digest your auditor verifies offline with openssl. One changed byte fails.

What lands in the auditor's folder

The pack, and its sidecar

SignedEd25519

Two files: the PDF, and the sidecar that makes it checkable by anyone holding the public key.

evidence-pack.sig.json

sidecar

{
  "signature": "<base64 Ed25519 signature>",
  "sha256":    "<hex digest of the PDF bytes>",
  "keyId":     "<16-hex-char key identifier>",
  "algorithm": "Ed25519",
  "signedAt":  "2026-08-05T09:14:22.000Z"
}

A deployment without a signing key stamps its packs unsigned — not for audit use. An unsigned pack says so itself.

Frameworks & footing

What we are aligned to — stated exactly.

Packs are prepared with reference to these frameworks — deliberate wording, because no one has certified this platform.

IFRS S2

Mandatory from 2027

Adopted by ICAG in 2024, mandatory for listed and regulated entities from 2027. Packs prepared with reference to IFRS S2.

The Ghana roadmap

GHG Protocol

Factors follow the Corporate Standard — source, version and GWP set travel with every figure.

VSME

Basic Module pack prepared with reference to the EU SME standard. Missing datapoints are stated as omissions.

GHS billing

Priced, invoiced and collected in cedis, with mobile money.

Offline-capable

The field app records work without a connection.

Ed25519-verifiable

Detached signatures, verifiable offline against a published key.

Pilot package

A pilot that ends with a real signed pack.

One workflow, your own field team, and an exported evidence pack at the end — three weeks, either way you learn something concrete.

7 days

Workspace seeded with your data

2 weeks

Your crew running it on site

1 pack

Exported, signed, reviewed

A technician and a supervisor in hard hats reviewing work together on a phone beside a diesel generator.

Scope

Narrow enough to finish, real enough to argue about

1
We import your assets and stand up the workflow that is already causing trouble.
2
Labels, roles and report templates are configured against your sites, not a sample tenant.
3
Your crew runs it for two weeks on their own phones.
4
You export the pack and walk it through with whoever has to defend it.

A data processing agreement is available before any of your data is loaded.

Security & verification

Don't take our word for any of this.

The point of signing a pack is that our assurances stop mattering — here is the command that checks one.

SignedEd25519

Detached Ed25519 signatures

Each pack is signed as Ed25519(sha256(pdf bytes)) — prove the file is unmodified before trusting a figure in it.

Append-only at the database

Postgres triggers reject UPDATE and DELETE, so not even an administrator can quietly rewrite history.

A public key, on this domain

Served from /.well-known/assetops-signing-key. Pin it once and never ask us for anything again.

Chains re-walked nightly

A break is an alert, not something discovered during an audit.

verify a pack offline

openssl

# 1. The PDF's hash must equal the sidecar's sha256 field
shasum -a 256 report.pdf

# 2. Verify the signature over that digest
echo -n "<sha256 hex>" | xxd -r -p > digest.bin
echo "<signature base64>" | base64 -d > sig.bin
curl -s https://<domain>/.well-known/assetops-signing-key \
  | jq -r .publicKeyPem > pub.pem
openssl pkeyutl -verify -pubin -inkey pub.pem \
  -rawin -in digest.bin -sigfile sig.bin
# -> "Signature Verified Successfully"

Step-by-step verification guide Fetch the public key Raw guide (.md)

Next step

Bring one asset register and one thing you cannot currently prove.

We'll show you the record chained, and the signed pack it exports when somebody finally asks.