FAQ

Frequently asked questions about FixedHook — pricing, limits, privacy, and how it compares to other tools.

FixedHook is a developer-first webhook ingress and debugging platform. It gives every project a permanent webhook URL, a real-time event inspector, replay tools, and a CLI tunnel for local development. See the introduction for the full pitch.

Why not just use ngrok or Cloudflare Tunnel?

ngrok and Cloudflare Tunnel give you a new random URL on every restart. With FixedHook, the URL is permanent. You register my-app.fixedhook.com in Stripe once, and the alias URL never changes — even when you switch from your laptop to a colleague's machine, or move from local dev to a preview deployment. FixedHook also gives you an event inspector, replay, and share links, which those tools don't.

Is FixedHook open source?

The CLI is open source. The relay and web app are not. The CLI source lives in the monorepo at apps/cli.

Where does my data live?

Event payloads and metadata are stored in the region you select when you create your account. In production, FixedHook uses Cloudflare R2 for payload storage. In local dev, the Docker stack uses MinIO as a stand-in.

How long is my data kept?

It depends on your plan:

Plan	Event history
Free	3 days
Builder	30 days
Studio	90 days

After the history window, event records and bodies are pruned. Aliases and their URLs are kept indefinitely until you delete them.

Pricing and limits

Can I use FixedHook for free?

Yes. The free plan includes 1 alias, 10,000 events per month, and 3 days of history. There is no time limit on the free plan; you can stay on it forever.

What counts as an "event"?

An event is one webhook delivery attempt. A successful request counts as one event. A failed request also counts as one event. A replay attempt counts as one event. Heartbeats and other system pings do not count.

What happens when I hit the event limit?

The relay keeps accepting and recording events. Your existing tunnels keep forwarding traffic. The only thing that pauses is the ability to initiate new traffic through a tunnel if you have also exceeded your alias limit. We chose this design because losing a webhook because of a quota is much worse than temporarily throttling outbound traffic.

Can I upgrade mid-cycle?

Yes. Upgrades are prorated to the day. Downgrades take effect at the end of the current cycle.

Do you offer a student or non-profit discount?

Not at the moment.

Privacy and security

Can my provider see my real server's IP?

No. Providers only see the FixedHook relay IP. The CLI never exposes your local machine to the public internet. The tunnel is outbound from your machine to the relay, so no inbound ports need to be open.

Can FixedHook see my webhook payloads?

Yes — we store the full request and response bodies so the inspector and replay work. The data is encrypted at rest in object storage. We do not read or process payloads for any purpose other than the inspector, replay, and share features.

Can I delete my data?

Yes. From the dashboard, you can:

Delete a single alias (and all its events) at any time.
Delete your entire account from the danger zone in Settings. This is irreversible after a 7-day grace period.

A share link is scoped to a single event. The recipient sees the event details and can trigger a replay, but cannot navigate to other events or to your account. You can revoke a share link at any time. The access log in the dashboard shows who opened the link and from which IP.

What happens if FixedHook goes down?

If the relay is unreachable, incoming requests to your alias return 502 Bad Gateway from Cloudflare (or whoever fronts the relay). Your providers will see a 5xx and retry according to their own policies. The tunnel will buffer a few requests client-side and try to reconnect automatically. If the relay is down for more than a few minutes, you should temporarily point your providers at a backup URL.

CLI

Where is the CLI key stored?

In your OS keychain: Keychain on macOS, Secret Service on Linux, Credential Manager on Windows. The CLI never writes the key to disk in plaintext.

Yes. Run fixedhook login on each machine. Each machine gets its own key. You can see all active keys in the dashboard under Settings → CLI keys and revoke any of them individually.

Sort of. The alias is owned by one account, but only one tunnel can be online at a time. The second person to start a tunnel takes over from the first. The cleanest way to share is to give each person their own alias (e.g. alice-app, bob-app) and have them register their own provider URLs.

Can the CLI run on a server without a browser?

Yes. Use FIXEDHOOK_API_KEY instead of running fixedhook login. The key is created in the dashboard under Settings → API keys.

Providers

Which providers does FixedHook work with?

Any provider. FixedHook doesn't care about the payload format; it stores the bytes verbatim. Provider detection (the colored badges in the dashboard) is best-effort and based on request headers and path patterns. We currently recognize Stripe, GitHub, Shopify, Clerk, Twilio, Slack, and Svix-based services.

Does FixedHook verify provider signatures?

No. The provider sends a signed request to your alias; the alias forwards it to your code; your code verifies the signature. FixedHook is transport only. We do not see the signing secret and do not perform verification on your behalf.

Production use

Can I use FixedHook for production traffic?

Yes, but with caveats. The current architecture is optimized for development and small-to-medium production traffic. For very high rates, point the alias at a real server (a long-lived process you control) rather than a local tunnel. The alias → server path is the same; the difference is the listener.

What are the rate limits?

Per tunnel: roughly 50 requests per second, 5 MB per request body, a few hundred concurrent in-flight requests. The relay itself handles much higher rates; the bottleneck is the tunnel.

Is there a status page?

Yes, at status.fixedhook.com.

Getting help

Email: support@fixedhook.com
GitHub: github.com/fixedhook/fixedhook/issues
Discord: discord.gg/fixedhook
In-app: Click the help icon in the dashboard to start a conversation.

For urgent production issues, email is the fastest channel. For bug reports and feature requests, GitHub is better — it makes it easier to track and prioritize.

FAQ