SingleStore review

SingleStore is a database built to run transactions and analytics on the same system. The pitch is that applications and AI agents can query current business data without moving it first into a separate analytics store. That makes it a candidate for mixed workloads—not an automatic replacement for every database in a stack.

The product also includes Analyst, which plans and runs database queries from plain-English questions, and Context Engine, which maps schemas, relationships, and definitions for users and agents. The homepage says the engine is designed for millisecond query responses; that is a design claim, not a workload-specific guarantee. It also describes connecting operational data to open formats such as Apache Iceberg, plus natural-language analysis.

Pricing is usage-based for cloud compute. The Shared plan is free for one workspace, while Standard starts at $0.99 per hour and Enterprise at $1.49 per hour, according to the pricing page. Storage is billed separately, and no monthly or annual plan price is published.

The clearest case is a workload where fresh operational data needs to support analytics or application queries without a separate reporting pipeline. One engine can reduce the number of systems to coordinate, and the Analyst and Context Engine features are aimed at making that data easier for people and agents to query. Whether that replaces other tools depends on your workload and the features you need.

The pricing page gives teams a way to start small: Shared includes one free workspace, SQL and programmability features, monitoring, and self-support. Standard is aimed at general-purpose production workloads and lists read replicas, database branching, 30-day monitoring, and a 99.9% SLA in one availability zone or 99.99% in two. Enterprise starts at $1.49 per hour and lists online point-in-time recovery, Smart DR, audit logging, and customer-managed encryption keys.

That is a useful set of production options to price against a multi-system setup. A commenter in a Reddit thread described SingleStore’s sweet spot as a blend of transactions and analytics, while cautioning that a classic single-machine application workload may be better served by PostgreSQL. That is a reasonable distinction to test against your own workload before switching.

The pricing is not a simple monthly subscription. Standard starts at $0.99 per hour and Enterprise at $1.49 per hour, but the pricing page does not publish monthly or annual totals. Storage is charged separately, with listed examples of $0.023 and $0.025 per GB; optional SingleStore Flow also has separate compute and processing rates. Commitment pricing is available, but its rates are not published. Model compute, storage, and any add-ons against your actual usage before comparing it with your current stack.

The free plan is one shared workspace for evaluation, development, and testing, with self-support; the published pricing details do not list a free trial or additional free-workspace allowance. Don’t assume the hybrid pitch means full feature parity with dedicated databases. In one Reddit discussion, a user reported comparable performance to PostgreSQL on their workload but cited reduced features and compatibility. A SingleStore employee in that thread said regular transactions support READ COMMITTED isolation and SNAPSHOT is used for backup. Another employee acknowledged the storage format is not open. Those are discussion comments, not a substitute for checking current product documentation and migration requirements.

SingleStore’s Shared plan is free for one workspace, with SQL and programmability features, monitoring, and self-support. It is positioned for evaluation, development, and testing—not as a published-price production plan.

For production, the pricing page lists Standard starting at $0.99 per hour and Enterprise starting at $1.49 per hour. That is a $0.50-per-hour starting-rate gap, but neither tier has a published monthly or annual price. Standard includes read replicas, database branching, 30-day monitoring, and a 99.9% SLA in one availability zone or 99.99% in two. Enterprise adds online point-in-time recovery, Smart DR, audit logging, and customer-managed encryption keys.

Budget separately for storage: examples are $0.023 or $0.025 per GB. Optional SingleStore Flow lists compute at $3.96 per credit and data processing at $0.02 per GB. Commitment pricing is available, but its rates are not published. Price compute, storage, and any add-ons against your workload before comparing the hourly starting rates with a fixed monthly database bill.

Treat a move to SingleStore as an application and data-model review, not just a database replacement. Its pitch is one engine for transactions, analytics, and context, with SQL and programmability features on the Shared plan. Check that your workload fits that model, and validate how your existing applications and queries use the database. The published material does not detail migration tools, supported source databases, or export procedures, so confirm those with SingleStore before planning a cutover.

Portability deserves the same scrutiny. SingleStore connects operational data to open formats such as Apache Iceberg, but that is not a promise that every workload can move freely between systems. Ask what data can be exported, in what format, and at what cost; those terms are not published here. We also can’t responsibly name reasons people leave based on Reddit: no Reddit posts or comments were included in the published material. For a move away, verify export options and rebuild requirements before committing production workloads.