Ably enables real-time communication and live data updates across our application. We use Ably whenever we require instant delivery of events, live updates without page refresh, and seamless synchronization between multiple users and systems. It is especially useful in scenarios where speed, reliability, and scalability are critical. Ably acts as the backbone for our real-time layer, allowing the front-end and back-end systems to stay in sync at all times.

We use Ably for real-time notifications and status updates for our application. Whenever a user performs any action, submits data, or triggers any event, the back-end publishes an event to our Ably channel and all subscribed clients instantly receive the updates. All updates are pushed instantly to our connected users, and message delivery remains reliable even during high traffic. Ably also handles our connection management, automatic reconnections, and message ordering and delivery guarantees.

The best feature I appreciate about Ably is the real-time messaging and Pub/Sub channels. It provides a high-throughput publish and subscribe model for our real-time data delivery, ensuring instant event propagation across clients with minimal latency. It supports both private and public channels for fine-grained access control.

The second feature I value most about Ably is automatic connection management, which includes handling of connection drops and network reconnection logic, along with session resumption. This saves our engineering time compared to manual WebSocket management. I also appreciate the global edge network feature; Ably's infrastructure is geographically distributed worldwide, ensuring low latency across our regions and a consistent real-time experience for global users.

The most reliable feature I depend on day-to-day is automatic connection management. In real-world applications, network reliability is never perfect; users switch between Wi-Fi and mobile data, connections drop unexpectedly, and browsers may go to the background or sleep. Ably automatically handles reconnecting clients, resuming sessions, and maintaining message continuity, which removes substantial complexity from our codebase. This has significant day-to-day impact on the development and operations of our company as we no longer need to write custom retry logic, manage WebSocket reconnect loops, or handle edge cases for dropped connections. Our developers can focus on business logic, product features, and user experience, which reduces bugs related to real-time failures and support issues caused by missed updates.

Ably has definitely impacted my organization positively. It improves the real-time user experience by enabling us to deliver instant updates across our application. Users no longer need to refresh pages or wait for delayed updates, resulting in smoother workflows, faster response times, and higher user satisfaction. It has reduced our engineering complexity; before Ably, our teams spent a significant amount of time managing WebSocket infrastructure, connection drops, retries, and message ordering and delivery guarantees. Ably handles these concerns out of the box, leading to faster development and feature delivery. Developers are able to implement real-time features quickly and reuse Ably's SDKs across platforms, shortening our development cycle and helping us release features faster and respond more quickly to business requirements.

We have seen positive metrics, the most noticeable being time savings in development and maintenance. By using Ably, we eliminate the need to build and maintain custom real-time infrastructure, and our developers no longer spend time handling WebSocket reconnections. It saves us approximately thirty to forty percent of our development time. We have also seen faster delivery of our features, shortening our release cycles. Real-time features that previously took weeks to stabilize can now be implemented much faster, in three to four days. Teams are able to prototype real-time functionality quickly and move features to production with more confidence.

Every software platform has opportunities for improvement. The first improvement I see is that local development and testing experience can be improved. Testing real-time flow locally can still be challenging for us, and better tooling for mocking or simulating Ably events, along with better support for testing reconnections and failure scenarios, would help our teams validate behavior before moving to production.

While basic metrics are available, deeper observability could be beneficial, including enhancements such as more granular and real-time dashboards, easy integration with third-party monitoring tools, and clear visibility into message flow and latency.

Regarding pricing, usage-based pricing can sometimes be hard to forecast at scale, and our teams may want a clearer cost estimation tool. Improved cost visibility and forecasting would help with budgeting.

Ably should provide more pre-built patterns or templates for chats and notification collaboration features, which could further speed up our process and adoption of Ably.

I have been working in my current field for the last five years, and I have been using Ably for approximately two and a half years.

Ably is quite stable. Messages are delivered even with intermittent network conditions, and automated reconnection ensures clients reattach to channels after disconnection without manual intervention. We have experienced very few outages or service interruptions, and planned maintenance and updates do not adversely affect our production workloads. Ably's global edge network distributes traffic intelligently, minimizing single points of failure. After we adopted Ably, incidents and support alerts related to the real-time system dropped significantly compared to our custom WebSocket deployment. Ably handles retries, resends, and session recovery internally, reducing stability issues caused by client code complexity.

Ably is highly scalable. My experience confirms that it can handle a large number of users, devices, and events without performance issues. Ably's global edge network allows messages to be delivered with low latency worldwide, and users in different regions experience consistent performance even during high traffic, with no manual provisioning of regional servers needed.

I have not been very active or interacted much with customer support, but I have heard from a few of my teammates that their experience with Ably's customer support has been very positive, responsive, and helpful, especially for real-time product questions and troubleshooting. Support inquiries are generally answered quickly, often within hours, and there is rapid turnaround on technical questions that keeps development moving healthily. When issues are more complex, responses include helpful follow-ups and explanations. Support engineers have a strong understanding of real-time systems, providing insights on best practices and possible solutions rather than pointing to documentation.

Positive

I have not personally used any previous solution because when I joined my company, they were already using some local messaging tools. I was the one who started using Ably.

We have seen return on investment from Ably, where the ROI comes less from direct revenue and more from engineering efficiency, reduced operational overhead, and faster delivery of real-time features. We did not need to dedicate one to two engineers to manage WebSocket servers and scaling issues, allowing existing engineers to focus on product development instead of infrastructure, which saves our manpower. Development time for real-time features was reduced by thirty to forty percent, leading to quicker releases for production, as fewer development hours per feature were required after using Ably.

Overall, Ably's pricing felt fair and reasonable for the value it delivers. The pricing model is primarily usage-based, meaning we pay based on our actual consumption rather than large upfront fees, and the price scales naturally as our usage grows. This works well because we can start small and gradually scale without a large initial commitment. The licensing model is straightforward and flexible, with no complex or restrictive licensing, making it easier for us to experiment with new use cases and onboard new teams or applications without negotiating licensing. Setup costs were very low compared to building an in-house real-time solution, with no need to provision new servers or manage infrastructure setup.

Before choosing Ably, I evaluated other options. The options I assessed included custom WebSocket infrastructure, Firebase Realtime Database, and a Kafka plus WebSocket combination, each with its pros and cons, which led us to choose Ably.

My advice for others looking into using Ably is to evaluate their real-time needs first and take full advantage of Ably's SDK. Planning for scaling early is critical because even if initial user base is small, Ably scales globally without manual intervention. Familiarity with channel architecture, message throughput limits, and monitoring dashboards is important. Additionally, leveraging documentation and support, while keeping an eye on metrics such as messaging throughput, connection counts, and latency across regions, can be beneficial. Implementing token-based authentication and scoped channel permissions ensures secure access and prevents accidental exposure of sensitive channels.

Ably is a mature, reliable real-time platform that delivers consistent performance across our use cases. It combines low latency messaging, automatic connection management, global scalability, and a strong developer experience. These attributes have significant operational impact and business value.

I give Ably a nine out of ten overall because of its reliability, stability features, ease of use for developers, scalability, and global performance. I am not giving it a ten out of ten because I believe there are opportunities for improvement; it is not perfect. There is still room for improvement in advanced documentation, real-world examples, better cost visibility, and usage forecasting, as well as deeper built-in observability tools, which could elevate it to a ten out of ten.