CnosDB vs FiloDB
CnosDB
cnosdb.comFiloDB
github.comSide by side
| Figure | CnosDB | FiloDB |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | Yes | — |
| Open source | — | — |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 2 | 1 |
| Spec score · Time-Series Databases | 8.5 (#6) | 8.1 (#12) |
| Deployment | The installation guide provides a Docker command for running the community image. | FiloDB is deployed as standalone processes in a cluster and requires Java, Cassandra, Kafka, Rust, and a C compiler to build; SBT is also listed as a build prerequisite. |
| Integrations | The ecosystem integration page lists LangChain, Grafana, Jaeger, Kafka, Prometheus, Telegraf, TensorFlow, and Vector. | The README describes using FiloDB as a Grafana data source through its Prometheus-compatible HTTP API and identifies Cassandra as its persistence store. |
| License | The official site says the standalone, distributed, and ecosystem tools use the AGPL-3.0 open-source license. | The repository identifies Apache-2.0 as its license. |
| Product | CnosDB is an open-source distributed time-series database designed for high performance, compression, and ease of use. | FiloDB is an open-source distributed, real-time, in-memory time-series, event, and operational database with Prometheus query support. |
| Querying | CnosDB supports standard SQL and time-based aggregation queries. | FiloDB supports PromQL through an HTTP API and CLI, and the README says its PromQL support is about 60%. |
| Use cases | The stated application areas include IoT, industrial internet, connected vehicles, and IT operations. | Documented uses include operational metrics, distributed tracing storage, ad-hoc application-metric debugging, and real-time event storage and querying. |
Plans
In their own words
CnosDB
CnosDB is an open-source distributed time-series database for workloads such as IoT, industrial internet, connected vehicles, and IT operations. It supports standard SQL, time-based aggregation, and a DataFrame API. Data can be written without a predefined schema, including out of order, and historical data can be replenished. Ingestion methods include SQL, Line Protocol, OpenTSDB, Elasticsearch bulk, Loki, NDJSON, and OpenTelemetry. Deployment options include standalone, distributed, and storage-compute separated modes, on public, private, or hybrid clouds. The documentation describes horizontal scaling for storage and stateless compute nodes. Integrations include Grafana, Prometheus, Telegraf, JDBC, and a Python SDK; the open-source Python connector provides a PEP 249 interface for SQLAlchemy and pandas. Import and export formats include PARQUET, CSV, and JSON with AWS S3, Google Cloud Storage, and Azure Blob Storage. CnosDB documents retention policies, multi-tenancy, and role-based permissions, as well as optional TLS certificate and private-key settings. Community Edition is free under AGPL-3.0.
FiloDB
FiloDB is a free, Apache-2.0 open-source database for distributed, real-time time-series, event, and operational data. It is designed to ingest and query many millions of time series, sharding data across processes with distributed querying. Columnar compression and off-heap memory management support substantial in-memory storage while reducing garbage collection. PromQL is available through an HTTP API and command-line interface; the README describes support as about 60%. Histograms are a first-class column type, with the project reporting possible compression and query-speed improvements of up to two orders of magnitude. Typical ingestion uses Apache Kafka, while the Gateway accepts Influx Line Protocol over TCP. Grafana can connect through the Prometheus-compatible API, and Cassandra is identified as the persistence store. Deployment uses clustered standalone processes and requires Java, Cassandra, Kafka, Rust, a C compiler, and SBT to build.