Alternatives to Pusher logo

Alternatives to Pusher

PubNub, SignalR, Firebase, Chat by Stream, and Twilio are the most popular alternatives and competitors to Pusher.
486
1.1K
+ 1
228

What is Pusher and what are its top alternatives?

Pusher is the category leader in delightful APIs for app developers building communication and collaboration features.
Pusher is a tool in the Realtime Backend / API category of a tech stack.

Top Alternatives to Pusher

  • PubNub

    PubNub

    PubNub makes it easy for you to add real-time capabilities to your apps, without worrying about the infrastructure. Build apps that allow your users to engage in real-time across mobile, browser, desktop and server. ...

  • SignalR

    SignalR

    SignalR allows bi-directional communication between server and client. Servers can now push content to connected clients instantly as it becomes available. SignalR supports Web Sockets, and falls back to other compatible techniques for older browsers. SignalR includes APIs for connection management (for instance, connect and disconnect events), grouping connections, and authorization. ...

  • Firebase

    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • Chat by Stream

    Chat by Stream

    Chat API and SDK. With a beautiful UI Kit, easy to use React Components and powerful API. Add Chat to any application in a matter of hours. The tech uses Go, RocksDB and Raft. By the creators of Stream, the API that powers activity feeds for more than 300 million users. ...

  • Twilio

    Twilio

    Twilio offers developers a powerful API for phone services to make and receive phone calls, and send and receive text messages. Their product allows programmers to more easily integrate various communication methods into their software and programs. ...

  • Socket.IO

    Socket.IO

    It enables real-time bidirectional event-based communication. It works on every platform, browser or device, focusing equally on reliability and speed. ...

  • Google Cloud Pub/Sub

    Google Cloud Pub/Sub

    Cloud Pub/Sub is a fully-managed real-time messaging service that allows you to send and receive messages between independent applications. You can leverage Cloud Pub/Sub鈥檚 flexibility to decouple systems and components hosted on Google Cloud Platform or elsewhere on the Internet. ...

  • NATS

    NATS

    Unlike traditional enterprise messaging systems, NATS has an always-on dial tone that does whatever it takes to remain available. This forms a great base for building modern, reliable, and scalable cloud and distributed systems. ...

Pusher alternatives & related posts

PubNub logo

PubNub

168
379
228
Build real-time apps quickly and scale them globally.
168
379
+ 1
228
PROS OF PUBNUB
  • 33
    Massively scalable & easy to use
  • 24
    Easy setup
  • 18
    Great support
  • 18
    Reliable
  • 14
    Flexible to integrate to custom applications
  • 13
    High-Performance
  • 12
    99.999% availability guarantees
  • 12
    Sockets at Scale
  • 12
    Multiplexing
  • 11
    High-Reliability
  • 7
    Scalability
  • 5
    High-Availability
  • 5
    70+ SDKs
  • 4
    Azure Add-on
  • 4
    Security
  • 3
    Presence
  • 3
    Heroku Add-on
  • 3
    Flexible
  • 3
    Easy to setup
  • 2
    Data Sync
  • 2
    AngularJS Adapter
  • 2
    PhoneGap Plugin
  • 2
    Server-Side Cache
  • 2
    Free Plan
  • 2
    Support
  • 2
    Analytics
  • 2
    Data Streams
  • 1
    Easy setup and very reliable
  • 1
    Real time and easy to use.
  • 1
    High cost, going up more in Summer '15
  • 1
    Cool
  • 1
    CTO stephen also is A++++++
  • 1
    Angular 2+ integration
  • 1
    Documentation, easy to use, great people/service
  • 1
    Easy integration with iOS apps
CONS OF PUBNUB
    Be the first to leave a con

    related PubNub posts

    Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?

    See more
    Shared insights
    on
    PubNub
    Socket.IO

    I am trying to replace Socket.IO with PubNub. Provide the way to do it.

    See more
    SignalR logo

    SignalR

    342
    882
    94
    A new library for ASP.NET developers that makes developing real-time web functionality easy.
    342
    882
    + 1
    94
    PROS OF SIGNALR
    • 20
      Supports .NET server
    • 14
      Real-time
    • 12
      Free
    • 11
      Fallback to SSE, forever frame, long polling
    • 11
      WebSockets
    • 7
      Simple
    • 7
      JSON
    • 5
      Open source
    • 4
      Cool
    • 3
      Ease of use
    CONS OF SIGNALR
    • 1
      Requires jQuery
    • 1
      Expertise hard to get
    • 1
      Weak iOS and Android support

    related SignalR posts

    Firebase logo

    Firebase

    24.5K
    20.6K
    1.9K
    The Realtime App Platform
    24.5K
    20.6K
    + 1
    1.9K
    PROS OF FIREBASE
    • 361
      Realtime backend made easy
    • 263
      Fast and responsive
    • 234
      Easy setup
    • 207
      Real-time
    • 186
      JSON
    • 127
      Free
    • 121
      Backed by google
    • 81
      Angular adaptor
    • 63
      Reliable
    • 36
      Great customer support
    • 26
      Great documentation
    • 23
      Real-time synchronization
    • 20
      Mobile friendly
    • 17
      Rapid prototyping
    • 12
      Great security
    • 11
      Automatic scaling
    • 10
      Freakingly awesome
    • 8
      Chat
    • 8
      Angularfire is an amazing addition!
    • 8
      Super fast development
    • 6
      Awesome next-gen backend
    • 6
      Ios adaptor
    • 5
      Built in user auth/oauth
    • 5
      Firebase hosting
    • 4
      Speed of light
    • 4
      Very easy to use
    • 3
      It's made development super fast
    • 3
      Great
    • 3
      Brilliant for startups
    • 2
      Great all-round functionality
    • 2
      Low battery consumption
    • 2
      I can quickly create static web apps with no backend
    • 2
      The concurrent updates create a great experience
    • 2
      JS Offline and Sync suport
    • 1
      Faster workflow
    • 1
      Large
    • 1
      Serverless
    • 1
      .net
    • 1
      Free SSL
    • 1
      Good Free Limits
    • 1
      Push notification
    • 1
      Easy to use
    • 1
      Easy Reactjs integration
    CONS OF FIREBASE
    • 28
      Can become expensive
    • 15
      Scalability is not infinite
    • 14
      No open source, you depend on external company
    • 9
      Not Flexible Enough
    • 5
      Cant filter queries
    • 3
      Very unstable server
    • 2
      Too many errors
    • 2
      No Relational Data

    related Firebase posts

    Stephen Gheysens
    Senior Solutions Engineer at Twilio | 12 upvotes 路 113K views

    Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

    My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

    See more
    Tassanai Singprom

    This is my stack in Application & Data

    JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

    My Utilities Tools

    Google Analytics Postman Elasticsearch

    My Devops Tools

    Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

    My Business Tools

    Slack

    See more
    Chat by Stream logo

    Chat by Stream

    11
    44
    95
    Chat API & SDK
    11
    44
    + 1
    95
    PROS OF CHAT BY STREAM
    • 15
      Reasonable Pricing
    • 14
      Threads
    • 13
      Very fast and scalable
    • 13
      SDKs for React, RN, Android and iOS are better
    • 13
      Reactions
    • 10
      Front-End Components
    • 9
      Great support
    • 4
      Stability
    • 4
      Performance
    CONS OF CHAT BY STREAM
      Be the first to leave a con

      related Chat by Stream posts

      Twilio logo

      Twilio

      6.9K
      5.1K
      511
      Bring voice and messaging to your web and mobile applications.
      6.9K
      5.1K
      + 1
      511
      PROS OF TWILIO
      • 144
        Powerful, simple, and well documented api
      • 87
        RESTful API
      • 66
        Clear pricing
      • 61
        Great sms services
      • 58
        Low cost of entry
      • 28
        Global SMS Gateway
      • 14
        Good value
      • 12
        Cloud IVR
      • 11
        Extremely simple to integrate with rails
      • 11
        Simple
      • 5
        Great for startups
      • 3
        Great developer program
      • 3
        SMS
      • 3
        Hassle free
      • 1
        New Features constantly rolling out
      • 1
        Many deployment options, from build from scratch to buy
      • 1
        Text me the app pages
      • 1
        Easy integration
      • 1
        Two factor authentication
      • 0
        A
      CONS OF TWILIO
      • 1
        Predictable pricing
      • 1
        Expensive

      related Twilio posts

      Julien DeFrance
      Principal Software Engineer at Tophatter | 3 upvotes 路 473.5K views

      Nexmo vs Twilio ?

      Back in the early days at SmartZip Analytics, that evaluation had - for whatever reason - been made by Product Management. Some developers might have been consulted, but we hadn't made the final call and some key engineering aspects of it were omitted.

      When revamping the platform, I made sure to flip the decision process how it should be. Business provided an input but Engineering lead the way and has the final say on all implementation matters. My engineers and I decided on re-evaluating the criteria and vendor selection. Not only did we need SMS support, but were we not thinking about #VoiceAndSms support as the use cases evolved.

      Also, on an engineering standpoint, SDK mattered. Nexmo didn't have any. Twilio did. No-one would ever want to re-build from scratch integration layers vendors should naturally come up with and provide their customers with.

      Twilio won on all fronts. Including costs and implementation timelines. No-one even noticed the vendor switch.

      Many years later, Twilio demonstrated its position as a leader by holding conferences in the Bay Area, announcing features like Twilio Functions. Even acquired Authy which we also used for 2FA. Twilio's growth has been amazing. Its recent acquisition of SendGrid continues to show it.

      See more
      Socket.IO logo

      Socket.IO

      8K
      6.7K
      769
      Realtime application framework (Node.JS server)
      8K
      6.7K
      + 1
      769
      PROS OF SOCKET.IO
      • 212
        Real-time
      • 141
        Event-based communication
      • 140
        Node.js
      • 102
        Open source
      • 101
        WebSockets
      • 26
        Binary streaming
      • 22
        No internet dependency
      • 9
        Fallback to polling if WebSockets not supported
      • 7
        Large community
      • 5
        Ease of access and setup
      • 4
        Push notification
      CONS OF SOCKET.IO
      • 9
        Bad documentation
      • 4
        Githubs that complement it are mostly deprecated
      • 2
        Doesn't work on React Native
      • 2
        Small community

      related Socket.IO posts

      across_the_grid
      Full-stack web developer at Capmo GmbH | 10 upvotes 路 323.5K views
      Shared insights
      on
      Socket.IO
      Node.js
      ExpressJS

      I use Socket.IO because the application has 2 frontend clients, which need to communicate in real-time. The backend-server handles the communication between these two clients via websockets. Socket.io is very easy to set up in Node.js and ExpressJS.

      In the research project, the 1st client shows panoramic videos in a so called cave system (it is the VR setup of our research lab, which consists of three big screens, which are specially arranged, so the user experience the videos more immersive), the 2nd client controls the videos/locations of the 1st client.

      See more

      We are starting to work on a web-based platform aiming to connect artists (clients) and professional freelancers (service providers). In-app, timeline-based, real-time communication between users (& storing it), file transfers, and push notifications are essential core features. We are considering using Node.js, ExpressJS, React, MongoDB stack with Socket.IO & Apollo, or maybe using Real-Time Database and functionalities of Firebase.

      See more
      Google Cloud Pub/Sub logo

      Google Cloud Pub/Sub

      368
      312
      4
      Global service for real-time and reliable messaging and streaming data
      368
      312
      + 1
      4
      PROS OF GOOGLE CLOUD PUB/SUB
      • 4
        Easy to set-up and start with
      CONS OF GOOGLE CLOUD PUB/SUB
      • 2
        Need integration with stackdriver for monitoring

      related Google Cloud Pub/Sub posts

      Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?

      See more
      NATS logo

      NATS

      212
      326
      50
      Lightweight publish-subscribe & distributed queueing messaging system
      212
      326
      + 1
      50
      PROS OF NATS
      • 20
        Fastest pub-sub system out there
      • 14
        Rock solid
      • 10
        Easy to grasp
      • 3
        Easy, Fast, Secure
      • 2
        Light-weight
      • 1
        Robust Security Model
      CONS OF NATS
      • 1
        Persistence with Jetstream supported
      • 1
        No Order
      • 1
        No Persistence

      related NATS posts