Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
I have used pusher in my projects and felt unfair pricing for corporations/developers. After realizing this, I saw an opportunity for building an open-source platform for web-sockets. What is the main difference between socket.io and pusher? I want to know this as I am building an alternative to pusher with my team.
This project (netdevv-sockets) will be a partial open-source project, which will provide you the node-js server code for deploying your personal instance of netdevv-sockets on your infrastructure. The second service will provide you our optimized infrastructure with extra dev-tools.
Our motive behind this project: When you don't want to use our infrastructure and build your own - you can do so, with an open-source node-js based server.
Motive behind this post: Provide your views on web sockets and what features you as a modern developer want from a web-socket platform?
I have used pusher in my projects and felt unfair pricing for corporations/developers.
Are you aware of this new package, called 'Laravel Websockets' which is a free alternative to Pusher? It runs a local websockets server and fully integrates with Laravel's native broadcasting (Laravel Echo).
@JOHNBRAUN - It doesn't provide dev-ops and I prefer nodejs socket-server because of low latency, low-resource-usage, async functions, and analytics. And the flexibility to use nosql database makes it perfect for much more scalability and flexibility. No-offense to laravel-websockets, Its actually a great alternative for small apps or even for complex apps.
@smitpatelx What source are you talking about? ??
https://github.com/soketi/soketi should be what you want.
Pusher compatible open source nodejs websocket server (including metrics).
do not reinvent the wheel :-)
edit: never mind - 2 year old thread .. damn it @atta ksery :D
Please or to participate in this conversation.