Get started

The control plane that stops AI agents breaking your rules

Your AI agents are already acting. Prove they were allowed to.

Companies are letting AI assistants issue refunds, open customer records and send data outside the business. It happens thousands of times a day, and the assistants decide on their own. IndexTracer sits in front of every one of those actions, stops the ones that break your rules, and keeps a record of all of it that nobody can quietly rewrite.

Working software today. One reply from a person, no newsletter.

Or see how it works ↓

11frameworks covered
154requirements answered
24hkeeps working if we go down
Decisions · acme-prod Live
14:02 Refund assistant → issue a $4,200 refundabove the $500 limit set for this assistant Blocked
14:02 Support assistant → look up a customer's contact detailspermitted for this assistant Allowed
14:02 Claims assistant → file a document with medical detailssent to a named person to approve first Needs a person
14:02 Reporting assistant → send a report to a supplierapproved destination · no sensitive data found Allowed
14:02 Refund assistant → email a customerthe message contained a card number Blocked
14:02 System → today's record sealed1,204 decisions · signature applied Verified

The gap

Three questions nobody can answer yet

An AI assistant is neither an employee nor ordinary software. It decides in the moment, it holds the company's passwords, and by default it leaves nothing behind that anyone can review.

What AI do we even have?

Teams build these in days. Nobody keeps a list, nobody rates how much damage each one could do, and the security review happens after something goes wrong.

What is it allowed to do?

The rules live in a document. Nothing actually stands between the assistant and the refund button, the customer record, or the message leaving the building.

Can we prove any of it?

The only record is a log that anyone in IT could edit. That is the first objection an auditor raises when you offer it as evidence.

How it works

A checkpoint at the door, and a logbook nobody can alter

Every time an assistant tries to do something real, the request goes through the checkpoint first. It looks up the rules for that specific assistant and makes one of four decisions, before anything happens.

Allow

Within the rules

The action goes ahead, and the decision is written down.

Block

Outside the rules

It never happens. The assistant is told no, and so is your record.

Ask a person

Borderline

It pauses and waits for a named human to approve or decline.

Watch only

Still learning

Nothing is blocked yet. You just see what would have been.

It checks before, not after

This is not a report you read tomorrow about something that already happened. The action does not happen unless it is permitted.

Your AI never holds the keys

Passwords stay at the checkpoint and are attached to approved requests only. The assistant never sees them, so a misbehaving one has nothing to leak.

You start in watch-only mode

For the first few weeks it blocks nothing and simply shows you what it would have stopped. You turn on enforcement when you are ready. Nothing breaks on day one.

Read the whole thing in plain words, including how it gets set up →

What you get

Paperwork that fills itself in, from a record that resists you

Every decision goes into the logbook, whether it was allowed, blocked, approved or declined. Each entry is mathematically linked to the one before it, and every day is sealed with a signature.

A record that cannot be rewritten

Alter or delete a past entry and the chain visibly breaks. Not even your own IT administrators can change history without it showing.

Compliance answers, not a questionnaire

The system fills in your obligations automatically, showing which requirements you meet, which you do not, and the actual evidence behind each answer.

Give auditors a pass, not a folder

Issue temporary access that expires. Your auditor sees only the parts you choose, and everything they look at is recorded too.

Most compliance software watches and reports. This one steps in and stops things, and because it is the thing doing the stopping, its records are evidence rather than claims.

Coverage

Eleven rulebooks, answered from what your AI actually did

Each requirement is checked against how the system really behaves, and marked met, partly met or not met, with the evidence attached. Not a checklist somebody ticked.

NIST AI Risk Management Framework 1.023 requirements
SOC 2: what enterprise buyers ask for14 requirements
NIST SP 800-53: the US federal baseline18 requirements
ISO/IEC 42001: AI management systems13 requirements
EU AI Act15 requirements
GDPR: automated decisions12 requirements
HIPAA: patient data15 requirements
SOX: financial reporting controls12 requirements
PCI DSS: card data15 requirements
US state AI laws (CO, CA, IL, NYC, TX)12 requirements
Industry packs from specialist partners5 requirements

154 requirements in total. Start with the two most people need, SOC 2 and the EU AI Act, then turn on the rest when you need them.

11 frameworks. 154 requirements. Running in production today.