FiloDB vs SiriDB
FiloDB
github.comSiriDB
siridb.comSide by side
| Figure | FiloDB | SiriDB |
|---|---|---|
| Price from | Free | €150/mo |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 3 |
| Spec score · Time-Series Databases | 8.1 (#12) | 7.5 (#27) |
| Deployment | 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. | The server can be installed from a Debian package, compiled on Linux or OSX, or run with Docker. |
| Integrations | The README describes using FiloDB as a Grafana data source through its Prometheus-compatible HTTP API and identifies Cassandra as its persistence store. | The maker lists a Grafana data source plugin and native connectors for C/C++, Python, Go, and Node.js. |
| License | The repository identifies Apache-2.0 as its license. | The multi-node clustering version is available as open source under the MIT license. |
| Product | FiloDB is an open-source distributed, real-time, in-memory time-series, event, and operational database with Prometheus query support. | SiriDB is an open-source time-series database for analyzing and aggregating time-series data from sources including IoT and financial transactions. |
| Querying | FiloDB supports PromQL through an HTTP API and CLI, and the README says its PromQL support is about 60%. | Its custom query language supports dynamic grouping of time series and distributed queries across pools. |
| Support | The repository invites contributions; it does not state a paid support plan on the README page. | Community support is available through Slack and GitHub, and commercial support packages include remote monitoring and health checks. |
Plans
SiriDB
- Basic support€150 a month
- Standard support€400 a month
- Premium support€800 a month
In their own words
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.