Free
$0
For trying it out and small projects.
- Hooks
- 5
- Events a month
- 10,000
- Event history
- 7 days
- Agent generations a month
- 50
Pricing
You pay for events processed, not for features: every plan includes the CLI, MCP tools, provider presets, the dashboard, failure alerts and team invites.
$0
For trying it out and small projects.
$29/ month
or MX$499 · €27 a month, tax included
For hooks that run part of your production stack.
Billing runs through Stripe: upgrade, invoices, payment method and cancellation are all in the Usage page. Checkout charges in your local currency where one is set (MXN, USD or EUR), with tax included. Cancelling returns the workspace to Free at the end of the period.
Hooks
Events per month
Event retention
Hosted agent generations a month
CLI, TUI and MCP tools
Dashboard, replay and test events
Provider presets and quiet hours
Failure alert emails
Team invites and roles
Each request accepted at your /h/<id> URL counts once, whether your conditions let it through, skip it, or quiet hours defer it. Retries to a destination, duplicate deliveries from the sender, and the replays and test events you start from the dashboard do not count. The usage page shows the running total and resets on the first of each month (UTC).
The usage meter on the dashboard and the Usage page warns you at 70% and 90% of your event allowance. Going over does not drop webhooks: events keep flowing, and the response your sender gets for an over-limit event carries an x-hooksmith-quota: over header. The Usage page shows your count against the allowance and has an Upgrade to Pro button.
Creating a hook past your plan's limit is refused, so you need to delete one or upgrade first. Existing hooks are not affected, and updating or redeploying them is always allowed.
Upgrade from the Usage page. It opens a Stripe checkout and the workspace moves to Pro once the payment confirms. Manage billing on the same page covers invoices, payment method and cancellation. After cancelling, the workspace returns to Free at the end of the period.
Yes. A hook is a plain hooksmith/v1 YAML file that you keep in your repo. The cloud runtime executes it. Delete a hook and its URL stops working; your YAML stays yours.
No. The CLI and TUI work locally: describe, test and iterate on your machine. You need the cloud when you want a public /h/<id> URL that receives real traffic.
By default, yes, so you can inspect and replay them. The history window for each plan is in the table above. Set logging.retainPayload to false in a hook to keep payloads out of storage. Such events cannot be replayed.