Skip to main content
Markdown

Why WordPlus Cloud

Laravel, Django, FastAPI, Express and Flask can run websockets of their own, on your servers. WordPlus Cloud runs them for you, and adds what a websocket alone does not do:

  • No websocket servers to keep. Your own has to hold every connection, grow past one machine and stay up through your deploys. The WordPlus Cloud servers hold them, more of them start as your app grows, and a page moves from one to another without a drop.
  • Any host for your server. Your server only signs and sends, so it runs anywhere, serverless and edge functions included, which cannot hold a connection open themselves.
  • Nothing lost on a reconnect. A room keeps its last events, and a page that comes back gets what it missed, in order, before what comes next.
  • Who is online across your app, presence in every room, and live counts of who is looking.
  • Calls, not only messages. Calls between two people and group calls need relays and media servers besides a socket. WordPlus Cloud runs both, its media servers in several regions.
  • Sealed end to end. What your app sends travels encrypted with keys only your server and your users hold.
  • Parts ready to use, all optional. The Better Messages call screen, chat and list of who is online, as React components or elements for any page, and agent skills that teach AI coding agents the SDK.
  • In the style of your framework. In Laravel it is a broadcasting driver, so broadcast() and routes/channels.php stay as they are. In Next.js, a route handler and a provider. In Django, FastAPI, Express and Flask, a router and a few rules.

Start with the guide for your framework: Next.js, Laravel, Django, FastAPI, Express, PHP or Flask, or any other stack.