# Shared Edition 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 Shared workspace to use SingleStore Helios. A Shared workspace uses a shared compute environment and allows users to create a single database for their needs. To learn more about Shared Edition limitations, refer to [Configuration Limits for Shared Workspaces](https://docs.singlestore.com/#section-idm4517573019484834098204976897.md) and [Operational Limits for Shared Workspaces](https://docs.singlestore.com/#section-idm4594624572019234098224277745.md). Considerations: * Each Shared workspace is allowed to have only one database. * Shared workspaces can only be deployed in AWS US-EAST-1 region. If you require a deployment in a specific region of AWS, or in a different cloud provider (GCP or Azure), spin up a regular workspace in SingleStore Standard or Enterprise edition. * Shared 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 latest SingleStore features. * Shared workspaces are **not intended for Benchmarking**. Use a Standard workspace to take full advantage of SingleStore's performance capabilities. ## Configuration Limits for Shared Workspaces | Configuration Option | Limit | | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Cloud Service Provider and Region | Sharedworkspaces can only be deployed in AWS US-EAST-1 region. | | SingleStoreVersions and Upgrades | The underlyingworkspaceis automatically upgraded once the latest version ofSingleStorebecomes available. | | # of SharedWorkspaces | Unlimited. | | WorkspaceSize | You cannot configure memory or vCPU size for Sharedworkspaces. | | Naming Databases | You must select a unique name for your database in a Sharedworkspace. There is a single global namespace for all databases on a Sharedworkspace.

๐Ÿ“ Note:

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

| | Naming Database Users | You must select a unique name for your database users in order for them to accessย a Sharedworkspace. There is a single global namespace for all database users.

๐Ÿ“ Note:

Only your database users have permissions to access your database in a Shared workspace.

| | Automated Backups | Not supported. | | Moving to Standard and EnterpriseWorkspaces | To move data, back up a database and then restore it to a Standard or Enterprise project. | | 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 accessible from anywhere by default). | | Audit Logging | No support for audit logs. | | SingleStoreStage | SupportsSingleStoreStage up to 10 GB of storage. | | Updating Global Variables | Users cannot change global configurations for their deployments. | | Support for`CREATE DATABASE`and`DROP DATABASE` | These SQL commands are disabled for Sharedworkspaces. To drop your database, you need to terminate the Sharedworkspaceusing the UI. | ## Operational Limits for Shared Workspaces | Component | Limit | | ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | # of SharedWorkspaces per Org | Unlimited. | | # of Databases per SharedWorkspace | 1You cannot use`DROP DATABASE`command on the Sharedworkspace. To drop your database, you need to terminate the Sharedworkspaceusing the UI. | | # of Tables per Database | 10 | | # of Reference Tables | No reference tables. | | # of Rowstore Tables | No rowstore tables. | | # of Pipelines | 10

๐Ÿ“ Note:

CDC-in pipelines are not supported in Shared Edition (Shared workspaces). To ingest data using CDC, SingleStore recommends using SingleStore Flow or a Standard/Enterprise deployment instead.

| | # of Stored Procedures and User-Defined Functions | 10 | | Data Size | 1 GB of compressed data.SingleStoretypically sees 75% compression on average, depending on the data set. Refer to[SingleStore Helios Sizing Guidelines](https://docs.singlestore.com/cloud/getting-started-with-singlestore-helios/singlestore-helios-sizing-guidelines.md)for more information. | | # of Database Users | 3 Users. Users can be admin or Read only. | | # of Concurrent Incoming Connections | 100 | *** Modified at: May 13, 2026 Source: [/cloud/getting-started-with-singlestore-helios/about-singlestore-helios/singlestore-helios-editions/shared-edition/](https://docs.singlestore.com/cloud/getting-started-with-singlestore-helios/about-singlestore-helios/singlestore-helios-editions/shared-edition/) (An index of the documentation is available at /llms.txt)