Skip to main content
Features in PowerSync are introduced through a phased release cycle to ensure quality and stability. Below is an overview of the release stages namely Experimental/Pre-Alpha, Closed Alpha, Open Alpha, Beta and GA (General Availability):

​
Service Release Channels

PowerSync Service releases are published to two channels:
  • Next: New releases are published here first. They run in internal and public testing for anything from a day to a couple of weeks.
  • Stable: Promoted from Next after that testing period. This is the most reliable release and is recommended for production.
A Stable release can include features that are not yet GA (Experimental, Alpha, or Beta stages). These are included when are sufficiently self-contained and low-risk, though they may still have known issues. The Next channel adds new features, fixes, or changes to stable functionality that need further validation.

​
PowerSync Cloud

Configure the channel per instance in the PowerSync Dashboard, under the instance’s Settings view. Select Stable or Next.

​
Self-Hosted (Open Edition)

Select a channel through the Docker image tag you pull:
Each release is published under several tags. The full version (1.23.0) is pinned to a single release. The shorter major and minor tags (1.23, 1) are rolling aliases that move to the latest matching release when a new one is published. The latest tag tracks the most recent stable build but is recommended for development only, since it can move across major versions. Pin a version tag for production. Development images may also be published for bleeding-edge features or hotfix testing. These are versioned as 0.0.0-dev-XXXXXXXXXXXXXX pre-releases.

​
Feature Status Summary

Below is a summary of the current main PowerSync features and their release states: Also see: