Compare

Hookdeck vs Ujex Ingress for AI Agents

Akshay Sarode
Verdict

Hookdeck is the right pick if webhook development is the entire problem (event inspection, replay, filtering matter most). Ujex Ingress is the right pick when you also need agent-aware auth, audit, budgets, and integration with the rest of an agent stack — same Firebase project as your memory and email.

What each one is

Hookdeck: an Event Gateway for webhooks. Sources, connections, destinations, events. Inspection, replay, filtering, retries. CLI for local development; managed cloud for production. Open-source CLI.

Ujex Ingress: the ingress subsystem of Ujex. Three-tier tunnels — Quick (no signup, ephemeral via bore), Standard (cloudflared, persistent), Stable (user-owned Cloudflare Tunnel, custom domain). Auth via Ujex agent identity; events tagged in audit log.

Capability matrix

HookdeckUjex Ingress
Local-dev tunnel✓ (CLI)✓ (Quick tier)
Stable URL on custom domain✓ (paid)✓ (Stable tier)
Event inspection / replay✓ ExcellentBasic (audit log)
Event filtering / transformationLimited
MCP server for AI agents
Auth via agent identityAPI keysUjex device keys + scopes
Spend cap integration✓ (Governor)
Audit trail (hash-chained)Standard logs✓ Hash-chained
Self-hostableCloud-managed✓ (Apache-2.0)
Free tier10k events/mo1k events/mo · stable tier limited

Pick Hookdeck if

Pick Ujex Ingress if

Use both

Yes, you can. Hookdeck for the developer-flow webhooks (Stripe → my agent for payment events). Ujex Ingress for the agent-internal webhooks (one agent calls another's URL, both authenticated as Ujex agents).

FAQ

Does Hookdeck have an MCP server?

Yes — Hookdeck CLI ships with MCP server capabilities for AI agents.

Can Ujex Ingress run my own Cloudflare Tunnel?

Yes — the Stable tier uses your Cloudflare account and custom domain. The Quick tier uses bore against our relay.