Fauna, which wants to make adding a database a simple API call, adds $27M to its $25M Series A, bringing its total raised to $57M
Databases have always been a complex part of the equation for developers requiring a delicate balance to manage inside the application, but Fauna wants …
Context & Ripple Effects
Fauna's pitch is that provisioning and scaling a database should be an API call rather than an operations project, and investors just backed it twice in one raise: a [[a:none|$25M Series A extended by another $27M]], taking total funding to $57M. The timing matters — it lands in the same month that open-source rival MariaDB added a $25M extension to its own Series C while claiming a doubled valuation, signaling that database-layer capital was flowing broadly even mid-2020.
The arc since then validates the thesis from two directions. Access layers built on other people's databases got big fast: Hasura, which exposes databases through an open-source GraphQL API, went from a $25M Series B to a $100M Series C at a $1B valuation within roughly two years. And MotherDuck's later $52.5M Series B to commercialize DuckDB showed the money extending into rethinking what the database engine itself looks like.
First-order effects
- With $57M raised, Fauna gains extended runway to scale its serverless database platform and push the 'database as an API call' model against managed-database offerings from incumbent cloud providers.
Second-order effects
- Hasura's rapid climb to a $1B valuation on top of existing databases shows where adjacent value accrues — whoever owns the developer-facing access layer, not just the storage engine — forcing both Fauna and traditional vendors to treat API ergonomics as the competitive front.
Third-order effects
- If the pattern holds across Fauna, Hasura, MariaDB, and MotherDuck, database selection shifts from an infrastructure-ops decision made by platform teams to a usage-priced API chosen inline by application developers — restructuring how the category is sold and who signs off on spend.
The trend: Database infrastructure is being financialized and API-wrapped — provisioned per call, priced on usage, and funded at extension-round cadence — turning a procurement-heavy product category into consumable developer plumbing.