Softwr

APIs · head to head

Episode Six vs Hookdeck

Episode Six logo

Episode Six

APIs

Payment processing and ledger platform deployable on premise or in your own cloud

From
On request
Free plan
No
Hookdeck logo

Hookdeck

Developer Tools

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

From
Free
Free plan
Yes

The short version

  • Hookdeck starts at $39/mo; Episode Six prices on request.
  • Only Episode Six lists tritium API platform; only Hookdeck lists ingest and persist.
  • Where Hookdeck falls short: pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • Prices and features on this page were last checked on 20 November 2026.

How do Episode Six and Hookdeck differ?

Episode Six and Hookdeck differ on starting price (On request against Free), pricing model and free tier (No against Yes). Only the attributes on which Episode Six and Hookdeck actually diverge.

Attributes where Episode Six and Hookdeck differ
AttributeEpisode SixHookdeck
Starting priceOn requestFree
Pricing modelQuotePer month by delivered event count
Free tierNoYes
PlatformsWeb, API, Self-hostedWeb, Linux, macOS, Windows
CategoryAPIsDeveloper Tools

Which features does each one have?

They share no listed features; 8 appear only for Episode Six and 6 only for Hookdeck. 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 Episode Six

  • Tritium API platform
  • Flexible deployment
  • Multi product issuing
  • Digital wallets
  • Multi currency ledger
  • Network connectivity
  • Configurable product engine
  • Institutional controls

Only in Hookdeck

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

What is each one used for?

Episode Six is most often brought in for A telco or airline launching a branded wallet and card product at national scale. The jobs each tool is most often brought in to do.

Episode Six

  • A bank in a jurisdiction with data residency rules that forbid processing customer data in a shared multi tenant cloudnot Hookdeck
  • A large institution replacing a legacy card processor without moving off its own infrastructurenot Hookdeck
  • A telco or airline launching a branded wallet and card product at national scalenot Hookdeck
  • A bank running prepaid, debit and credit products that wants them on one ledger rather than three processorsnot Hookdeck

Hookdeck

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

Where do Episode Six and Hookdeck fall short?

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

Episode Six

  • Deployment on premise or in a private tenancy means the institution carries infrastructure, upgrade and PCI scope work that a hosted processor would absorb
  • Implementation runs to quarters and involves core banking, network certification and fraud system integration, so time to first card is far longer than with a self serve issuer processor
  • Pricing is entirely bespoke and weighted to large programmes, which prices out fintechs and small issuers who would be better served by a hosted platform
  • Being smaller than the incumbent processors, its network certifications and operational presence vary by region, so a global rollout can find gaps in specific markets
  • The flexibility of six hundred APIs and a configurable product engine shifts design responsibility onto the buyer, and institutions without strong internal payments architects end up dependent on professional services

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

How much do Episode Six and Hookdeck cost?

Episode Six is priced on request; Hookdeck has a free plan, with paid plans from $39/mo. Plan by plan below, from each vendor's own pricing page.

Episode Six

On request
  • Tritium platformOn request
    • Licence and implementation quoted per institution
    • Deployment model affects cost materially: on premise, private cloud or hosted
    • Processing fees typically per transaction or per active card

Hookdeck

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

Which should you pick?

Choose Episode Six if

  • You need tritium api platform.
  • You work on Web, API, Self-hosted.
  • You also want flexible deployment.

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.

Questions people ask

Is Episode Six or Hookdeck better?
Neither clearly leads. Episode Six starts at On request and Hookdeck at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Episode Six or Hookdeck?
Hookdeck has a free tier; the other does not. Paid plans start at On request for Episode Six and Free for Hookdeck.
Does Episode Six or Hookdeck run on more platforms?
Episode Six runs on Web, API, Self-hosted. Hookdeck runs on Web, Linux, macOS, Windows.
Can I use Hookdeck for free?
Yes. Hookdeck has a free tier, so you can try it without paying. Episode Six starts at On request.
What is Episode Six best used for?
Episode Six is most often used for a bank in a jurisdiction with data residency rules that forbid processing customer data in a shared multi tenant cloud, a large institution replacing a legacy card processor without moving off its own infrastructure, a telco or airline launching a branded wallet and card product at national scale, a bank running prepaid, debit and credit products that wants them on one ledger rather than three processors. Of those, a bank in a jurisdiction with data residency rules that forbid processing customer data in a shared multi tenant cloud and a large institution replacing a legacy card processor without moving off its own infrastructure are not what Hookdeck is typically brought in for.
What can Episode Six do that Hookdeck cannot?
Episode Six covers Tritium API platform, Flexible deployment, Multi product issuing, Digital wallets. Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations.

Answered from the vendors’ own pages

Episode Six: Can Episode Six run inside our own data centre?

Yes. On premise and private cloud deployment is the main reason banks choose it over hosted only processors.

Hookdeck: Is there a free plan?

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

Episode Six: Is it suitable for a startup issuing its first cards?

Not really. The licence, implementation timeline and cost are aimed at banks and large institutions.

Hookdeck: How is usage counted?

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

Episode Six: Do we still need a card licence or sponsor?

Yes. Episode Six is a processor. Network membership, licensing or a sponsor arrangement remains your responsibility.

Hookdeck: Can I replay a failed webhook?

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

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