Softwr

Databases · head to head

FaunaDB vs Hookdeck

FaunaDB logo

FaunaDB

Databases

Document-relational database whose hosted service closed in 2025 and whose core is now unmaintained Apache 2.0 code.

From
Free
Free plan
Yes
Visit FaunaDBFull review
Hookdeck logo

Hookdeck

Developer Tools

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

From
Free
Free plan
Yes
Visit HookdeckFull review

The short version

  • Free plans on both; paid from $25/mo and $39/mo.
  • Only FaunaDB lists document-relational model; 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 13 November 2026.

Where they differ

Only the attributes on which FaunaDB and Hookdeck actually diverge.

Attributes where FaunaDB and Hookdeck differ
AttributeFaunaDBHookdeck
Pricing modelFreemiumPer month by delivered event count
PlatformsWebWeb, Linux, macOS, Windows
CategoryDatabasesDeveloper Tools

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 FaunaDB

  • Document-relational model
  • FQL v10
  • Distributed ACID transactions
  • HTTPS access
  • User-defined functions
  • Attribute-based access control
  • Document history
  • Event streaming

Only in Hookdeck

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

What people use each for

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

FaunaDB

  • Keeping an existing Fauna-backed application alive on self-hosted infrastructure while a migration is planned and fundednot Hookdeck
  • Extracting historical data from a Fauna dataset that can no longer be reached through the hosted APInot Hookdeck
  • Studying a production implementation of deterministic distributed transactions, since the full server source is now readable under Apache 2.0not Hookdeck
  • Forking the engine deliberately, where an organisation has JVM and distributed-systems staff and wants a document-relational store it fully controlsnot Hookdeck

Hookdeck

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

Where each one falls short

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

FaunaDB

  • The hosted service was wound down in 2025, so there is no managed Fauna to buy; every remaining user either operates a JVM cluster themselves or migrates, and both are projects rather than tasks
  • The open-sourced repository has had no substantive activity since May 2025 and the drivers were frozen alongside it, so you inherit responsibility for security patches in a Scala distributed database that almost nobody else is running
  • FQL has no wire or dialect compatibility with anything else, so migrating off is a rewrite of every query, index and access rule in the application rather than a data export
  • No BI tool, ORM or CDC connector speaks FQL, so reporting and analytics always required exporting the data first, and that export tooling is now also unmaintained
  • The community was small before the shutdown and has dispersed since, so operational answers, tuning advice and people who have run a Fauna cluster in anger are all scarce when something breaks

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

Pricing, plan by plan

FaunaDB

Free
  • FreeFree
    • 100K read ops
    • 50K write ops
    • 1GB storage
  • Pro$25/mo
    • Pay per use
    • Priority support
    • Advanced features

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 FaunaDB if

  • You need document-relational model.
  • You want to start without paying.
  • You also want fql v10.
FaunaDB review

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

Questions people ask

Is FaunaDB or Hookdeck better?
Neither clearly leads. FaunaDB starts at Free and Hookdeck at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, FaunaDB or Hookdeck?
FaunaDB starts at Free and Hookdeck at Free.
Does FaunaDB or Hookdeck run on more platforms?
FaunaDB runs on Web. Hookdeck runs on Web, Linux, macOS, Windows.
Can I use FaunaDB for free?
Both have a free tier, so you can try either at no cost before committing.
What is FaunaDB best used for?
FaunaDB is most often used for keeping an existing fauna-backed application alive on self-hosted infrastructure while a migration is planned and funded, extracting historical data from a fauna dataset that can no longer be reached through the hosted api, studying a production implementation of deterministic distributed transactions, since the full server source is now readable under apache 2.0, forking the engine deliberately, where an organisation has jvm and distributed-systems staff and wants a document-relational store it fully controls. Of those, keeping an existing fauna-backed application alive on self-hosted infrastructure while a migration is planned and funded and extracting historical data from a fauna dataset that can no longer be reached through the hosted api are not what Hookdeck is typically brought in for.
What can FaunaDB do that Hookdeck cannot?
FaunaDB covers Document-relational model, FQL v10, Distributed ACID transactions, HTTPS access. Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations.

Answered from the vendors’ own pages

FaunaDB: Can I still sign up for Fauna as a service?

No. Fauna Inc. wound down the hosted service in 2025 and the company website is no longer serving. The only way to run Fauna now is to build and operate the open-sourced server yourself.

Hookdeck: Is there a free plan?

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

FaunaDB: What licence is the open-sourced code under?

Apache 2.0, with the copyright held by a FaunaDB Foundation. That is a permissive OSI licence with no competing-use clause, so you may run it, modify it and even offer it as a service.

Hookdeck: How is usage counted?

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

FaunaDB: Is the open source version the same software that ran the cloud?

It is the core database engine. The control plane, billing, dashboard and multi-tenant operational tooling that made it a service are not part of the release, so you are running the engine, not the product.

Hookdeck: Can I replay a failed webhook?

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

FaunaDB: What should I migrate to?

There is no drop-in target. Teams that valued the document model with relationships usually land on Postgres with JSONB, and teams that valued the serverless HTTP access pattern usually land on DynamoDB or a managed Postgres with an HTTP driver. Either way the query layer is rewritten.

Hookdeck: Does it work for outbound webhooks too?

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

FaunaDB: How hard is it to self-host?

It builds as a fat JAR and runs as a multi-node JVM cluster. There is an OPERATING.md, but no supported packaging, no operator, no upstream releases and no support contract, so budget for a distributed-systems engineer, not a container.

Share

Related pages

More on FaunaDB

More on Hookdeck

Keep looking

Other head to heads