Yes, it is very as we have a Pusher protocol adaptor that allows customers who are migrating from Pusher to use the Pusher client libraries directly with our service. See article: Using the Ably Pusher protocol adaptor.


For example, a typical migration from Pusher to Ably goes as follows:

  • Initially a customer will simply change the host name for all of their Pusher client library integrations to use our endpoints.
  • A customer will then migrate one app at a time over to our Ably client libraries that provides access to all of our features.  At this stage, some of the customer's apps will be using Pusher client libraries and others will be using Ably's client libraries. However, as we are translating the Pusher protocol, there is no interruption and interoperability between both protocols is provided by Ably.
  • Customer will finally migrate all their apps and servers to use the Ably client libraries and will terminate their old contracts.


If you are interested in migrating from Pusher and want to use our protocol adaptors, please get in touch.


Find out more about our protocol agnostic approach to realtime, including support for the IoT focussed MQTT protocol.