Company

We built this because we needed it.

untactit started as internal tooling for a team whose agent instructions had quietly scattered across four vendors and a dozen machines. It turned out not to be a problem unique to us.

The problem

Why we're building this

Agent instructions started as personal files. Someone's prompt, someone's rules file, someone's custom setup. Then they became load-bearing — they decide what an agent will and will not do on behalf of the company.

The tooling never caught up. There is no inventory, no approval, no record of who changed what. Version control was solved for code thirty years ago. For the instructions running agents against production systems, most teams are still on shared folders and hope.

What we kept running into

Nobody knew the full inventory
Different answers from different people
Changes shipped without review
Found out when behavior changed
Leavers took context with them
Assets in personal accounts, gone
Security reviews stalled
No answer to "what can it see"

How we work

Four things we decided early.

These shape the product more than any roadmap does. They also explain some of what we have chosen not to build.

Vendor-neutral

We do not favor a model or platform. The moment we take a side, we stop being infrastructure and become a bet on someone else's roadmap.

Read-only by default

Connecting a platform never changes what is there. Nothing moves until someone decides it should. Trust is easier to keep than to rebuild.

Say what is missing

We state our position on what is built and what is not. Overstating gets found out in the first serious review, and it costs more than the deal it wins.

Boring where it counts

Standard REST, standard SSO, standard audit formats. Novelty in infrastructure is a cost your team pays, not a feature.


Where we are

Where we are.

The product is in daily production use. We are deliberate about which enterprise capabilities we build next, and we scope that with the teams evaluating us rather than guessing.

If a capability your review depends on is not in place yet, you will hear it from us before a procurement cycle rather than during one. The security page states our certification position plainly.

Built for ourselves

Internal tooling, one workspace, no intention of shipping it.

Opened to a few teams

Turned out the problem was common. Multi-tenancy, roles, audit log.

Now

Taking on teams who want to shape what gets built next.


Stop guessing what your agents are running.

Connect one workspace and see every skill, rule, and memory your team has in play — in about ten minutes.

Start free→ Talk to us

No credit card. Works with what you already run.