Audit

Audit the build against what you agreed to build.

Freeze the requirements everyone signed off on. Atrix then shows, requirement by requirement, what has work behind it, what has none, and what changed after the freeze.

Free plan · no card · two seats included

atrix.dev/dashboard · baseline · frozen

What it does

Answers you can check

Every state on the audit is computed from your records. No model decides whether a requirement is covered.

  • Frozen baselines

    Take a snapshot of the agreed requirements. Later edits do not rewrite it, so you can always compare today with what was promised.

  • Five plain states

    No work, in progress, work done, dropped since and record gone. A dropped requirement reads as a decision; a missing one reads as a gap.

  • Work done is not verified

    When every issue against a requirement is finished, Audit says the work is done — and deliberately stops short of calling it checked.

  • Gaps become backlog

    Accepted requirements can be broken down into backlog work, each item linked back to the requirement it serves.

  • Repository signals

    Link a GitHub repository to see the last push, open pull requests and issues, and commits over the past 7 and 30 days.

  • What is actually live

    Link a Vercel project to see the production build state and which deployment is serving, even when the latest build failed.

How it works

Set up an audit in three moves

These are the setup steps the project's Audit panel walks you through.

  • Agree the requirements — Write them by hand or let a Develop run draft them, then accept the ones you mean to build.
  • Link and freeze — Link a repository, complete the project's identity, and freeze a baseline of the accepted requirements.
  • Read the coverage — Open the baseline any time to see each requirement's state, and follow the gaps into the backlog.
atrix.dev/dashboard

Plans

Audit is on every plan

Coverage is computed from your records, so it uses no AI runs. Plans differ in how many private repositories you can connect.

  • Free$0/mo

    Audit on up to 3 projects. Link public repositories by URL; private ones need a paid plan.

  • Builder$39/mo

    1 connected private repository across the workspace, and unlimited projects.

  • Studio$149/mo

    10 connected private repositories, for studios running several products.

FAQ

Questions, answered

Does Audit scan my code for vulnerabilities?

Not today. Audit compares the work against the agreed requirements and shows repository and deployment signals. It does not run static analysis or dependency scans, and it never reports findings it has not verified.

What is a baseline?

A frozen copy of the requirements at the moment you agreed them. Coverage is measured against it, so later edits and deletions show up instead of disappearing.

Why does it say “work done” rather than “complete”?

Because finished issues are not proof the requirement is met. Audit reports what the records show and leaves the verdict to a person.

Which GitHub access does it need?

Public repositories need none — paste the URL. Private ones use a GitHub connection that only makes read requests; see the GitHub integration page for the exact scopes.

Does running an audit use my AI runs?

No. Coverage involves no model. Only drafting requirements or breaking them into work with the agent uses runs.

Find out what was agreed and forgotten.

Freeze your first baseline on the free plan, in any of your three projects.