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):
StageProduction ReadinessAPI StabilitySupportDocumentation
Experimental/Pre-AlphaNot production-ready; purpose is early exploration and proof of concept.API may change significantly or be removed.Not covered under SLAs.Limited or placeholder documentation.
Closed AlphaNot production-ready; purpose is early feedback and testing of new ideas.Subject to breaking changes.Not covered under SLAs.Limited or placeholder documentation.
Open AlphaNot production-ready; purpose is broader testing and wider public feedback.Subject to changes based on feedback.Not covered under SLAs.Basic documentation provided.
BetaProduction-ready for tested use cases.Fully stable; breaking changes clearly communicated.Covered under SLAs.Documentation provided; may contain known gaps.
GAProduction-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 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:
ChannelExample tagsUse for
Stable1.23.0, 1.23, 1Production
Next1.23.0-next, 1.23-next, 1-nextTesting upcoming releases
docker pull journeyapps/powersync-service:1.23.0
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:
Category / ItemStatus
Database Connectors
ConvexExperimental
SQL ServerBeta
MySQLBeta
MongoDBGA
PostgresGA
PowerSync Service
Open EditionGA
Enterprise Self-HostedGA
Sync StreamsGA
Postgres Bucket StorageGA
Client SDKs
High Performance DiffsExperimental
Tauri SDKAlpha
Rust SDKAlpha
Capacitor SDKBeta
TanStack QueryAlpha
Node.js SDKBeta
.NET SDKBeta
OP-SQLite SupportBeta
Flutter Web SupportBeta
React Native Web SupportBeta
Flutter SQLCipherBeta
Kotlin SQLite3MultipleCiphersBeta
Vue ComposablesBeta
Swift SDKGA
Kotlin SDKGA
JavaScript/Web SDKGA
Dart/Flutter SDKGA
React Native SDKGA
React HooksGA
ORMs/SQL Libraries
TanStack DB (JS)Alpha
GRDB (Swift)Alpha
Drift (Flutter)Beta
Drizzle (JS)Beta
Kysely (JS)Beta
Room (Kotlin)Beta
SQLDelight (Kotlin)Beta
Attachment Helpers
KotlinAlpha
SwiftAlpha
JavaScript (new built-in library)Alpha
Flutter (new built-in library)Alpha
.NETAlpha
Other
CLIBeta
Also see: