Softwr

Developer Tools · head to head

Hookdeck vs Rollup

Hookdeck logo

Hookdeck

Developer Tools

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

From
Free
Free plan
Yes
Rollup logo

Rollup

Web Development

JavaScript module bundler built for libraries

From
Free
Free plan
Yes

The short version

  • 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.; Rollup slower than the Go and Rust bundlers that followed it, since it is written in JavaScript
  • They diverge on capability: Hookdeck covers Ingest and persist, Rollup covers Tree shaking.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Hookdeck and Rollup actually diverge.

Attributes where Hookdeck and Rollup differ
AttributeHookdeckRollup
Pricing modelPer month by delivered event countOpen source, no licence fee
PlatformsWeb, Linux, macOS, WindowsLinux, macOS, Windows
CategoryDeveloper ToolsWeb Development

Identical on both: starting price (Free), free tier (Yes), 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 Rollup

  • Tree shaking
  • Clean output
  • Multiple output formats
  • Plugin API

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 Rollup
  • Fanning one provider webhook out to several internal services without each subscribing separatelynot Rollup
  • Debugging a partner integration by replaying the exact failing payload after shipping a fixnot Rollup
  • Receiving production-shaped webhooks on a developer laptop without running a public tunnelnot Rollup

Rollup

  • Publishing a JavaScript library in several module formatsnot Hookdeck
  • Builds where output size and cleanliness matter more than build speednot Hookdeck
  • Producing ES module output for consumers who will bundle it themselvesnot 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.

Rollup

  • Slower than the Go and Rust bundlers that followed it, since it is written in JavaScript
  • Application concerns like dev servers and hot reloading are not its job, so app builds need Vite on top
  • Configuration for non-trivial applications gets verbose compared with tools that assume more

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

Rollup

Free
  • RollupFree
    • Full functionality
    • Commercial use permitted
    • Community support

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.

Choose Rollup if

  • You need tree shaking.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want clean output.

Questions people ask

Is Hookdeck or Rollup better?
Neither clearly leads. Hookdeck starts at Free and Rollup at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Hookdeck or Rollup?
Hookdeck starts at Free and Rollup at Free.
Does Hookdeck or Rollup run on more platforms?
Hookdeck runs on Web, Linux, macOS, Windows. Rollup runs on Linux, macOS, Windows.
Can I use Hookdeck for free?
Both have a free tier, so you can try either at no cost before committing.
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 Rollup is typically brought in for.
What can Hookdeck do that Rollup cannot?
Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations. Rollup covers Tree shaking, Clean output, Multiple output formats, Plugin API.

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.

Rollup: Is Rollup free?

Yes, open source under the MIT licence.

Hookdeck: How is usage counted?

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

Rollup: Rollup or webpack?

Rollup is the usual choice for libraries thanks to cleaner output and better tree shaking. webpack remains stronger for complex applications with heavy asset handling.

Hookdeck: Can I replay a failed webhook?

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

Rollup: Do I need Rollup if I use Vite?

Not directly. Vite uses Rollup for production builds, so you already benefit from it.

Hookdeck: Does it work for outbound webhooks too?

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

Share

Related pages

Other head to heads