A fleet of agents, working inside your rules, 24/7.

Each project gets its own agents. Every action they take passes the same deterministic checks.

Request access See how it works
How it works

Set up agents in plain words.

Describe the job. Hinzel drafts and tests it. Nothing goes live until a person approves.

  1. 01

    Say what you want

    In Slack or web chat, the way you would ask a colleague.

  2. 02

    Hinzel drafts and tests it

    It writes the rule, runs the tests and replays last week's events.

  3. 03

    A person approves it

    A project admin reviews the change. Then it runs the same way every time.

The engine

Agents decide what to do. Rules decide what they may do.

Every call an agent makes goes through one gateway. Rules you can read allow it, send it to a person, or block it.

How the engine works

Exact triggers

Runs start on the events you describe, and nothing else.

on: jira.issue_created
if: priority == "P1"

Business hours

Schedules and timers follow your calendar, time zones and holidays.

Thursday is a holiday

Multi-step rules

Follow an issue through its states, with timers like "2 business hours without a reply".

waiting → escalate → done

Proven before it ships

Behaviour tests and replays of past events run on every change.

$ test · ✓ 48 passed
Integrations

Works with events from anywhere.

Any event from the outside world can start a run: a message, a ticket, a webhook or a schedule. Agents act back through the same checked gateway.

Slack GitHub Jira Zendesk Any webhook Schedules Any MCP server hinzel rules · gateway Reply in the thread Open a pull request Update the ticket Call any MCP tool

Events in

  • Slack
  • GitHub
  • Jira
  • Zendesk
  • Any webhook
  • Schedules
  • Any MCP server

Checked actions out

  • Reply in the thread
  • Open a pull request
  • Update the ticket
  • Call any MCP tool
See all integrations
For teams and orgs

Every project on its own terms, under one policy.

  1. 1
    Scoped to each projectIts own agents, tools, people and memory.
  2. 2
    Acts as the right identityAs Hinzel, or as the person who asked.
  3. 3
    Approvals where you workApprove or decline in Slack or web chat.
  4. 4
    Budgets and tracesSpend limits per project, and a trace for every reply.
All features
Agents together

Agents that do real work, together.

Real workspaces, shared outputs, lasting memory.

support-desk builder rca.md · v3 support-desk hands the root cause to builder

A workspace for every run

Each run gets its own sandbox, branch and files.

Memory that knows its sources

Project memory records where each fact came from.

Refunds over $200 need Anafrom #billing, Oct 3
billing-api deploys on Tuesdaysfrom README
Security

Safe by default.

Agents never hold your keys, code runs in a sandbox, and your words stay out of the logs.

Agents never hold keys

The gateway adds credentials to each call. Agents never see them.

Encrypted at rest

Secrets use envelope encryption with keys held in KMS.

Code in a sandbox

Sandboxes run under gVisor, apart from the host.

Your words stay out of logs

Logs keep what happened, not what people wrote.

How Hinzel keeps you safe

Put a fleet to work this week.

Hinzel is in early access. Tell us about your team and we will set up your first project with you.