# Simplified Cloud Pricing Based On Data Synced > Pro and Team plans now use one billing metric for data throughput: data synced. This replaces the existing sync operations and data processing metrics. We’re also increasing the overage rate for peak concurrent connections from $15 to $30 per 1,000. Overall, these changes should lower usage costs for everyone. - Published: 2025-09-12 - Author: Kobie Botha - Category: Announcement - Source: https://powersync.com/blog/simplified-cloud-pricing-based-on-data-synced --- ## TL;DR Pro and Team plans now use one billing metric for data throughput: _data synced_. This replaces the existing _sync operations_ and _data processing_ metrics. We’re also increasing the overage rate for _peak concurrent connections_ from $15 to $30 per 1,000. Overall, these changes should lower usage costs for everyone. ## Pricing challenges Since launching PowerSync Cloud pricing back in 2023, we've gathered enough data to analyze our customers’ actual usage patterns, associated invoices, and our related infrastructure costs. Three things stood out: 1. **_Sync operation_ billing spikes weren’t proportional to costs:** Customers often had big spikes in billing for sync operations, but our infrastructure costs didn’t spike in the same way. When there were excessive (and unexpected) spikes, we worked with customers directly to offset costs, but this was time-consuming for everyone involved. 2. **Not all sync operations carry the same amount of data** : `MOVE` and `CLEAR` operations typically contain very little data, but they were being billed the same as other operations. If developers didn’t defragment regularly, the number of billed sync operations could be an order-of-magnitude higher than the number of rows actually synced. [Defragmenting](https://docs.powersync.com/usage/lifecycle-maintenance/compacting-buckets#defragmenting) is still a good idea, but the pricing impact was not sufficiently warranted. 3. ** _Data processing_ and _peak concurrent connections_ were undervalued:** The overage rates for these metrics didn’t fully cover our infrastructure costs ## What is changing Here’s a refresher of how the billing metrics (mentioned above) are defined: * A _sync operation_ is when a single row is synced from the PowerSync Service to a client. * _Data processing_ is calculated as the sum of: * _Data replicated_ from your source database(s) to PowerSync Service instances * _Data synced_ from PowerSync Service instances to clients. * _Peak concurrent connections_ is the peak number of client connections active at the same time across all apps in your organization. _Data synced_ is now the only metric we use to measure data throughput for billing. _Sync operations_ and _data processing_ metrics have been removed. Additionally, the overage rate for peak concurrent connections will increase from $15 to $30 per 1,000 concurrent connections. Pro and Team plans are still usage-based: the base fee includes a certain baseline usage allowance, and usage overages beyond that have an additional cost. Here’s a summary of what’s changing: ### Pricing model comparison | Infrastructure component | Previous model | New model | | --- | --- | --- | | Replication operations (count) | _not billed_ | _not billed_ | | Data replicated (per GB) | Billed as data processing @ $0.15 per GB after the first 30 GB. | _not billed_ | | Sync operations (count) | $2.00 per 1,000,000 after the first 10,000,000. | _not billed_ | | Data synced (per GB) | Billed as data processing @ $0.15 per GB after the first 30 GB. | $1.00 per GB after the first 30 GB. | | Peak concurrent connections (count) | $15 per 1,000 after the first 1,000. | $30 per 1,000 after the first 1,000. | | Data hosted (per GB) | $1 per GB after the first 10 GB. | _no change_ | ### Previous model ![](https://powersync.com/images/blog/simplified-cloud-pricing-based-on-data-synced-inline-62f2253a5b.png) ### New model ![](https://powersync.com/images/blog/simplified-cloud-pricing-based-on-data-synced-inline-e31a16ef47.png) Our [pricing page](https://powersync.com/pricing) has been updated, and new customers are already on the new model. ## How we reasoned about it Our goal was to reduce the impact of sync operation spikes on customers, while making sure that our relevant infrastructure costs are covered. In practice, every sync operation already contributes to data processing, which can be calculated as: the number of operations synced × the average size of a row. So when you sync a row, it contributes to both the number of sync operations and to data processing. By removing sync operations as a separate billing metric, your usage is now mainly measured in data terms (GB). This is more intuitive for developers to reason about, keeps billing simpler, and ties in better with our actual cost driver — the infrastructure needed to move data. To make this sustainable, we had to look into increasing the $ rate for _data synced_ (in our current model this forms part of the _data processing_ line item). Historically, our infrastructure costs for replicating data have been lower than for syncing data. Increasing the rate for _data processing_ as a whole meant our customers would pay disproportionately more for replicating data. We therefore decided to drop _data replicated_ as a billing line item, and only bill _data synced_. We set the data synced rate to $1.00/GB, which is closer to our real infrastructure costs. Our infrastructure costs for handling concurrent connections are currently over $50 per 1,000 connections. The previous $15 rate was far below that. We’re raising it to $30 — still well under our actual costs — to strike a balance between covering more of the cost and avoiding too steep a jump for existing customers. Over time we hope we can lower costs for this metric by optimizing our infrastructure further. ## Impact on existing customers We looked at each of our existing Pro and Team plan customers’ historic usage and invoices, and simulated their future billing using the new model. The outcome: 99% of customers will be paying less under the new pricing model, assuming similar usage. We are working with existing customers to migrate them to the new pricing model and are aiming to have everyone migrated by 31 October 2025. If you have any questions, feedback or concerns about this update, please [get in touch](https://powersync.com/contact). Overall, we hope this will simplify billing and reduce billing surprises around sync operations.