Fauna Problems & Issues
Real user-reported problems, complaints, and limitations for Fauna. Based on analysis of 10 signals.
Overall score: 0/100
Issues by Category
SERVICE SHUT DOWN - May 30, 2025
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.
Open source release promised but no timeline
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.
Costs did not scale to $0 like truly serverless
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.
Dashboard usage consumed operations
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.
FQL query language had steep learning curve
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.
Type system difficult to debug
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.
No transactions spanning multiple requests
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.
Company pivoted focus from developers to enterprise
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.
Documentation gaps for new product
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.
Lacked full-text search capability
Fauna lacked native full-text search capabilities. Users needing search functionality had to integrate external services. This gap limited use cases and added complexity.
Regret Patterns
Common reasons users regret choosing Fauna.
Invested heavily before vendor went out of business
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.
Didn't consider vendor viability
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.
FQL investment became stranded asset
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.
Cloud-only meant no self-hosting escape hatch
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.
Waited for open-source that may never come
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 Fauna Breaks Down
Specific scenarios where Fauna fails or underperforms.
Vendor shuts down with 2-month notice
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.
Proprietary query language becomes worthless
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.
No self-hosting fallback available
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.
Data access lost after deadline
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.
Open-source promise unfulfilled
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.