Developer Tools · head to head
Hookdeck vs Marqeta

Hookdeck
Developer Tools
Event gateway that receives, queues, retries and replays inbound webhooks
- From
- Free
- Free plan
- Yes

Marqeta
APIs
Card issuing and transaction processing APIs with just-in-time funding
- From
- On request
- Free plan
- No
The short version
- Hookdeck starts at $39/mo; Marqeta prices on request.
- Only Hookdeck lists ingest and persist; only Marqeta lists just-in-time funding.
- 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.
- Where Marqeta falls short: pricing carries minimum monthly platform commitments, so a programme with modest card volume pays for capacity it never uses.
- Prices and features on this page were last checked on 20 November 2026.
How do Hookdeck and Marqeta differ?
Hookdeck and Marqeta differ on starting price (Free against On request), pricing model and free tier (Yes against No). Only the attributes on which Hookdeck and Marqeta actually diverge.
Which features does each one have?
They share no listed features; 6 appear only for Hookdeck and 6 only for Marqeta. 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 Marqeta
- Just-in-time funding
- Virtual and physical issuing
- Spend controls
- Programme management tools
- Multi-region issuing
- Webhooks and ledger data
What is each one used for?
Marqeta is most often brought in for an expense platform issuing a virtual card per subscription with merchant locks. 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 Marqeta
- Fanning one provider webhook out to several internal services without each subscribing separatelynot Marqeta
- Debugging a partner integration by replaying the exact failing payload after shipping a fixnot Marqeta
- Receiving production-shaped webhooks on a developer laptop without running a public tunnelnot Marqeta
Marqeta
- A delivery marketplace funding courier cards only at the moment a courier pays for the ordernot Hookdeck
- An expense platform issuing a virtual card per subscription with merchant locksnot Hookdeck
- A lender issuing a card that draws on an approved credit line rather than a stored balancenot Hookdeck
- A fintech wanting the same issuing stack across US and European programmesnot Hookdeck
Where do Hookdeck and Marqeta fall 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
Marqeta
- You still need a sponsor bank and a BIN, so the timeline and compliance burden of launching are set by a bank you must separately court and satisfy
- Pricing carries minimum monthly platform commitments, so a programme with modest card volume pays for capacity it never uses
- Programme revenue depends heavily on interchange, which means regulated debit interchange caps and European interchange caps materially change the business case by market
- Disputes, chargebacks and fraud losses sit with the programme, and teams that assumed the processor absorbed them discover a real operations headcount requirement
- Just-in-time funding makes your own authorisation endpoint a hard availability dependency; if it is slow or down, cards decline at the point of sale
How much do Hookdeck and Marqeta cost?
Hookdeck has a free plan, with paid plans from $39/mo; Marqeta is priced on request. Plan by plan below, from each vendor's own pricing page.
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
Marqeta
On request- Marqeta card issuingOn request
- Minimum monthly platform fee plus per-transaction and per-active-card charges
- Interchange share negotiated between programme, processor and sponsor bank
- Sponsor bank required, with its own fees and approval process
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 Marqeta if
- You need just-in-time funding.
- You work on Web, API.
- You also want virtual and physical issuing.
Questions people ask
- Is Hookdeck or Marqeta better?
- Neither clearly leads. Hookdeck starts at Free and Marqeta at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Hookdeck or Marqeta?
- Hookdeck has a free tier; the other does not. Paid plans start at Free for Hookdeck and On request for Marqeta.
- Does Hookdeck or Marqeta run on more platforms?
- Hookdeck runs on Web, Linux, macOS, Windows. Marqeta runs on Web, API.
- Can I use Hookdeck for free?
- Yes. Hookdeck has a free tier, so you can try it without paying. Marqeta 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 Marqeta is typically brought in for.
- What can Hookdeck do that Marqeta cannot?
- Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations. Marqeta covers Just-in-time funding, Virtual and physical issuing, Spend controls, Programme management tools.
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.
Marqeta: Do I need a sponsor bank?
Yes. Marqeta is an issuer processor, not a bank. Card programmes run on a sponsor bank BIN, and that bank approves and supervises your programme.
Hookdeck: How is usage counted?
By delivered events, so a single inbound webhook fanned out to three destinations counts as three.
Marqeta: How does the pricing really work?
A minimum monthly platform fee plus per-transaction and per-active-card charges, offset by a negotiated share of interchange. The interchange split is the substance of the deal.
Hookdeck: Can I replay a failed webhook?
Yes, individually or in bulk from the console, with the original payload.
Marqeta: What is just-in-time funding?
Marqeta calls your endpoint at authorisation so you decide and fund each transaction, rather than pre-loading balances onto cards.
Hookdeck: Does it work for outbound webhooks too?
Yes, the same queueing, retry and observability applies to webhooks you send.
Related pages
Other head to heads
- Hookdeck vs Envoy
- Hookdeck vs Istio
- Hookdeck vs Jitsu
- Hookdeck vs GitLab
- Hookdeck vs Spacelift
- Hookdeck vs Okteto
- Hookdeck vs Webpack
- Hookdeck vs Garden
- Hookdeck vs Backstage
- Hookdeck vs Cloud Native Buildpacks
- Hookdeck vs AWS Serverless Application Model (AWS SAM)
- Hookdeck vs Dagger
- Hookdeck vs GNAT Pro
- Hookdeck vs HCP Terraform
- Hookdeck vs JetBrains Rider
- Hookdeck vs Moonrepo
- Hookdeck vs PartyKit
- Hookdeck vs PyCharm
- Hookdeck vs Paymentology
- Hookdeck vs Highnote
- Hookdeck vs i2c
- Hookdeck vs Enfuce
- Hookdeck vs Tribe Payments
- Hookdeck vs Lithic
- Hookdeck vs Thredd
- Hookdeck vs Episode Six
- Hookdeck vs Weavr
- Hookdeck vs Unit
- Hookdeck vs Yapily
- Hookdeck vs Synctera
- Hookdeck vs Volt
- Hookdeck vs Zimpler
- Hookdeck vs 3scale
- Hookdeck vs Basis Theory
- Hookdeck vs curl
- Hookdeck vs Flybits
- Marqeta vs Envoy
- Marqeta vs Istio
- Marqeta vs Jitsu
- Marqeta vs GitLab
- Marqeta vs Spacelift
- Marqeta vs Okteto
- Marqeta vs Webpack
- Marqeta vs Garden
- Marqeta vs Backstage
- Marqeta vs Cloud Native Buildpacks
- Marqeta vs AWS Serverless Application Model (AWS SAM)
- Marqeta vs Dagger
- Marqeta vs GNAT Pro
- Marqeta vs HCP Terraform
- Marqeta vs JetBrains Rider
- Marqeta vs Moonrepo
- Marqeta vs PartyKit
- Marqeta vs PyCharm
- Marqeta vs Paymentology
- Marqeta vs Highnote
- Marqeta vs i2c
- Marqeta vs Enfuce
- Marqeta vs Tribe Payments
- Marqeta vs Lithic
- Marqeta vs Thredd
- Marqeta vs Episode Six
- Marqeta vs Weavr
- Marqeta vs Unit
- Marqeta vs Yapily
- Marqeta vs Synctera
- Marqeta vs Volt
- Marqeta vs Zimpler
- Marqeta vs 3scale
- Marqeta vs Basis Theory
- Marqeta vs curl
- Marqeta vs Flybits
