How it works
Three layers, in order. Each one only makes sense once the one before it is in place.
Layer one
You can't govern what you can't see. untactit reads the folders and vendor accounts your team already uses and builds a single index of every asset in play.
Who can do what
| Role | Edit | Deploy | Approve |
|---|---|---|---|
| Admin Owns the workspace | ✓ | ✓ | ✓ |
| Approver Reviews and releases | ✓ | ✓ | ✓ |
| Editor Writes and proposes | ✓ | — | — |
| Viewer Reads only | — | — | — |
Roles are enforced on the server. The interface never grants something the backend would refuse.
Layer two
Three roles, not one shared admin account. Contributors propose, approvers decide, and the record of who decided what survives both of them leaving.
Layer three
An approved asset still has to reach the tool that runs it. untactit decides what loads where, for whom, and pushes it — so the version on someone's laptop is the version you approved.
Deployment targets
Integrations
Your assets shouldn't be hostage to whichever model you're using this quarter. untactit stores them in a neutral format and translates on the way out.
Skills, projects, and instruction files.
Rules and workspace configuration.
Skills, memory, routines, and session history.
.github/copilot-instructions.md
Custom instructions and configured assistants.
The open convention read by 20+ agents, adopted by 60,000+ projects.
Anything else, through a documented endpoint.
Connect one workspace and see every skill, rule, and memory your team has in play — in about ten minutes.
No credit card. Works with what you already run.