LiveSync pricing

LiveSync is priced on the number of unique users that receive updates each month. Database changes, messages and connection time don't affect your bill.

Ably prices on monthly active users (MAUs). A user who interacts with your application counts once in a calendar month, whichever products they use, however many database changes they receive, however many channels they subscribe to, and however long they stay connected.

Monthly active users

An MAU is a unique clientId that is active during a calendar month. LiveSync publishes database changes from the database connector to the clients subscribed to them, and a clientId becomes active when a realtime client created from the device package connects to Ably to receive those changes. It is counted once for that month, whether it was active for a minute or every day.

Each clientId is counted once per app. The same user counts once whether they connect from one device or several, and whether they use LiveSync alone or LiveSync alongside Pub/Sub, Chat, Spaces, AI Transport or LiveObjects in the same app.

Identifying users

Because an MAU is identified by their clientId, the way you assign them decides what you are billed for:

  • Assign one clientId per user, and use it on every device and in every session. A user who connects from a phone and a laptop with different clientIds counts as two MAUs.
  • Never share a clientId between users.

Anonymous users

Users who are anonymous to your application still require a clientId. Generate an identifier for each anonymous user and store it on their device, so that a returning anonymous user counts only once. If your application generates a fresh identifier on every visit, each visit counts as a new MAU.

Servers

The database connector runs on your servers and publishes with the server package, so it is not counted as an MAU, however many changes it publishes or channels it publishes to. The same applies to any other realtime or HTTP client created from the server package.

If you call the REST API directly rather than through an SDK, declare the caller as a server. With API key authentication, add clientType=server as a request or connection parameter. With token authentication, add the x-ably-clientType claim with the value server to the JWT you issue to the server. A request that doesn't declare itself as a server is counted as a user.

Resource-based pricing

If your account is still on resource-based pricing, LiveSync is charged on what you use rather than on your number of MAUs: per million messages, per million channel minutes and per million connection minutes. Each database change the connector publishes counts as one inbound message plus one outbound message per subscriber, and each channel the connector publishes to counts as channel minutes while it is active. How messages are counted has the detail.

To move your account to MAU pricing, follow the migration guide.

Resource efficiency

Regardless of whether you are on MAU pricing or resource-based pricing, effectively managing resources is beneficial to your application:

  • Configure your database connector to publish only meaningful changes. Reducing the frequency of updates at the source directly reduces the number of messages.
  • Subscribe clients only to the channels where they need realtime updates. Fewer subscribers per channel means fewer outbound messages per update.
  • Detach from channels and close connections when they are no longer needed to tidy up resources.