Softwr

Developer Tools · head to head

Hookdeck vs TiDB

Hookdeck logo

Hookdeck

Developer Tools

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

From
Free
Free plan
Yes
Visit HookdeckFull review
TiDB logo

TiDB

Databases

Apache 2.0 distributed SQL database with MySQL wire compatibility and a separate columnar replica for analytical queries.

From
Free
Free plan
Yes
Visit TiDBFull review

The short version

  • Free plans on both; paid from $39/mo and $250/mo.
  • Only Hookdeck lists ingest and persist; only TiDB lists MySQL wire compatibility.
  • 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 31 August 2026.

Where they differ

Only the attributes on which Hookdeck and TiDB actually diverge.

Attributes where Hookdeck and TiDB differ
AttributeHookdeckTiDB
Pricing modelPer month by delivered event countFreemium
PlatformsWeb, Linux, macOS, WindowsWeb, AWS, Azure, Self-managed
CategoryDeveloper ToolsDatabases

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: founded for Hookdeck.

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 TiDB

  • MySQL wire compatibility
  • Horizontal write scaling
  • Distributed ACID transactions
  • TiFlash columnar replica
  • Automatic rebalancing
  • Raft replication
  • Apache 2.0 licence
  • Online schema change

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

TiDB

  • A MySQL workload that has hit the write ceiling of a single primary and would otherwise need an application-level sharding layernot Hookdeck
  • Reporting that must run against current transactional data, where the columnar replica removes the delay and the cost of an ETL pipelinenot Hookdeck
  • Multi-region deployments needing a single logical database with automatic failover rather than manual primary promotionnot Hookdeck
  • Migrating off a sharded MySQL estate where the sharding logic in the application has become the main source of bugs and operational toilnot 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

TiDB

  • A production cluster needs several placement driver, storage and SQL nodes before it is fault tolerant, so the minimum viable footprint is far larger than a MySQL server and TiDB is never the economical choice for a small database
  • Every transaction takes a timestamp from the placement driver and crosses the network to storage nodes, so simple point queries are slower than on single-node MySQL and latency-sensitive paths need to be measured, not assumed
  • MySQL compatibility is at the wire and dialect level but not complete; stored procedures, triggers and events are not supported, so an application that pushed logic into the database cannot simply be repointed
  • The columnar replica is an extra full copy of the data on its own nodes, so hybrid analytics roughly doubles storage and adds hardware that must be sized and paid for separately
  • Operating it well requires cluster-specific expertise in TiUP or the Kubernetes operator, region hot spots, and rebalancing behaviour, so the licence is free but the running cost includes an engineer who understands distributed storage

Pricing, plan by plan

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

TiDB

Free
  • ServerlessFree
    • 5GB storage
    • 50M request units
    • Free forever tier
  • Dedicated$250/mo
    • Dedicated resources
    • SLA guarantees
    • Enterprise 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.
Hookdeck review

Choose TiDB if

  • You need mysql wire compatibility.
  • You want to start without paying.
  • You work on Web, AWS, Azure, Self-managed.
  • You also want horizontal write scaling.
TiDB review

Questions people ask

Is Hookdeck or TiDB better?
Neither clearly leads. Hookdeck starts at Free and TiDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Hookdeck or TiDB?
Hookdeck starts at Free and TiDB at Free.
Does Hookdeck or TiDB run on more platforms?
Hookdeck runs on Web, Linux, macOS, Windows. TiDB runs on Web, AWS, Azure, Self-managed.
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 TiDB is typically brought in for.
What can Hookdeck do that TiDB cannot?
Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations. TiDB covers MySQL wire compatibility, Horizontal write scaling, Distributed ACID transactions, TiFlash columnar replica.

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.

TiDB: Is TiDB a drop-in replacement for MySQL?

At the protocol and dialect level it is close, and most applications connect unchanged. Stored procedures, triggers and events are not supported, and latency characteristics differ, so it needs testing rather than assumption.

Hookdeck: How is usage counted?

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

TiDB: What licence is it under?

Apache 2.0, for both TiDB and the underlying TiKV storage engine. TiKV is a graduated CNCF project, which is a meaningful governance signal in a market where several competitors moved to source-available licences.

Hookdeck: Can I replay a failed webhook?

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

TiDB: Do I need TiFlash?

Only for analytical queries. It is an optional columnar replica; without it TiDB is a distributed transactional database. With it you get analytics on live data at the cost of an additional full copy.

Hookdeck: Does it work for outbound webhooks too?

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

TiDB: Is the managed cloud the same software?

TiDB Cloud runs the same engine, with the control plane, scaling and operational tooling provided as a service. The entry tier is metered differently from a dedicated cluster, so the cost model rather than the engine is what changes.

TiDB: When is TiDB the wrong choice?

When the database is small enough for one server, when latency on single-row lookups is the primary constraint, or when the application depends on MySQL stored procedures and triggers.

Share

Related pages

More on Hookdeck

More on TiDB

Keep looking

Other head to heads