Fauna Problems & Issues
SaasThe Distributed Serverless Database (DISCONTINUED)
FAUNA SHUT DOWN MAY 30, 2025. Service no longer available. All scores set to 0 as product cannot be used. The technology was innovative but the business could not sustain capital requirements. This serves as a cautionary tale about vendor risk with cloud-only, VC-funded database services.
Should you use Fauna?
ByeFauna disappoints many users (score 0/100). Most reported issues: SERVICE SHUT DOWN - May 30, 2025; Costs did not scale to $0 like truly serverless; FQL query language had steep learning curve. Not a good fit for: Anyone considering Fauna in 2026; Former Fauna users needing migration; Document database seekers. Users most often switch to Amazon DynamoDB, FerretDB, MongoDB Atlas.
Top problems
- SERVICE SHUT DOWN - May 30, 2025
- Costs did not scale to $0 like truly serverless
- FQL query language had steep learning curve
Avoid if you are
- Anyone considering Fauna in 2026
- Former Fauna users needing migration
- Document database seekers
Common alternatives: Amazon DynamoDB, FerretDB, MongoDB Atlas
Overview
Fauna was a distributed serverless database offering document storage with relational features, ACID transactions, and global distribution. Founded by ex-Twitter engineers. SERVICE SHUT DOWN MAY 30, 2025. Company promised open-source release of core technology but no timeline provided.
Signals & Issues
Patterns extracted from real user feedback — not raw reviews.
Fauna announced shutdown in March 2025 and terminated all services on May 30, 2025. All accounts were deleted. The company stated 'driving broad adoption of a new operational database globally is very capital intensive' and could not raise needed capital.
Company committed to 'releasing open-source version of core database technology' but provided no timeline. As of March 2026, status of open-source release remains unclear. Users waiting for self-hosted option have no certainty.
Despite being 'serverless,' costs did not 'scale to $0' like other serverless offerings. Once exceeding free tier, users faced flat monthly rate + overage model - paying every month regardless of usage. Users complained about being 'forced to jump to higher tier' for features.
Using Fauna Dashboard to navigate databases and run FQL queries 'consumes read, write, and compute operations.' Every navigation or browser refresh executed queries against quotas, adding unexpected costs.
Fauna's FQL (Fauna Query Language) required learning a new paradigm. 'All compute operations that might happen between different SQL calls must be translated into FQL expressions.' Porting existing SQL apps took significant effort.
Users reported the 'type system can be difficult to debug.' Error messages weren't always clear, making troubleshooting time-consuming. Developer experience had friction points.
As a newer product, 'it was hard to find well-documented patterns.' Reaching out to Fauna team was often the best way to resolve edge cases. Community resources were limited compared to established databases.
Unlike traditional SQL RDBMS, users 'cannot span a single transaction over multiple requests.' All operations had to run inside the database via FQL expressions. This architectural limitation complicated certain application patterns.
Users noted that after accepting VC money and new CEO, 'things started to go downhill' as company 'started focusing on selling to corporations instead of developers.' Developer experience suffered.
Fauna lacked native full-text search capabilities. Users needing search functionality had to integrate external services. This gap limited use cases and added complexity.
What Users Love
Document model with relational capabilities (Historical)
Fauna combined flexibility of document databases with relational power - joins, foreign keys, and full schema enforcement. Solved 'many problems with flexibility of document-based databases combined with relational power.'
Global distribution with strong consistency (Historical)
Built by ex-Twitter engineers, Fauna offered global distribution with ACID transactions. Data replicated globally with strong consistency guarantees. Genuinely serverless operation.
Removed operational database burden (Historical)
Fauna 'removed the painful part of relational databases - the operations.' Developers could 'build data stores without worrying as much about operating, patching, and scaling the database.'
Generous free tier (Historical)
Offered generous free tier for development and small projects. Entry point was accessible for experimentation and prototyping before service shutdown.
GraphQL and REST API support (Historical)
Provided GraphQL integration and REST-like APIs alongside native FQL. Multiple access patterns supported different application architectures.
Row-level security built-in (Historical)
Security model allowed fine-grained access control at the document level. Simplified authorization logic in applications.
Pricing Plans
Users: N/A
Storage: N/A
Limitations: Cannot sign up or use - service terminated
Users: N/A
Storage: 5GB (was)
Limitations: Historical reference only - service shut down
Users: N/A
Storage: Pay per GB
Limitations: Historical reference only - service shut down
Features
Database
- Document + Relational
Was unique
- ACID Transactions
Historical
- SQL Queries
FQL only
Infrastructure
- Global Distribution
Historical
- Serverless
Historical
API
- GraphQL Support
Historical
Status
- Active Service
SHUT DOWN
Licensing
- Open Source
Promised, no timeline
Search
- Full-Text Search
Never had
Deployment
- Self-Hosted Option
Was cloud-only
Who Should Use This?
Neutral
Developers waiting for open source release
Fauna promised to open-source the core technology but provided no timeline. As of March 2026, status is unclear. Don't count on this for production planning.
Those researching database history
Fauna's shutdown is a cautionary tale about vendor risk with cloud-only databases. The technology was innovative but the business couldn't sustain the capital requirements for global adoption.
Avoid
Anyone considering Fauna in 2026
FAUNA SERVICE IS SHUT DOWN. The service terminated on May 30, 2025 and all accounts were deleted. You cannot sign up or use Fauna. See alternatives below for migration options.
Former Fauna users needing migration
If you haven't migrated yet, do so immediately. Consider MongoDB Atlas, Supabase, PlanetScale, or DynamoDB depending on your data model. FerretDB offers MongoDB-compatible open-source option.
Document database seekers
For document database needs, use MongoDB Atlas (established), Supabase (PostgreSQL with JSON), or DynamoDB (AWS). Fauna is no longer an option.
Globally distributed database seekers
For global distribution needs, consider CockroachDB, Google Cloud Spanner, or DynamoDB Global Tables. These are actively maintained services unlike Fauna.
Regret Patterns
Common buyer's remorse scenarios reported by users.
Teams chose Fauna for innovation, building applications deeply integrated with FQL and Fauna features. When shutdown announced in March 2025, faced urgent migration with 2-month deadline. Vendor risk materialized painfully.
Evaluation focused on technology, not business sustainability. Didn't assess funding runway, market adoption, or competitive position. A more established database would have avoided forced migration.
Significant time invested learning FQL, a proprietary language. Skills not transferable to other databases. Code required complete rewrite for any alternative. Should have used standard SQL/document APIs.
Unlike open-source databases, couldn't self-host when vendor failed. Completely dependent on Fauna's continued operation. Self-hostable alternatives would have provided continuity option.
Some teams delayed migration hoping for promised open-source release. No timeline provided, status unclear months later. Should have migrated immediately rather than waiting on uncertain promises.
When It Breaks Down
Scenarios where this product tends to fail users.
Fauna announced shutdown in March 2025, terminated May 30, 2025. Teams had approximately 2 months to export data and migrate applications to alternatives. Urgent, unplanned migration consumed significant resources.
FQL skills and code non-transferable to any other database. Entire data access layer required rewriting. Investment in learning Fauna-specific patterns yielded no portable knowledge.
Cloud-only service meant complete dependency on vendor. When vendor failed, no option to run infrastructure independently. Open-source databases would have allowed self-hosting continuity.
Teams that didn't migrate before May 30, 2025 deadline lost access to their data. All accounts deleted as part of shutdown. No recovery option for missed migration window.
Company promised open-source release but provided no timeline. Months after shutdown, status remains unclear. Teams counting on self-hosting open-source version left waiting indefinitely.
Alternatives Users Switch To
MongoDB Atlas
9x mentionedBest overall Fauna alternative per G2. Gain: established market leader, document model, flexible schemas, multi-cloud. Trade-off: different query language, no native relational features like Fauna had.
Supabase
8x mentionedGood for teams wanting PostgreSQL with JSON support. Gain: SQL + document flexibility, auth/storage included, active development. Trade-off: relational-first vs Fauna's document-first approach.
Amazon DynamoDB
7x mentionedServerless document database from AWS. Gain: truly serverless scaling, global tables, AWS integration. Trade-off: AWS lock-in, different data model, no relational features.
PlanetScale
6x mentionedFor teams wanting serverless relational. Gain: MySQL/PostgreSQL support, branching workflows. Trade-off: no free tier since 2024, relational model vs document.
FerretDB
5x mentionedOpen-source MongoDB-compatible database. Gain: no vendor lock-in, MongoDB wire protocol, self-hostable. Trade-off: newer project, less mature ecosystem.
Frequently Asked Questions
See how Fauna compares in our Best Database Software rankings, or calculate costs with our Budget Calculator.
Work at Fauna or spotted something outdated? Suggest a correction — we verify every change against public sources. See our methodology.