SingleStore

The buyers SingleStore courts are application engineers and data architects who have outgrown a single MySQL or PostgreSQL instance and do not want to bolt a warehouse, a search cluster and a standalone vector store onto the same product. The SingleStore company page names SaaS builders, data leaders, architects and digital giants as its intended makers, and lists brands including Nvidia, Goldman Sachs, Adobe, Siemens, Hulu, Dell and Sony among customers.

Day-to-day access to SingleStore runs over the MySQL wire protocol, so ODBC and JDBC drivers, ANSI SQL and most BI connectors attach without application rewrites. Data arrives through bulk load, streaming pipelines, third-party integration tools or SingleStore Flow, the no-code replication and CDC product SingleStore launched in 2025 after acquiring BryteFlow. SingleStore Kai adds MongoDB wire-protocol compatibility, while notebooks, Database Branching and a Wasm-powered Code Engine give developers room to prototype against live workspaces.

On the AI layer, SingleStore ships Aura Intelligence, made up of Analyst and the Context Engine. Analyst takes a plain-English question, plans the query and executes it against the live SingleStore database rather than a nightly copy. The Context Engine publishes a shared map of schemas, relationships and definitions so agents stop rediscovering structure at runtime, which SingleStore argues cuts both query volume and token spend. The homepage also prints a 20ms SingleStore figure against a 2400ms traditional figure, which readers should treat as a vendor benchmark rather than an independent result.

Packaging on the SingleStore pricing page is usage-based, not per seat. Managed Shared is a free workspace scoped to evaluation, development and non-production testing with self-support. Managed Standard starts at $0.99 per hour and adds read replicas, Database Branching, 30-day monitoring, standard support and a 99.9% single-AZ or 99.99% dual-AZ SLA. Managed Enterprise starts at $1.49 per hour and layers on Online PITR, Smart DR (Preview), audit logging and customer-managed encryption keys. BYOC Standard runs Helios inside a customer VPC and the Self-Managed edition are both quoted by SingleStore sales, and new Standard users are offered $500 worth of free credits.

The real invoice arithmetic in SingleStore's worked examples is denominated in credits rather than the headline hourly sticker. SingleStore prices a credit at $3.96 and storage between roughly $0.023 and $0.025 per GB per month in its published scenarios. One SingleStore example — an S00 workspace running part-time across 20 days — bills 40 credits at $158.40 plus $6.90 of storage. A larger multi-tenant SingleStore example with S4 and S8 production workspaces reaches $35,006.40 of compute and $574.90 of storage in a month, and a Flow CDC example at F-3 size adds $2,679.77 of compute plus $204.80 for 10,240 GB processed. SingleStore does not charge for data ingress, though its notes warn a cloud provider still may.

Limits are worth naming plainly. The free SingleStore workspace is shared, self-supported and explicitly labelled non-production, so it is a sandbox rather than a starter tier for customer traffic. Disaster recovery and stricter security controls such as Smart DR, Online PITR, audit logging and CMEK live only in Managed Enterprise, and Smart DR is still marked Preview. SingleStore is a commercial product with no open-source core, so there is no community edition fallback if a commitment negotiation goes badly, and the hourly stickers convert into credits, making cost forecasting an exercise in workspace sizing rather than reading one number.

Against category peers, SingleStore sits between the OLTP databases and the columnar warehouses instead of inside either camp. Compared with a warehouse-first product, SingleStore accepts low-latency single-row writes; compared with a general-purpose relational engine, SingleStore adds columnstore analytics, vector indexing and full-text search under the same SQL surface, and connects to Apache Iceberg for open lakehouse access. Teams already running a lake plus a warehouse plus a vector database are the ones most likely to find the SingleStore consolidation argument worth pricing out.