What is Noset?

Noset lets AI agents such as Claude Code work on your systems while the actions that matter wait for a person. You decide which actions those are; Noset holds them until the right people approve, and records every decision as signed evidence.

The parts

• The gate runs on a Linux server next to your agents. Each agent runs inside the gate’s sandbox, a small virtual machine with no network of its own: every request it makes leaves through the gate.
• Rules say what happens to a request: allow it, ask a person first, or deny it. A rule matches an HTTP API call, such as DELETE /users/{id} on your customer API; every tool the agent uses, from curl to an SDK, sends its calls through the gate.
• Approvers decide in the Noset web app, in Slack or in Microsoft Teams. A held request continues the moment it is approved, exactly once.
• Evidence: every request, decision and rule change is written to a hash chain signed by your organization. You can check it yourself, offline, with noset verify.

Where Noset runs

• Noset Cloud at app.noset.ai: we run the server; your gates connect to it.
• On-prem: you install the Noset server in your own network with one command; nothing leaves it. The gate is the same in both.

A request, step by step

1. The agent calls DELETE https://api.example.com/users/12345.
2. The gate matches the request against your rules: deleting a user is ask.
3. The request waits. Approvers see what the agent wants to do and, when the agent said so, why.
4. An approver clicks Approve. The gate sends the request once, and the agent gets the answer as if nothing had happened.
5. The evidence names the agent, the request, the rule, the approver and the time.

Next: install the gate.