Open Source Linux WebSocket Libraries - Page 2
Sort By:
WebSocket Libraries for Linux
View 1581 business solutions-
$300 Free Credits to Build on Google CloudPut your $300 in credit toward real workloads, then keep building with free monthly usage for 20+ products. No commitment and no charge until you upgrade.
-
Earn up to 16% annual interest with Nexo.Generate interest, borrow against your crypto, and trade a range of cryptocurrencies — all in one platform. Geographic restrictions, eligibility, and terms apply.
-
1
Melody
Minimalist websocket framework for Go
Melody is a minimalist WebSocket framework for Go that wraps the standard WebSocket workflow in a simple, developer-friendly API. It is designed to make real-time server features easier to build without requiring a large framework or complex setup. Developers can use it for chat systems, live notifications, dashboards, multiplayer coordination, collaborative tools, and other bidirectional communication features. Melody provides connection lifecycle hooks, message handlers, broadcasting, session management, and grouped communication patterns. It is built to feel familiar to Go developers and can be integrated into existing HTTP applications. The project is especially useful when a team needs straightforward WebSocket behavior without building connection handling and broadcast logic from scratch. -
2
N2O
Distributed WebSocket Application Server ISO 20922
N2O is an embeddable message protocol loop library for WebSocket, HTTP, MQTT and TCP servers. It provides basic features, such as process management, virtual nodes ring for request processing, sessions, frame encoding, and unified API for external mq and caching services. -
3
NestJS-Websocket
Websocket Client for NestJS based on ws
Websocket Client for NestJS based on ws. -
4
Rockets
REST and websockets C++ library
A library for easy HTTP and websockets messaging in C++ applications. -
Build Data Resilience - Take the Assessment TodayIs your recovery strategy as strong as you think? Take this quick self-assessment to check your recovery readiness and gain tailored insights. In only 2 minutes, you'll learn where you fall on the recovery readiness scale.
-
5
SockJS-client
WebSocket emulation and Javascript client
SockJS is a browser JavaScript library that provides a WebSocket-like object. SockJS gives you a coherent, cross-browser, Javascript API which creates a low latency, full duplex, cross-domain communication channel between the browser and the web server. Under the hood SockJS tries to use native WebSockets first. If that fails it can use a variety of browser-specific transport protocols and presents them through WebSocket-like abstractions. SockJS is intended to work for all modern browsers and in environments which don't support the WebSocket protocol, for example, behind restrictive corporate proxies. SockJS-client does require a server counterpart, such as SockJS-node, which is a SockJS server for Node.js. The API should follow HTML5 Websockets API as closely as possible. All the transports must support cross domain connections out of the box. It's possible and recommended to host a SockJS server on a different server than your main web site. -
6
Sockette
The cutest little WebSocket wrapper
Sockette is a tiny (367 bytes) wrapper around WebSocket that will automatically reconnect if the connection is lost. In addition to attaching additional API methods, Sockette allows you to reuse instances, avoiding the need to redeclare all event listeners. You have direct access to the (current) underlying WebSocket within every EventListener callback. -
7
SuperSocket
Extensible socket server application framework for .NET
SuperSocket is a high-performance, extensible socket server framework for .NET applications. It provides a structured foundation for building custom network communication servers without manually implementing every low-level socket concern. The framework supports multiple protocols, including TCP, UDP, and WebSocket, and gives developers a modular architecture for protocol parsing, session handling, command processing, and server hosting. It is suitable for chat servers, game servers, IoT gateways, telemetry services, industrial systems, and other real-time network applications. SuperSocket is designed to be flexible enough for custom binary or text protocols while still offering reusable abstractions for common server patterns. It is most useful for .NET teams that need robust networking infrastructure with room for domain-specific protocol logic. -
8
Tyrus
Eclipse Tyrus is the open source JSR 356 - Java API for WebSocket
Eclipse Tyrus is the open source JSR 356 - Java API for WebSocket reference implementation for easy development of WebSocket applications.Eclipse Tyrus is also a Jakarta WebSocket 2.0 compatible implementation. WebSocket protocol defined by IETF provides bi-directional communication between the server and the remote host. The pros are mainly the ability to communicate both ways, low latency and small communication overhead. Therefore Tyrus and WebSocket in general are suitable for web applications that require sending a huge volume of relatively small messages like online games or market ticker broadcasting. -
9
Vue-Socket.io
Socket.io implementation for Vuejs and Vuex
Vue-Socket.io is a Socket.IO integration library for Vue.js and Vuex applications. It allows Vue components to listen for real-time socket events through a clean, framework-friendly API. The project helps developers connect frontend applications to Socket.IO servers without manually wiring every event listener and lifecycle behavior. It also supports Vuex integration, making it easier to route socket events into centralized state management. Vue-Socket.io is especially useful for chat apps, dashboards, notifications, collaborative interfaces, live counters, and other real-time user experiences. Because the project is centered on Vue 2-era usage, modern Vue teams should evaluate compatibility before using it in a new application. -
Paessler - Monitor Your Whole Network in MinutesWaiting weeks for a monitoring rollout isn't an option when infrastructure doesn't stop running. PRTG's auto-discovery scans your network and suggests from over 200 pre-configured sensor types, so you're watching servers, applications and devices within minutes, not after a multi-week deployment. Enterprise-strength monitoring, without the enterprise complexity. Start your free trial today.
-
10
WebSocket Kit
WebSocket client library built on SwiftNIO
WebSocket client library built on SwiftNIO. WebSockets allow for two-way communication between a client and server. Unlike HTTP, which has a request and response pattern, WebSocket peers can send an arbitrary number of messages in either direction. Vapor's WebSocket API allows you to create both clients and servers that handle messages asynchronously. -
11
WebSocket RPC
RPC library for .NET with auto JavaScript client code generation
WebSocket RPC library for .NET with auto JavaScript client code generation, supporting ASP.NET Core. -
12
WebSocket Ruby
Universal Ruby library to handle WebSocket protocol
Universal Ruby library to handle WebSocket protocol. It focuses on providing abstraction layer over WebSocket API instead of providing server or client functionality. WebSocket Ruby has no external dependencies, so it can be installed from source or directly from rubygems. -
13
WebSocketListener
A lightweight and scalable asynchronous WebSocket listener
The WebSocketListener class provides simple methods that listen for and accept incoming WebSocket connection requests asynchronously. It is a lightweight listener with an API very similar to the System.Net.TcpListener class. It does not use the Microsoft's System.Net.WebSockets namespace. WebSocketListener has been designed to provide WebSocket connectivity to other applications, in the same way that System.Net.TcpListener provides TCP connectivity. It is not a communication framework on its own and it does not provide any kind of publisher/subscriber pattern or reliable messaging beyond TCP. -
14
WebSockets in C
WebSockets in C for Embedded Applications
WIC is a C99 implementation of rfc6455 websockets designed for embedded applications. WIC decouples the websocket protocol from the transport layer. This makes it possible to use WIC over any transport layer assuming that you are prepared to do the integration work. -
15
Websocketfiles
Provide two well designed and out of box websocket c++ classes
Websocketfiles provides two well designed and out of box websocket c++ classes that you can easily use in your ongoing project which needs to support websocket. The purpose of this project is to let you add websocket support in your c++ project as quickly/efficient as possible.The websocketfiles is designed as simple as possible and no network transport module included. It exports two network interfaces named from_wire/to_wire that can be easily binding with any network modules(Boost.Asio, libuv, libevent and so on). -
16
Wslay WebSocket Library
WebSocket library written in C.
Wslay is a WebSocket library written in C. It implements the protocol version 13 described in RFC 6455. This library offers 2 levels of API: event-based API and frame-based low-level API. For event-based API, it is suitable for non-blocking reactor pattern style. You can set callbacks in various events. For frame-based API, you can send WebSocket frame directly. Wslay only supports data transfer part of WebSocket protocol and does not perform opening handshake in HTTP. Wslay does not perform any I/O operations for its own. Instead, it offers callbacks for them. This makes Wslay independent on any I/O frameworks, SSL, sockets, etc. This makes Wslay protable across various platforms and the application authors can choose freely I/O frameworks. -
17
arduinoWebSockets
arduinoWebSockets
A WebSocket Server and Client for Arduino based on RFC6455. -
18
deno websocket
A simple WebSocket library like ws of node.js library for deno
A simple WebSocket library like ws of node.js library for deno. This library is wrapping the ws standard library as the server side and the native WebSocket API as a client side. You can receive callbacks at the EventEmitter and can use the same object format on both the server side and the client side. -
19
go-socket.io
socket.io library for golang, a realtime application framework
go-socket.io is the library implementation of Socket.IO in Golang, which is a real-time application framework. Current this library supports 1.4 version of the Socket.IO client. It supports room, namespaces and broadcast at now. This project is looking for contributors to help fix bugs and implement new features. -
20
libhv
Network library for developing TCP/UDP/SSL/HTTP/WebSocket/MQTT client
Like libevent, libev, and libuv, libhv provides event loop with non-blocking IO and timer, but simpler api and richer protocols. Cross-platform (Linux, Windows, MacOS, BSD, Solaris, Android, iOS) High-performance EventLoop (IO, timer, idle, custom) TCP/UDP client/server/proxy. TCP supports heartbeat, reconnect, upstream, MultiThread-safe write and close, etc. Built-in common unpacking modes (FixedLength, Delimiter, LengthField) RUDP support: WITH_KCP. SSL/TLS support: (via WITH_OPENSSL or WITH_GNUTLS or WITH_MBEDTLS) HTTP client/server (support https http1/x http2 grpc). HTTP supports static service, indexof service, proxy service, sync/async API handler. HTTP supports RESTful, router, middleware, keep-alive, chunked, SSE, etc. WebSocket client/server. -
21
rxWebSocket
rxWebSocket is a simple reactive extension of OkHttp Websocket
rxWebSocket is a simple reactive extension of OkHttp Websocket interface with support for Convertor Factories and Interceptors. -
22
tokio-tungstenite
Future-based Tungstenite for Tokio
tokio-tungstenite is a Rust library that connects the Tungstenite WebSocket implementation with the Tokio asynchronous runtime. It lets developers build non-blocking WebSocket clients and servers using Tokio’s async networking model. The crate wraps asynchronous TCP streams and upgrades them into WebSocket streams that integrate naturally with Rust futures and async tasks. It is useful for real-time services, streaming applications, chat systems, gateways, backend infrastructure, and any Rust project that needs WebSocket communication without blocking threads. Because it builds on Tungstenite, it inherits a standards-focused WebSocket protocol foundation while adding Tokio compatibility. It is a practical choice for Rust developers who need efficient, event-driven WebSocket networking. -
23
uWebSockets.js
μWebSockets for Node.js back-ends
µWebSockets.js is a web server bypass for Node.js that reimplements eventing, networking, encryption, web protocols, routing and pub/sub in highly optimized C++. As such, µWebSockets.js delivers web serving for Node.js, 8.5x that of Fastify and at least 10x that of Socket.IO. It is also the built-in web server of Bun. -
24
websocket for Go
Minimal and idiomatic WebSocket library for Go
websocket is a minimal and idiomatic WebSocket library for Go. Minimal and idiomatic API. First class context.Context support. Fully passes the WebSocket autobahn-testsuite. Single dependency. JSON and protobuf helpers in the wsjson and wspb subpackages. Zero alloc reads and writes. Concurrent writes. Close handshake. net.Conn wrapper. Ping pong API. RFC 7692 permessage-deflate compression. Compile to Wasm. Transparent message buffer reuse with wsjson and wspb subpackages. Gorilla writes directly to a net.Conn and so duplicates features of net/http.Client. Gorilla requires registering a pong callback before sending a Ping. Compare godoc of nhooyr.io/websocket with gorilla/websocket side by side. Will enable easy HTTP/2 support in the future. -
25
ws
Tiny WebSocket library for Go
Zero-copy upgrade. No intermediate allocations during I/O. Low-level API which allows building your own logic of packet handling and buffers reuse. High-level wrappers and helpers around API in wsutil package, which allow to start fast without digging the protocol internals. Existing WebSocket implementations do not allow users to reuse I/O buffers between connections in clear way. This library aims to export efficient low-level interface for working with the protocol without forcing only one way it could be used. Library is tagged as v1* so its API must not be broken during some improvements or refactoring. Example applications using ws are developed in separate repository ws-examples. We can apply the same pattern to read and write structured responses through a JSON encoder and decoder.Zero-copy upgrade helps to avoid unnecessary allocations and copying while handling HTTP Upgrade request.
