Softwr

Developer Tools · head to head

Hookdeck vs Teleport

Hookdeck logo

Hookdeck

Developer Tools

Event gateway that receives, queues, retries and replays inbound webhooks

From
Free
Free plan
Yes
Full reviewWebsite
Teleport logo

Teleport

Cybersecurity

Certificate-based access to servers, Kubernetes, databases and apps, replacing shared credentials and VPNs

From
On request
Free plan
No
Full reviewWebsite

The short version

  • Only Hookdeck has a free tier, so it costs nothing to try first.
  • Each has a real cost: Hookdeck pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.; Teleport pricing is not published and is described as active users plus protected resources, so an autoscaling estate cannot forecast the bill and finance teams discover the true cost only after the first true-up.
  • They diverge on capability: Hookdeck covers Ingest and persist, Teleport covers Short-lived certificates.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Hookdeck and Teleport actually diverge.

Attributes where Hookdeck and Teleport differ
AttributeHookdeckTeleport
Starting priceFreeOn request
Pricing modelPer month by delivered event countquote
Free tierYesNo
PlatformsWeb, Linux, macOS, WindowsLinux, macOS, Windows, Kubernetes, Cloud
CategoryDeveloper ToolsCybersecurity

Identical on both: user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Hookdeck

  • Ingest and persist
  • Automatic retries
  • Filters and fan-out
  • Transformations
  • Local development CLI
  • Rate limiting

Only in Teleport

  • Short-lived certificates
  • Protocol coverage
  • Session recording and replay
  • Access Requests
  • Device Trust
  • Identity provider integration
  • Machine identity
  • FIPS and FedRAMP builds

What people use each for

The jobs each tool is most often brought in to do.

Hookdeck

  • A payments integration where losing a Stripe event during a deploy causes an order to go unfulfillednot Teleport
  • Fanning one provider webhook out to several internal services without each subscribing separatelynot Teleport
  • Debugging a partner integration by replaying the exact failing payload after shipping a fixnot Teleport
  • Receiving production-shaped webhooks on a developer laptop without running a public tunnelnot Teleport

Teleport

  • Removing long-lived SSH keys and shared database passwords so that offboarding an engineer takes one action in the identity providernot Hookdeck
  • Producing session recordings and per-user database audit trails as direct evidence for SOC 2 or FedRAMPnot Hookdeck
  • Giving contractors or on-call engineers time-boxed, approved access to production instead of standing admin rightsnot Hookdeck
  • Replacing a flat VPN with per-resource authorisation across servers, Kubernetes and internal web appsnot Hookdeck

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Hookdeck

  • Pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • Free-tier retention is three days, which is shorter than the time it typically takes to notice a failing integration, so the payloads needed for a replay are often already gone.
  • It becomes a single point of failure in front of every third-party integration, and an outage there means every provider webhook queues or fails at once.
  • The transformation layer runs JavaScript in a constrained environment, so anything that needs a database lookup or an external call has to happen downstream instead.
  • For a team already running Kafka or SQS the value is mostly the console and the replay UI, which is a hard cost to justify against infrastructure they already operate.

Teleport

  • Pricing is not published and is described as active users plus protected resources, so an autoscaling estate cannot forecast the bill and finance teams discover the true cost only after the first true-up.
  • The proxy is a hard dependency on reaching production, so it needs its own high availability deployment and a tested break-glass path or an outage in Teleport becomes an outage in your ability to respond to outages.
  • The open source Community Edition omits Access Requests, Device Trust and the FIPS builds, which are exactly the controls an auditor asks about, so the free tier rarely survives a compliance review.
  • Self-hosting means running and upgrading a certificate authority and its backing store, and Teleport releases frequently enough that upgrade work becomes a standing operational commitment.
  • Coverage across protocols is uneven in depth, so teams with legacy systems, unusual databases or bespoke network appliances find gaps that still require the old VPN to remain in place alongside it.

Pricing, plan by plan

Hookdeck

Free
  • DeveloperFree
    • Up to ten thousand events per month
    • Three-day retention
    • One user
  • Team$39/month
    • Ten thousand events included
    • Unlimited users
    • Pay as you go metering above the included events
  • Growth$499/month
    • Ten thousand events included plus metered usage
    • Thirty-day retention
    • Uptime and latency SLAs
  • Enterprise$undefined/year
    • Negotiated event volume
    • Custom retention
    • Dedicated support

Teleport

On request
  • Teleport Community Edition$undefined/year
    • Open source, self-hosted
    • SSH, Kubernetes, database and app access
    • Session recording
  • Teleport Enterprise$undefined/year
    • Cloud-hosted or self-hosted
    • Access Requests and approval workflow
    • Device Trust and hardware key enforcement

Which should you pick?

Choose Hookdeck if

  • You need ingest and persist.
  • You want to start without paying.
  • You work on Web, Linux, macOS, Windows.
  • You also want automatic retries.
Hookdeck review

Choose Teleport if

  • You need short-lived certificates.
  • You work on Linux, macOS, Windows, Kubernetes, Cloud.
  • You also want protocol coverage.
Teleport review

Questions people ask

Is Hookdeck or Teleport better?
Neither clearly leads. Hookdeck starts at Free and Teleport at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Hookdeck or Teleport?
Hookdeck has a free tier; the other does not. Paid plans start at Free for Hookdeck and On request for Teleport.
Does Hookdeck or Teleport run on more platforms?
Hookdeck runs on Web, Linux, macOS, Windows. Teleport runs on Linux, macOS, Windows, Kubernetes, Cloud.
Can I use Hookdeck for free?
Yes. Hookdeck has a free tier, so you can try it without paying. Teleport starts at On request.
What is Hookdeck best used for?
Hookdeck is most often used for a payments integration where losing a stripe event during a deploy causes an order to go unfulfilled, fanning one provider webhook out to several internal services without each subscribing separately, debugging a partner integration by replaying the exact failing payload after shipping a fix, receiving production-shaped webhooks on a developer laptop without running a public tunnel. Of those, a payments integration where losing a stripe event during a deploy causes an order to go unfulfilled and fanning one provider webhook out to several internal services without each subscribing separately are not what Teleport is typically brought in for.
What can Hookdeck do that Teleport cannot?
Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations. Teleport covers Short-lived certificates, Protocol coverage, Session recording and replay, Access Requests.

Answered from the vendors’ own pages

Hookdeck: Is there a free plan?

Yes, ten thousand events a month with three-day retention and one user.

Teleport: Is the open source edition usable in production?

Yes, but it lacks Access Requests, Device Trust and FIPS builds, which most compliance programmes end up requiring.

Hookdeck: How is usage counted?

By delivered events, so a single inbound webhook fanned out to three destinations counts as three.

Teleport: How is it priced?

Not publicly. The vendor prices on active users and protected resources and provides a quote after a sales conversation.

Hookdeck: Can I replay a failed webhook?

Yes, individually or in bulk from the console, with the original payload.

Teleport: What happens if Teleport goes down?

Nobody reaches the resources behind it, so you need a highly available deployment and a documented break-glass procedure.

Hookdeck: Does it work for outbound webhooks too?

Yes, the same queueing, retry and observability applies to webhooks you send.

Teleport: Does it replace our VPN?

For anything you put behind it, yes. Legacy systems and appliances it does not support will keep the VPN alive.

Share

Related pages

More on Hookdeck

More on Teleport

Keep looking

Other head to heads