Compare all

Ably vs

Let us help you discover why Ably is clearly the better choice.

Easily build complete, trusted realtime functionality.

Take our APIs for a spin
Why it matters?
Global datacenters locations 15 3-6

As we have datacenters globally, we can ensure that your users always experience the lowest possible latency by connecting to the closest datacenter, and have complete availability by connecting to alternative healthy datacenters when necessary. approximately 3-6 datacenters spread across three geographical locations, Europe, US East and US West. Customers that are not close to those datacenters may experience some latency.

Find out more about Ably's datacenters
Latency based routing

Both Ably and offer latency based routing that ensures users anywhere in the world connect to the closest datacenter available to them.

Find out more about Ably's latency based DNS
Binary encoded messages

Encoding messages in binary format is faster. It reduces bandwidth to send and receive messages, and streamlines the processing time for clients and servers when encoding and decoding messages. does not support binary encoded messages.

Find out more about our binary protocol
Redundancy and Reliability
Mesh architecture / no central point of failure / self-healing cluster Unknown

The Ably platform is designed with no single point of failure and to be self-healing. All our customers benefit from their apps running on all of our datacenters providing resilience, reliability and low latencies globally.

Find out more about Ably's mesh architecture
Autonomous datacenters Unknown

Ably's servers are located in 15 datacenters covering 4 continents with each datacenter designed to operate as part of the global cluster when available, but operate autonomously when necessary.

Find out where Ably's servers are located
Data replicated in multiple regions

Ably stores every message in at least two datacenters and separate geographical regions. This ensures that an outage in any datacenter or region cannot result in data loss. does not persist messages so any message lost in transit is never recovered.

Find out about Ably's QoS and message delivery guarantee
QoS & message delivery guarantee

Ably provides guaranteed message delivery and continuity across disconnections. Publishers only receive an ACK when data is persisted in two locations, and subscribers never lose data during brief disconnections as we maintain connection state for each client on our servers.

With, if a message is published whilst a client is briefly disconnected (such as going through a tunnel or changing networks), then the message will never arrive to that client.

Find out about Ably's message delivery guarantee
Uptime SLA guarantees

Ably offers varying levels of uptime guarantees depending on your needs. For all of our enterprise customers we provide a 99.999% uptime SLA. offer an SLA only for corporate customers on custom packages.

Find out about Ably's uptime guarantees
Message and worker queues

Data published into Ably's realtime system can be moved into traditional message queues for realtime or batch processing. does not offer message queuing features or a means to distribute data using once-only pattern to your server workers.

Find out more about our Reactor Queues

Ably's Webhooks provide a means to get messages, channel lifecycle and present events pushed to your servers over HTTP. Both Ably and support Webhooks.

Find out more about Webhooks
Serverless cloud function invocation Partial

Ably can trigger serverless functions on any third platforms such as Amazon Lambda, Microsoft Azure or Google Function. recommends the use of a generic Webhook to be delivered to an API Gateway that in turn triggers a function.

Find out more about Reactor Events

Presence allows you to subscribe to events when users or devices enter or leave channels. This is a useful feature for collaborative apps, games and chat rooms. supports a maximum of 100 members per channel. Ably supports 200 by default and far more upon request.

Find out more about Presence
Message history

Ably's message history feature provides a means for clients or servers to retrieve messages that were previously published on a channel. does not support message history.

Find out more about our History API
Realtime data firehose

Stream your realtime data published within the Ably platform directly to another streaming or queueing service such as Amazon Kinesis, Apache Storm or Kafka.

Find out more about our Reactor Firehose
Reliable message ordering

Ably ensures that messages are delivered to persistently connected subscribers in the order they were published on each channel. does not provide these guarantees.

Find out more about reliable ordering
Push notifications

Both and Ably offer push notifications.

Find out more about Push Notifications
Message and worker queues

Data published into Ably's realtime system can be moved into traditional message queues for realtime or batch processing. does not offer any message queuing features or ways to distribute data using once-only pattern to your server workers.

Find out more about our Queues
Custom domain endpoint (CNAME)

Ably supports custom domains for our Enterprise customers allowing them to connect to Ably using a CNAME such as "". does not provide support for custom CNAME endpoints.

Find out more about our custom domains
Client libraries and protocol support
Native client libraries for every popular platform

Both Ably and offer a considerable range of client libraries for every popular platform.

View our client library SDKs
Embedded devices Limited

Using our protocol adapters, our customers can use the large selection of PubNub embedded client libraries for low energy and other embedded devices. has a small set of client libraries suitable for embedded devices.

See the list of supported embedded libraries
MQTT support

The Ably platform is designed to be protocol-agnostic and ensure protocol interoperability. Ably supports MQTT./p> does not support MQTT.

Find out which protocols we support
SSE protocol support

The Ably platform is designed to be protocol-agnostic and ensure protocol interoperability. That's why we support SSE. does not support SSE.

Find out which protocols we support
White-label browser library

Ably can provide a white-labelled browser Javascript library with a namespace of your choosing and no reference to Ably in the code. does not, as far as we are aware, offer white-label libraries.

Find out about our white-label libraries
Continuity and connection state recovery

Ably provides continuity for clients that become disconnected for reasons such as going through a tunnel or changing networks. Ably stores the connection state for each client on its servers so that clients that reconnect within two minutes can resume their connection and receive all messages published whilst they were disconnected.

With, if a message is published whilst a client is not connected, then the message is effectively lost and will never be delivered to that client. expects the developer to handle data loss due to loss of connectivity.

Find out more about connection state recovery
1st class WebSocket support

WebSockets are widely regarded as the most efficient HTTP compatible transport for full duplex realtime communication between devices.

View our supported transports
Fallback to Comet (XHR) and Long Polling for older browsers

Whilst most modern devices support WebSockets, there are situations where the device or the network environment requires use of HTTP transports.

View our supported transports
TLS connection

Both Ably and offer TLS connections ensuring that all data in transit is encrypted.

Find out more about SSL/TLS
Token based authentication

Token based authentication ensures your private key is never shared and instead a short-lived token is used to authenticate.

Ably and allow configurable policies to be embedded in a token ensuring you have complete control over what actions your users can perform such as limiting which channels they can subscribe or publish to.

Find out more about Ably's authentication
JSON Web Token support

Using JWT allows for easy integration with your existing authentication systems, along with ensuring your private key is never shared.

Ably allows for not only Ably Tokens to be embedded within JWTs, but also for JWTs to be signed by Ably API keys and used themselves for authentication.

Realtime does not support JWT.

Find out more about using JWT with Ably
Configurable private key permissions

Ably provides support for private API keys with configurable permissions including restrictions on channels or operations. does not support configurable permissions for keys.

Find out more about API keys
Configurable channel permissions

Ably provides channel rules providing you with the flexibility to maintain control of your channels, such as requiring SSL/TLS or only identified authenticated clients on a channel. does not provide channel configuration rules.

Find out more about channel rules
Encrypted message payloads

Ably's AES encryption allows messages to be encrypted using the provided private key before they are published to Ably. As a result, messages are practically impossible intercept and view for anyone including Ably. For very sensitive data, this ensures you can safely use us knowing your payloads are always secure and opaque. does not provide payload encryption in their client libraries.

Find out more about Ably's encryption

* All information regarding our competitors was obtained on or before January 2016. It is therefore possible that some of this information may now be out of date. If you believe that any of this information is incorrect, please get in touch with us so that we can correct it immediately.

Migrating to Ably

Join the others and upgrade your realtime platform.

  • We're happy to offer technical assistance from our engineering team to customers moving across from

    Get in touch for help
    Get in touch for help