Skip to main content
Hookie has four plans: Free, Starter, Pro and Team. A plan belongs to the workspace and sets the limits of every project in it. How to change plans is in Billing, and prices are on the pricing page.

Per plan

Everything in this table is counted across the whole workspace, not per project. Starter, Pro and Team accept 10% over the event and delivery numbers before they bite; Free stops at the number. Single sign-on (SAML or OIDC) is planned and not available yet, on any plan. Starter is $2.99 a month and **Pro** is $9.99 a month, both flat prices for the workspace. Team is $39.99 per member, per month: its seat count follows the number of people in the workspace, as they join and leave. See Billing. Nothing is billed as overage on any plan: past a limit, new events are refused, deliveries held and AI calls refused, as described below, so a paid plan never charges more than its price.

Retention after a downgrade

When your workspace moves to a plan with a shorter retention window, Hookie keeps your event data on your previous plan’s window for 7 more days. That happens when you downgrade or cancel a paid plan, when a subscription ends after failed payments, when a free trial ends, or when Hookie support changes your plan. After those 7 days, the new plan’s window applies: event data older than it is permanently deleted by the automatic cleanup, which runs every five minutes. That covers records, raw submissions, delivery history, the AI call log, workflow runs and AI trigger runs. For example, moving from Pro (90 days) to Free (30 days) keeps 90 days of data for 7 more days. After that, anything older than 30 days is deleted.
  • Downgrade again within the 7 days: the longest window still applies, and the 7 days start again. Pro → Starter → Free keeps 90 days until 7 days after the move to Free.
  • Upgrade to a plan whose retention is at least as long as the window being kept: the window ends, because the new plan keeps that data anyway.
  • Upgrade to a plan with a shorter window than the one being kept: the window runs on unchanged. When it closes, the new plan’s window applies.
  • Closing a workspace works differently. See Close the workspace.
While the window is open, Home shows a warning with the date the older data will be deleted. Below it are two buttons: Export & closure, where an owner or admin can download everything as one JSON Lines file (see Export all data), and Plan & billing, where the owner can upgrade. The API returns the window on GET /admin/api/me:
retention_days is the window being kept, plan_retention_days is the current plan’s, and ends_at is when the window closes. retentionGrace is null when no window is open.

The same on every plan

Monthly quotas

Every monthly quota resets at 00:00 UTC on the 1st of the month, whatever day your subscription renews. Home shows this month’s events, deliveries and AI tokens against your plan, with a warning from 80%.
  • Events. Every accepted submission counts once, however many records it makes, and so does every event a cron trigger, WebSocket trigger or database source writes. A database source row counts once, when it is stored; one Hookie could not store is not counted (see Database sources). Refused requests and recognised duplicates are not counted. The count is exact: one counter per workspace. Past the ceiling, a new event is refused with 429 and not stored. The answer carries "reason": "quota_exceeded", reset_at, an upgrade_url and Retry-After: 3600. A trigger or source shows the refusal instead.
  • Deliveries. One delivery is one event sent to one destination, counted when it is created. Retries are free, and replays count. Past the ceiling, deliveries are held, not dropped: see The delivery allowance and holds.
  • AI tokens. The input and output tokens of every AI call count: AI trigger runs, and workflow call_ai and agent_call steps. There is no grace: once the allowance is used, the next AI call is refused before the model runs, and its step or run fails. See AI allowance.
  • AI trigger runs. Each AI trigger run counts once it starts running; one that fails is not counted. Past the quota, a new run fails.

The burst limit

Each credential has a burst limit of about 100 requests per 10 seconds, the same on every plan:
  • on ingest, per endpoint URL and per ingest key, and per Data API key;
  • on /admin/api and /mcp together, per API key, per connected agent and per person signed in to the console.
Over it, the request is refused with 429 and a Retry-After: 10 header. The burst limit is a best-effort burst guard, not an exact count. It runs on Cloudflare’s rate limiting, where each Cloudflare location counts separately and its count catches up within seconds. So a short burst can get through above 100 before the first 429, and a sender whose requests reach several Cloudflare locations is counted once at each. It is there to stop a runaway sender, not to meter one. The monthly event quota is separate from it, and exact. The customer portal’s API has the same kind of guard, at about 60 calls a minute per portal token.

When you reach a limit