Databases · head to head
FaunaDB vs Fig

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
Fig
Developer Tools
IDE-style autocomplete for your existing terminal
- From
- Free
- Free plan
- Yes
The short version
- Fig is free; FaunaDB starts at $25/mo.
- Where Fig falls short: the standalone desktop app is no longer available or supported.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which FaunaDB and Fig actually diverge.
Identical on both: starting price (Free), pricing model (Freemium), free tier (Yes), platforms (Web).
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 Fig
Nothing recorded that FaunaDB does not also cover.
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 Fig
- Extracting historical data from a Fauna dataset that can no longer be reached through the hosted APInot Fig
- Studying a production implementation of deterministic distributed transactions, since the full server source is now readable under Apache 2.0not Fig
- Forking the engine deliberately, where an organisation has JVM and distributed-systems staff and wants a document-relational store it fully controlsnot Fig
Fig
No use cases recorded yet. See the Fig review.
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
Fig
- Shut down on 1 September 2024. Amazon acquired Fig in August 2023 and folded it into Amazon Q Developer, which now carries the terminal autocomplete
- The standalone desktop app is no longer available or supported
- The completion specs remain open source on GitHub, but the product that consumed them is gone
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
Fig
FreeNo published plan breakdown. See the Fig review.
Which should you pick?
Choose FaunaDB if
- You need document-relational model.
- You want to start without paying.
- You also want fql v10.
Questions people ask
- Is FaunaDB or Fig better?
- Neither clearly leads. FaunaDB starts at Free and Fig at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, FaunaDB or Fig?
- FaunaDB starts at Free and Fig at Free.
- Does FaunaDB or Fig run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- 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 Fig is typically brought in for.
- What can FaunaDB do that Fig cannot?
- FaunaDB covers Document-relational model, FQL v10, Distributed ACID transactions, HTTPS access.
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.
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.
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.
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.
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.
Related pages
Other head to heads
- FaunaDB vs PostgreSQL
- FaunaDB vs Cockroach Labs
- FaunaDB vs BigQuery
- FaunaDB vs DynamoDB
- FaunaDB vs CouchDB
- FaunaDB vs CosmosDB
- FaunaDB vs ArangoDB
- FaunaDB vs Dgraph
- FaunaDB vs MongoDB
- FaunaDB vs ClickHouse
- FaunaDB vs Elasticsearch
- FaunaDB vs PlanetScale
- FaunaDB vs Redis
- FaunaDB vs Supabase
- FaunaDB vs Google Cloud SQL
- FaunaDB vs Amazon RDS
- FaunaDB vs Apache Airflow
- FaunaDB vs Amazon Aurora
- FaunaDB vs Sweep
- FaunaDB vs Cody
- FaunaDB vs Warp
- FaunaDB vs Visual Studio Code
- FaunaDB vs CodeSandbox
- FaunaDB vs GitLab
- FaunaDB vs Keycloak
- FaunaDB vs Vite
- FaunaDB vs Daytona
- FaunaDB vs Depot
- FaunaDB vs ESLint
- FaunaDB vs Helix
- FaunaDB vs Refact
- FaunaDB vs Restate
- FaunaDB vs RubyMine
- FaunaDB vs Soketi
- FaunaDB vs SonarQube
- FaunaDB vs Sourcegraph
- Fig vs PostgreSQL
- Fig vs Cockroach Labs
- Fig vs BigQuery
- Fig vs DynamoDB
- Fig vs CouchDB
- Fig vs CosmosDB
- Fig vs ArangoDB
- Fig vs Dgraph
- Fig vs MongoDB
- Fig vs ClickHouse
- Fig vs Elasticsearch
- Fig vs PlanetScale
- Fig vs Redis
- Fig vs Supabase
- Fig vs Google Cloud SQL
- Fig vs Amazon RDS
- Fig vs Apache Airflow
- Fig vs Amazon Aurora
- Fig vs Sweep
- Fig vs Cody
- Fig vs Warp
- Fig vs Visual Studio Code
- Fig vs CodeSandbox
- Fig vs GitLab
- Fig vs Keycloak
- Fig vs Vite
- Fig vs Daytona
- Fig vs Depot
- Fig vs ESLint
- Fig vs Helix
- Fig vs Refact
- Fig vs Restate
- Fig vs RubyMine
- Fig vs Soketi
- Fig vs SonarQube
- Fig vs Sourcegraph
