We just shipped WebSockets for Laravel Cloud, the easiest way to add real-time features to your application.
WebSockets for Laravel Cloud are managed WebSocket clusters powered by Laravel Reverb. This means you can add real-time communication to your applications in just 10 seconds, and for up to 50% less than other third-party tools.
Simply pick the number of concurrent connections when setting up your cluster. Got multiple apps? Split your connections among different applications for greater cost efficiency. It's that easy.
Sign up for Laravel Cloud to add Laravel Reverb-powered WebSocket clusters to your apps in 10 seconds.
The Power of Laravel Reverb, Now Fully Managed
Real-time features are crucial for activation, retention, and engagement in an application. When users interface with a live chat, instant notifications, or real-time dashboards, the magic of "now" is undeniable.
However, building, scaling, and managing the underlying WebSocket infrastructure is anything but magical. It's painful, time-consuming, and complicated, and it takes precious time away from building features.
The Laravel community has come to know and love Laravel Reverb, the open-source, high-performance WebSocket server we released almost two years back. Reverb quickly became the go-to for Laravel developers implementing real-time features.
But since Reverb is an OSS package, hosting and scaling it still required managing servers or relying on separate third-party services.
Since the release of Laravel Cloud earlier this year, support for managed Reverb has become the single most requested feature from our Cloud customers, to the tune of countless "What's the ETA for Reverb in Cloud?", "Do you support Reverb?", and, my personal favorite, "Reverb when?".
Well, with WebSockets for Laravel Cloud, a fully managed Reverb cluster that is natively integrated into your Laravel Cloud experience, the answer is: Reverb now.
Simple Setup, Simple Scaling
In the spirit of Laravel Cloud's "it just works" ethos, we've made the experience of creating WebSockets clusters as simple as possible.
When you set up your cluster, you pick the number of concurrent connections it should be able to handle. This capacity can then be split into multiple applications, each sharing a portion of those connections for cost-effective resource management.
As soon as you add a WebSocket application to your Laravel environment, Cloud automatically populates all necessary environment variables. You don't have to look up keys or configure endpoints. You don't have to handle third-party vendors or separate billing.
It just works.
See WebSockets for Laravel Cloud in action, and check the code we used to build our demo app on GitHub.
Predictable Pricing
Simplicity isn't just about a beautiful UI, populating variables, and hands-off deployments.
It's also about making pricing predictable and easy to understand. We've kept the pricing for our Laravel Reverb-powered WebSocket clusters incredibly simple:
- You just pay for your maximum concurrent connections.
- Each concurrent connections tier includes a generous allowance of millions of messages.
- That's it.
No complex equation, no extra base plan, no cost-per-million-messages/minutes/channels confusion.
This simple, predictable model is designed to provide an incredibly low barrier to entry. In fact, our solution is up to 50% cheaper than some of our leading competitors. We want you to focus on building, not calculating costs.
Get Started with WebSockets for Laravel Cloud
WebSockets for Laravel Cloud frees you from handrolling another service or the hassle of third-party vendors and instead unifies another piece of your application architecture within Laravel Cloud.
It's a step closer to our mission of enabling developers to move to production quickly, eliminate infrastructure management, and enjoy the best developer experience along the way.
We build for developers who ship. Start integrating WebSockets for Laravel Cloud into your projects today.
Want to learn more?
- See WebSockets for Laravel Cloud in action.
- Check the code we used to build our demo app on GitHub.