The developer build is free and open source. For teams, we start with a free eight-week pilot shaped to your use case, then price it to the size of your fleet. No public number yet, because the pilots set it.
Every paid plan starts with a free eight-week pilot. Pricing is set with you, to the size of your fleet.
The core is deterministic and runs in process, with no model on the block path. Credentials and hard rules are always decided that way. Only genuinely ambiguous cases can escalate to a model, and you choose which one. It runs in your boundary, never on Tuent's.
No. Checks run in the same process as your agent and finish in well under a millisecond. There is no network hop, so the overhead is not something you or your agents will notice.
It is stopped at the pre-execution checkpoint before it runs, so the side effect never lands. The agent gets a denial, the event is written to the audit trail, and on a soft flag the developer can release it in one click.
You do not write rules. Sentinel learns from the actions your developers approve and deny, then recommends a specific policy in plain language for a person to approve. Credentials and other hard rules are blocked by default from day one.
Claude Code today, through a native hook. That is the only live integration to start. Support for additional runtimes is on the roadmap, and the policy model is built to extend without forking per tool.
No. Sentinel runs on-prem. Even model escalation uses an endpoint you bring, inside your own boundary, so nothing about your agents, code, or actions reaches Tuent.