Feature · Evidence
Microfilm’s signed evidence is tamper-evident test evidence: every event your AI coding agent writes is signed with a KMS-backed key (ES256) and chained into a reel, so any record can be verified offline — without trusting Microfilm — and any later change shows.
Every event written to the MCP server is signed with a KMS-backed key and chained into a reel. The chain is tamper-evident — actor, content, and time fixed at the moment of capture — and any record can be verified offline, so the proof holds up the day someone checks it.
Availability · Included on every plan — signing, chaining, and offline verification are core to Microfilm.
What Microfilm is · Microfilm is the evidence engine for teams and agents: a headless MCP server that AI coding agents write signed test evidence to as they work, paired with a web portal where teams search, trace, and share that evidence. Every event is signed with a KMS-backed key and chained, so any record can be verified offline.
The problem
Console output can be edited, re-dated, or quietly dropped. A spreadsheet of pass/fail can be changed by anyone after the fact, with no trace. When the integrity of your test record matters — and in regulated software it always does — "the build was green" doesn’t hold up.
How it works
When the agent writes an event, it’s signed with a KMS-backed key (ES256). Actor, content, and time are fixed together — not added later, not editable after the fact.
Each record links to the one before it. If anything in a sealed reel were altered, the chain would break and it would show. The history of what was tested, by whom, and what the result was stays intact.
A record carries what’s needed to check its signature and its place in the chain without calling back to Microfilm. Whoever you hand it to can confirm it themselves — integrity you can check, not something you take on faith.
Attributable, time-stamped, append-only records are the shape of evidence regulated environments expect — the same properties teams need when they work toward FedRAMP, CMMC, 21 CFR Part 11, or IEC 62304 review.
Where it fits
Signing turns each event the agent writes through the MCP server into something durable. From there, signed records land in the evidence portal and remain the source of truth the requirements-traceability views are built over.
FAQ
Each signed event links to the one before it, forming a reel. Any change to a sealed record breaks the chain and is detectable, which is what makes the evidence tamper-evident rather than merely stored.
A KMS-backed key using ES256. The private key never leaves the key-management service; Microfilm requests a signature for each event, so the signing material isn’t something the application can leak.
A record carries the signature and chain information needed to check it independently — anyone you share it with can confirm it’s authentic and unaltered without trusting Microfilm or being online to our service.
Yes. Signing, chaining, and offline verification are core to Microfilm and included on every plan. The shared portal, search, sharing, and traceability views are Team-and-up cloud features.
Create an account, connect your agent to the MCP server, and write your first signed record.