Databases · head to head
FaunaDB vs Timeplus

FaunaDB
Databases
Document-relational database whose hosted service closed in 2025 and whose core is now unmaintained Apache 2.0 code.
- From
- Free
- Rated
- -

Timeplus
Databases
Streaming SQL engine built on ClickHouse internals, shipping as one small binary
- From
- Free
- Rated
- -
The short version
- Each has a real cost: 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.; Timeplus proton, the free version, is single-node by design, so any requirement for high availability or horizontal scale forces the commercial licence; the open source edition is a trial in practical terms.
- They diverge on capability: FaunaDB covers Document-relational model, Timeplus covers Streaming SQL.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which FaunaDB and Timeplus actually diverge.
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Databases).
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 Timeplus
- Streaming SQL
- Unified streaming and historical
- ClickHouse-based engine
- Single binary deployment
- External streams
- Materialised views
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 Timeplus
- Extracting historical data from a Fauna dataset that can no longer be reached through the hosted APInot Timeplus
- Studying a production implementation of deterministic distributed transactions, since the full server source is now readable under Apache 2.0not Timeplus
- Forking the engine deliberately, where an organisation has JVM and distributed-systems staff and wants a document-relational store it fully controlsnot Timeplus
Timeplus
- Real-time alerting on Kafka topics where standing up a Flink cluster is more work than the use case justifiesnot FaunaDB
- Fraud or anomaly detection that must join a live event stream against recent history in one querynot FaunaDB
- Streaming ETL from Kafka or MySQL change data capture into ClickHouse without writing Javanot FaunaDB
- A small data team that needs continuous aggregation but has no platform engineers to operate JVM infrastructurenot 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.
Timeplus
- Proton, the free version, is single-node by design, so any requirement for high availability or horizontal scale forces the commercial licence; the open source edition is a trial in practical terms.
- It is a young project against Apache Flink’s decade of production history, so the hiring pool, the connector library and the body of known failure modes are all much smaller.
- Inheriting ClickHouse internals also inherits ClickHouse constraints: memory-hungry queries, awkward updates and a SQL dialect that is not portable to other engines.
- Exactly-once semantics and state recovery guarantees are less battle-tested than Flink checkpointing, which matters if the pipeline moves money.
- Cloud pricing is by provisioned instance size rather than usage, so a bursty workload pays for peak capacity around the clock or has to be resized by hand.
Pricing, plan by plan
FaunaDB
Free- FreeFree
- 100K read ops
- 50K write ops
- 1GB storage
- Pro$25/month
- Pay per use
- Priority support
- Advanced features
Timeplus
Free- Timeplus ProtonFree
- Apache 2.0 licence
- Single node only
- Full streaming SQL engine
- Timeplus Cloud$199/month
- One to thirty-two CPUs
- 4 GB to 128 GB memory
- From 250 GB SSD storage
- Self-hosted or BYOC$undefined/year
- Multi-node clustering
- Kubernetes or bare metal
- Customisable compute and storage
Which should you pick?
Choose FaunaDB if
- You need document-relational model.
- You want to start without paying.
- You also want fql v10.
Choose Timeplus if
- You need streaming sql.
- You want to start without paying.
- You work on Linux, macOS, Docker, Kubernetes, Web.
- You also want unified streaming and historical.
Questions people ask
- Is FaunaDB or Timeplus better?
- Neither clearly leads. FaunaDB starts at Free and Timeplus at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, FaunaDB or Timeplus?
- FaunaDB starts at Free and Timeplus at Free.
- Does FaunaDB or Timeplus run on more platforms?
- FaunaDB runs on Web. Timeplus runs on Linux, macOS, Docker, Kubernetes, Web.
- 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 Timeplus is typically brought in for.
- What can FaunaDB do that Timeplus cannot?
- FaunaDB covers Document-relational model, FQL v10, Distributed ACID transactions, HTTPS access. Timeplus covers Streaming SQL, Unified streaming and historical, ClickHouse-based engine, Single binary deployment.
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.
Timeplus: Is Timeplus open source?
The core engine, Timeplus Proton, is Apache 2.0. Timeplus Enterprise and Cloud are commercial.
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.
Timeplus: What is the difference from Flink?
Timeplus is one binary with SQL as the only interface; Flink is a JVM cluster with a Java and SQL API and far more operational surface.
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.
Timeplus: Can Proton run in production?
It can, but it is single-node only, so there is no high availability without the commercial edition.
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.
Timeplus: How much is the cloud?
From 199 US dollars a month, sized by CPU and memory, with a fourteen day trial.
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 Amazon Aurora
- FaunaDB vs PostgreSQL
- FaunaDB vs Airtable
- FaunaDB vs Cockroach Labs
- FaunaDB vs BigQuery
- FaunaDB vs CouchDB
- FaunaDB vs CosmosDB
- FaunaDB vs ArangoDB
- FaunaDB vs Dgraph
- FaunaDB vs DynamoDB
- FaunaDB vs Google Cloud SQL
- FaunaDB vs Apache Pinot
- FaunaDB vs Amazon RDS
- FaunaDB vs Apache Pulsar
- FaunaDB vs Cassandra
- FaunaDB vs Amazon Redshift
- FaunaDB vs Apache Flink
- FaunaDB vs ClickHouse
- FaunaDB vs Materialize
- FaunaDB vs Redpanda
- FaunaDB vs NATS
- FaunaDB vs DuckDB
- FaunaDB vs Estuary
- FaunaDB vs RisingWave
- FaunaDB vs Meilisearch
- FaunaDB vs Neo4j
- FaunaDB vs OpenSearch
- FaunaDB vs Qdrant
- FaunaDB vs SingleStore
- FaunaDB vs TiDB
- FaunaDB vs Tinybird
- FaunaDB vs Apache Kafka
- FaunaDB vs Apache Druid
- Timeplus vs Amazon Aurora
- Timeplus vs PostgreSQL
- Timeplus vs Airtable
- Timeplus vs Cockroach Labs
- Timeplus vs BigQuery
- Timeplus vs CouchDB
- Timeplus vs CosmosDB
- Timeplus vs ArangoDB
- Timeplus vs Dgraph
- Timeplus vs DynamoDB
- Timeplus vs Google Cloud SQL
- Timeplus vs Apache Pinot
- Timeplus vs Amazon RDS
- Timeplus vs Apache Pulsar
- Timeplus vs Cassandra
- Timeplus vs Amazon Redshift
- Timeplus vs Apache Flink
- Timeplus vs ClickHouse
- Timeplus vs Materialize
- Timeplus vs Redpanda
- Timeplus vs NATS
- Timeplus vs DuckDB
- Timeplus vs Estuary
- Timeplus vs RisingWave
- Timeplus vs Meilisearch
- Timeplus vs Neo4j
- Timeplus vs OpenSearch
- Timeplus vs Qdrant
- Timeplus vs SingleStore
- Timeplus vs TiDB
- Timeplus vs Tinybird
- Timeplus vs Apache Kafka
- Timeplus vs Apache Druid
