What Tracer is
Tracer answers one question about a software project: if someone asked you to prove your requirements are tested, could you? It reads the records you already keep — your Jira backlog and your test results — and tells you which requirements have passing evidence, which have failing evidence, and which have no evidence at all. It shows the record behind every claim and never guesses.
Who it is for
Teams that have to show their work: a release review, an audit, a customer security questionnaire, a regulator. The people who use it are QA managers, delivery leads, and the engineers who get asked "is this tested?" and have to go looking.
What you can do right now, without an account
- Watch the guided demo. A small synthetic backlog with eleven hidden gaps. Tracer names every one and shows why it refuses to publish a status the records cannot support.
- Scan your own Jira export. Paste a Jira search export; get the gaps and a traceability status in seconds. Nothing is stored and no credentials are asked for.
- Read a sample evidence pack. What a full assessment delivers, at three altitudes: the executive summary, the manager's repair queue, and the record-level detail.
What a team can do with an organization key
An organization is set up by hand today and receives an API key. With it, a team's CI pipeline can:
- Store an assessment of its Jira backlog — the requirement references and the gaps, never the ticket text.
- Send test results after every run, in any of three standard formats: OpenTelemetry traces, a CTRF report, or JUnit XML. Tracer links each test to the requirement it names and keeps the link's reasoning.
- Ask for the verdict: three counts that always add up — verified, falsified, unknown — over the latest requirements, with stale evidence set aside and named. The verdict is signed, and anyone can check the signature against a published key without asking Tracer.
- Gate a release on it: one command in CI fails the build when the verdict got worse than the last one recorded.
The API is described in the repository README; a key is issued by the founders while sign-in is being built.
What it costs
$39 per month per seat. Seats are provisioned by hand until sign-in ships. A fixed-price audit-readiness engagement is available as paid onboarding.
What is not built yet, as of 2026-09-11
| Missing | State |
|---|---|
| Sign-in for people | Organizations and keys exist; a person cannot yet sign in with a browser. Passkey sign-in is the next build. |
| Pages for teams | The verdict, the evidence list, and the findings are reachable by API today; the pages that show them on a phone follow the sign-in. |
| Automatic re-checks | Today a verdict is computed when asked. Webhooks from your repository and a nightly snapshot are next. |
If something looks broken
Pages under /api/ and /health answer in JSON because machines read them; a browser shows that as raw text, not an error. The founders' cockpit at /cockpit/ is a small installable page for two people and is not the product; if it says metrics are unavailable, it could not reach the service from your device. The service itself reports its state at /health.
A LumiraGroup product. This page describes the service as deployed at version fc931641.