Shared Edition


This is a Preview feature.

SingleStore provides a free entry point to get started with SingleStore Helios for low-throughput and prototype applications. In the Shared Edition, users create a Starter Workspace to use SingleStore Helios. A Starter Workspace uses a shared-compute environment and allows users to create a single database for their needs. To learn more about Shared Edition limitations, see Configuration Limits for Starter Workspaces and Operational Limits for Starter Workspaces.


  • All Starter Workspaces deploy on the latest version of SingleStore; however, not all functionality included in the latest version is supported in the Shared Edition.

  • An organization can only create one Starter Workspace. Each Starter Workspace is allowed to have only one database.

  • Starter Workspaces can only be deployed in AWS US-EAST-1. If you require a deployment in a specific region of AWS, or in a different cloud provider (GCP, Azure), spin up a regular workspace in SingleStore standard or premium edition.

  • Starter Workspaces are not intended for Production use. Use a Standard Workspace for high-traffic, compute-intensive apps for production workloads. These workspaces support read-replicas, shared deployments, and have full-access to all our latest features.

Configuration Limits for Starter Workspaces

Configuration Option


Cloud Service Provider and Region

Can deploy a Starter Workspaces only in AWS US-EAST-1.

SingleStore Versions and Upgrades

The underlying workspace is automatically upgraded once the latest version of SingleStore becomes available.

# of Starter Workspaces

You may deploy only one Starter Workspace per org.

Workspace Size

You cannot configure memory or vCPU size for Starter Workspaces.

Naming Databases

You will need to select a unique name for your database in a Starter Workspace. There is a single global namespace for all databases on a Starter Workspace.


While database names have to be unique – your data is fully isolated from all other databases and organizations.

Naming Database Users

You will need to select a unique name for your database users in order for them to access  a Starter Workspace. There is a single global namespace for all database users.


Only your database users will have permissions to access your database in a Starter Workspace.


No backups.

Upgrades to Standard and Premium Workspaces

SingleStore is working on providing a UI to upgrade your Starter Workspace to a Standard Workspace.

In the meantime, reach out to our team through the Chat feature in the Portal and we can help preserve your database as you upgrade to Standard.

Advanced Security and Routing

No support for Private Links, SSO, or CMEK.

Configuring Firewall Access

No support to configure where your database can be accessed from (it is accessibly from anywhere by default).


No support for audit logs.

Support for SingleStore Stage

No support for SingleStore Stage Storage system yet.

Updating Global Variables

Users cannot change global configurations for their deployments.


These SQL commands are disabled for Starter Workspaces. To drop your database, you will need to terminate the Starter Workspace using the UI.

Operational Limits for Starter Workspaces



# of Starter Workspaces per Org


# of Databases per Starter Workspace


You cannot use DROP DATABASE syntax on the Starter Workspace. To drop your database, you will need to terminate the Starter Workspace using the UI.

# of Tables per Database


# of Reference Tables

No reference tables.

# of Rowstore Tables

No rowstore tables.

# of Pipelines


# of Stored Procedures and User-Defined Functions


Data Size

1GB of compressed data. SingleStore typically sees 75% compression on average, depending on the data set. See more on our SingleStore Helios Sizing Guidelines.

# of Database Users

3 Users. Users can be admin or Read only.

# of Concurrent Incoming Connections


Last modified: February 26, 2024

Was this article helpful?