1. Say what you want
Describe the job in Slack or web chat.
The platform for AI agents that run your team's work.
The layer where agents and all your tools work together. Say what you want in plain words, and a deterministic engine makes sure it happens exactly that way.
Request accessSet up agents in plain words.
Describe the job. Hinzel drafts and tests it. Nothing goes live until a person approves.
2. Hinzel drafts and tests it
It writes the rule, tests it and replays past events.
3. A person approves it
An admin reviews the change. Then it goes live.
A deterministic engine under every agent.
Rules that run the same way, every time.
Proven before it ships
Checked, tested and replayed before anyone approves it.
Every call checked
Allow, ask a person, or block.
Triggers on exact events
Only the events you describe.
Schedules and business hours
Cron that knows your calendar.
Watches from a conversation
"Ping me when this PR merges."
Rules that remember
Follow a ticket through its states, with timers in business hours.
Records your agents keep
Typed data, with a history of who changed what.
Built for teams and whole orgs.
Every project on its own terms, under one org policy.
Scoped to each project
Each project reaches only what it's given.
Acts as the right identity
As the bot, or as the person who asked.
Approvals where you work
One click in Slack or the console.
Budgets per project
Spend limits for each project.
Traced end to end
Any reply, back to its cause.
Agents that do real work, together.
Real workspaces, shared outputs, lasting memory.
A workspace for every run
Its own branch and sandbox. Sleeps when idle.
Your model, your plugins
Pick the model. Pin the plugins.
Agent to agent
Hand-offs with a hop limit.
Artifacts that travel
Versioned, with lineage.
Memory that knows its sources
Every fact, with its source.
Safe by default.
Agents never hold your keys, code runs in a sandbox, and your words stay out of the logs.
No credentials in the workspace
Agents act through the gateway. Secrets stay encrypted with KMS.
Code runs in a sandbox
Chat sandboxes run under gVisor, apart from the host.
Message text stays out of logs
Logs keep ids, not words. Analytics drop personal fields.
Connects to the tools you have.
Use the built-in connectors, add any MCP server, or send events in with a webhook.
Built-in connectors
Events come in and actions go out, with replies in the same thread.
Any MCP server
Add its URL. Its tools pass the same checks as every other call.
Webhooks in and out
A signed webhook starts a run. Outbound webhooks report the result.