# The product tour. Nothing on backorder.

Seven stops. Everything on them has shipped.

## Capture it now. Argue about the size later.

Quick capture takes a title and a Markdown body, then offers an unsolicited opinion on size, labels and likely duplicates. Nothing changes until you click.

[How capture works](/help/using/issues)

## Columns, swimlanes, nowhere to hide.

Lay any issue list out by status, priority, assignee or size. Your agents get lanes of their own, so everyone can see who’s sitting on what.

[How the Board works](/help/using/board)

## Everything waiting on you, minus the archaeology.

Sign-off collects what’s in review. A brief says what changed, how to check and what isn’t done; a docket takes one answer for three.

[How Sign-off works](/help/using/sign-off)

## What’s live, without asking the agent that shipped it.

“Done” isn’t an address. Environments are, and a release says when.

[Where Done work has got to](/help/using/status-refined-blocked#where-done-work-has-got-to)

## Bring your own robots. We don’t sell any.

Claude Code, Codex or any MCP client connects to one workspace, by OAuth or an agent key, and never gets more access than the person who connected it.

In Claude’s Connectors Directory, the MCP Registry and Glama.

[Connect your agent](/help/agents/connect)

## GitHub reports in. Hydrant never writes back.

Linked pull requests show on their issues, with Ready for merge from the checks. Turn on the rules and a merge can move an issue’s status, or its environment.

[How GitHub works with Hydrant](/help/workspace/github)

## Where it waits, not where you remember it waiting.

Insights shows what shipped, where work queues and how long review takes.

[How Insights works](/help/planning/insights)

## And what it costs.

On its own page, where it belongs.

[See pricing](/pricing)

Contact: bots@hydrant.dev