Microfilm captures your testers' work and structures it into audit-ready proof — and into actionable context for the developers and AI agents fixing what fails. Built for regulated software teams.
Request early access →FedRAMP · CMMC · 21 CFR Part 11 · IEC 62304
The problem
Evidence lives in screenshots and Slack
Testing evidence is scattered across Jira comments, screenshots in tickets, manual spreadsheets, and tribal knowledge.
Traceability is a spreadsheet maintained by hand
The RTM is a doc someone rebuilds before each audit, with broken links and stale references.
Audits reveal the gaps too late
Coverage gaps surface during 3PAO review or FDA inspection, not during the work.
Two loops, one record of truth
Compliance and engineering normally pull from different artifacts. Microfilm produces a single signed record that serves both.
01 — The evidence loop
Testers, QA leads, and auditors need signed proof that every requirement was verified. Microfilm produces it as a byproduct of the work.
02 — The development loop
Developers and AI agents need structured context when something fails. Microfilm delivers it to where they already work — Jira tickets, Slack, and a native MCP server for agents.
The same captured evidence serves both. No duplicate work. No drift between what was tested and what's being fixed.
How it works
Microfilm reads requirements and test cases from Jira, Linear, or Azure DevOps. No migration.
A lightweight desktop app sits beside the browser. Screen, voice, screenshots, and structured comments are captured against the specific test case being executed.
Every verdict is signed by the tester. The evidence log is append-only and tamper-evident.
When a test fails, the linked Jira or Linear ticket gets a structured comment with the requirement, the acceptance criteria, what the tester saw and said, and a link to the evidence. AI coding agents — Claude Code, Cursor, and others — query the same evidence through a native MCP server, so they know exactly what failed, why, and against which acceptance criteria.
Requirements → acceptance criteria → test cases → execution evidence → signatures, exported as an audit package on demand.
Who it's for
Government contractors
Shipping into federal environments under FedRAMP, CMMC, NIST 800-171 / 800-53.
Teams shipping with AI agents
Claude Code, Cursor, and other coding agents fix what testers find. Microfilm gives them the structured context they need — requirement, AC, evidence, prior executions — through a native MCP server. Compliance and AI velocity in the same loop.
Medical device and digital health
IEC 62304, ISO 13485, FDA QMSR, 21 CFR Part 11.
Regulated software generally
Pharma (GAMP 5), aerospace (DO-178C), automotive (ISO 26262), or anyone whose auditors ask for a traceability matrix.
Request access
Microfilm is in early access. I'm working with a small number of teams to make sure it earns its place in your evidence and engineering loops before we open it up.