Feature Status
PowerSync feature states and their implications for factors such as API stability and support.
Features in PowerSync are introduced through a phased release cycle to ensure quality and stability. Below is an overview of the four release stages namely Closed Alpha, Open Alpha, Beta and V1:
| Stage | Production Readiness | API Stability | Support | Documentation |
|---|---|---|---|---|
| Closed Alpha | Not production-ready; purpose is early feedback and testing of new ideas. | Subject to breaking changes. | Not covered under SLAs. | Limited or placeholder documentation. |
| Open Alpha | Not production-ready; purpose is broader testing and wider public feedback. | Subject to changes based on feedback. | Not covered under SLAs. | Basic documentation provided. |
| Beta | Production-ready for tested use cases. | Fully stable; breaking changes clearly communicated. | Covered under SLAs. | Documentation provided; may contain known gaps. |
| V1 | Production-ready for all main use cases. | Fully stable; backwards compatibility maintained as far as possible; breaking changes clearly communicated. | Covered under SLAs. | Comprehensive and finalized documentation. |
Service Release Channels
PowerSync service features are deployed to different release channels throughout their lifecycle.
Open Edition
The latest stable PowerSync Docker image is available under the latest tag and can be pulled using:
Development images may be released for bleeding edge feature additions or hotfix testing purposes. These images are usually versioned as a 0.0.0-dev-XXXXXXXXXXXXXX prereleases.
Cloud Edition
In the PowerSync dashboard, developers can configure the service version channel for each instance under the General tab in the Edit Instance dialog.
Stable
The Stable channel provides the most reliable release of the PowerSync service. It includes features that may be in the V1, Beta, or Open Alpha stages. Open Alpha features in this channel are typically mature but may still have bugs or known issues.
Beta
The Beta channel builds on the Stable channel and includes new features, fixes, or modifications to existing stable functionality that may require additional testing or validation.
Was this page helpful?