SingleStore is a commercial distributed SQL database that runs transactional and analytical workloads in one engine, combining rowstore and columnstore tables with vector search, and delivered as the managed Helios service or self-managed.
Aggregators route queries across leaf nodes holding shards. Deploy self-managed from bare metal to Kubernetes, or use Helios, the managed service on AWS, Azure, and Google Cloud, where compute separates from object storage. Pricing is credit-based per compute hour; pipelines ingest from Kafka, S3, and CDC sources.
How SingleStore answers the questions OLAP Engines turns on.
| How it works | |
| Specialization | HTAP: one engine for transactions, analytics and vector search |
| SQL dialect | MySQL-compatible; MongoDB wire protocol via Kai |
| Joins | Full distributed joins, across row and column stores |
| Updates and deletes | Full transactional INSERT, UPDATE, DELETE |
| Ingest to queryable | Immediate on commit; pipeline ingest tuned by batch interval |
| Storage format | Rowstore and Universal Storage columnstore; Iceberg ingest |
| Compute and storage | Aggregators and leaves; Helios separates compute from object storage |
| Indexes | Rowstore skiplist; hash on both; columnstore sort key, fulltext, vector |
| Pre-aggregation | None: no materialized views; projections re-sort, not aggregate |
| Running it | |
| Concurrent users | High: workload manager queues by cost; add aggregators to scale |
vs SingleStore: Open source (permissive) · Self-hosted · Managed · Hybrid · Java, C++
vs SingleStore: Open source (permissive) · Self-hosted · Managed · Hybrid · Operational complexity: High · Java
vs SingleStore: Open source (permissive) · Self-hosted · Managed · Hybrid · Operational complexity: High · Java