Real-time transports
View →- WebSocket · RFC 6455
- HTTP/2
- HTTP/3 · QUIC
- SSE
- WebRTC
RFC 6455 compliant client and server, 10,000+ concurrent connections, TLS 1.3, IOCP on Windows and EPOLL on Linux. WebSocket, HTTP/2, MQTT, AMQP, STOMP, WAMP, SSE, WebRTC and AI for Delphi 7 to RAD Studio 13, C++Builder, Lazarus and .NET 2.0 to .NET 10, with one API across every target.
Standard, Professional and Enterprise editions →Narrated and captioned tours of the library and of the packages built from it. Pick one from the list. Nothing downloads until you press play.
Real-time components for Delphi, C++Builder and .NET: WebSocket, MQTT, HTTP/2 and HTTP/3, WebRTC and AI, in one library.
sgcWebSockets in two minutesReal-time components for Delphi, C++Builder and .NET: WebSocket, MQTT, HTTP/2 and HTTP/3, WebRTC and AI, in one library.
Messaging: MQTT, AMQP, STOMP, KafkaThe broker clients of sgcWebSockets, packaged as sgcMQ: MQTT 3.1.1 and 5.0, AMQP 0.9.1 and 1.0, Apache Kafka and STOMP.
HTTP server, HTTP/2 and gRPCHTTP server, HTTP/2 client, gRPC client and Google Cloud Pub/Sub, Calendar and FCM clients, packaged as sgcHTTP.
HTTP/3 over QUICRaw QUIC transport and an HTTP/3 client and server, with WebTransport. An add-on to sgcWebSockets Enterprise.
WebRTC audio, video and dataPeer-to-peer media and data channels, with STUN, TURN and ICE and a signalling server you host yourself.
AI agents and MCPSeven LLM providers behind one component, plus the Model Context Protocol client and server.
REST and OpenAPI serversPublish REST APIs from an OpenAPI 3.x contract, or consume any OpenAPI-described API.
OAuth2, JWT and passkeysSign in with any OAuth2/OIDC provider, issue and verify JWTs, and add WebAuthn passkeys to native apps.
WhatsApp and TelegramWhatsApp Business Cloud API and Telegram TDLib clients, packaged as sgcSocial.
Native client and server implementations, not thin wrappers over a browser engine. Mix protocols inside a single application and share one connection pool, with ready-made clients for the brokers, hubs and services your infrastructure team already runs.
The same pub/sub task written with the same component names in Delphi, C++Builder and C#. Learn the API once, reuse it on every target you ship to.
uses
sgcWebSocket, sgcWebSocket_Classes,
sgcWebSocket_Protocol_sgc_Client;
procedure TForm1.FormCreate(Sender: TObject);
begin
FClient := TsgcWebSocketClient.Create(Self);
FClient.Host := 'www.esegece.com';
FClient.Port := 2053;
FClient.TLS := True;
FClient.OnConnect := ClientConnect;
FProtocol := TsgcWSPClient_sgc.Create(Self);
FProtocol.Client := FClient;
FProtocol.OnMessage := ProtocolMessage;
FClient.Active := True;
end;
procedure TForm1.ClientConnect(Connection: TsgcWSConnection);
begin
FProtocol.Subscribe('orders');
FProtocol.Broadcast('{"id":42,"status":"filled"}', 'orders');
end;
procedure TForm1.ProtocolMessage(Connection: TsgcWSConnection;
const Text: string);
begin
Memo1.Lines.Add(Text);
end;
// uses: sgcWebSocket, sgcWebSocket_Classes,
// sgcWebSocket_Protocol_sgc_Client
FClient = new TsgcWebSocketClient(this);
FClient->Host = "www.esegece.com";
FClient->Port = 2053;
FClient->TLS = true;
FClient->OnConnect = ClientConnect;
FProtocol = new TsgcWSPClient_sgc(this);
FProtocol->Client = FClient;
FProtocol->OnMessage = ProtocolMessage;
FClient->Active = true;
void __fastcall TForm1::ClientConnect(TsgcWSConnection *Connection)
{
FProtocol->Subscribe("orders");
FProtocol->Broadcast("{\"id\":42,\"status\":\"filled\"}", "orders");
}
void __fastcall TForm1::ProtocolMessage(TsgcWSConnection *Connection,
const UnicodeString Text)
{
Memo1->Lines->Add(Text);
}
using esegece.sgcWebSockets;
var client = new TsgcWebSocketClient();
client.Host = "www.esegece.com";
client.Port = 2053;
client.TLS = true;
var protocol = new TsgcWSPClient_sgc();
protocol.Client = client;
protocol.OnMessage += (conn, text) => Console.WriteLine(text);
client.OnConnect += (conn) =>
{
protocol.Subscribe("orders");
protocol.Broadcast("{\"id\":42,\"status\":\"filled\"}", "orders");
};
client.Active = true;
TsgcWebSocketServer with a port, an OnMessage handler and Active := True is a running echo server. Connection.WriteData answers the client that spoke.TsgcWebSocketClient with TLS on, plus the sgc protocol component, subscribes to a named channel the moment it connects.TsgcWebSocketServer.Broadcast(Text, 'orders') fans the same payload to every subscriber of the channel.Every one of these ships on top of the same client and server components you install in your IDE today.
Persistent connections, presence, named channels and binary messaging, with a multithreaded server built for thousands of concurrent users.
Real-time communication →Ready-made streaming clients for 14 crypto exchanges, with TLS, binary frames and automatic reconnection on the market-data feed.
Exchange APIs →MQTT 3.1.1 and 5.0 with QoS 0/1/2 and shared subscriptions, plus turnkey clients for AWS IoT Core and Azure IoT Hub.
IoT components →Peer-to-peer media and data channels with built-in STUN, TURN and ICE, and a signalling server you host yourself.
WebRTC and P2P →Expose your own tools, prompts and resources to ChatGPT and Claude through the Model Context Protocol, client and server both included.
MCP components →Serve HTTPS, WebSocket and HTTP/2 from the same port, with multiplexing, header compression and server push, and HTTP/3 over QUIC.
HTTP components →Long-lived connections, encrypted by default, self-healing under churn. The parts that decide whether your server survives Monday morning.
The server accepts connections on I/O completion ports under Windows and on epoll under Linux, dispatching work across a thread pool instead of one thread per socket. That is what keeps 10,000+ live connections on a single server process.
Scaling components →Pick the TLS backend that fits deployment. OpenSSL 3 gives you the same behaviour on Windows, Linux, macOS, iOS and Android. Native SChannel uses the Windows certificate store, so there are no OpenSSL DLLs to ship.
TLS and certificates →HeartBeat sends periodic ping frames so dead peers are detected instead of lingering. WatchDog reconnects a dropped client automatically with configurable intervals and attempts, so a network blip does not become an outage.
Client component →Turn on the permessage-deflate extension and repetitive JSON payloads shrink on the wire, negotiated during the handshake with any compliant peer. Binary frames, fragmentation and Unicode validation are all handled for you.
Feature overview →Each edition includes everything in the one before it, with full Delphi and C++ Builder source code and one year of updates. The All-Access bundle covers the whole eSeGeCe suite.
All client components: WebSocket clients, MQTT, AMQP, STOMP and WAMP clients, 20+ exchange and messaging API clients, AWS IoT and Azure IoT clients, OAuth2 and JWT clients.
Standard plus every server: WebSocket and WebSocket + HTTP servers, Firewall, LoadBalancer and Proxy servers, WebRTC server, Dataset, Files and Presence servers, DataSnap WebBrokerBridge.
Professional plus the native HTTP/2 client, HTTP.SYS, IOCP and EPOLL high-performance servers, all AI components with MCP, OAuth2, JWT and WebAuthn servers, TURN, ICE and RTCPeerConnection, TLS 1.3, ALPN and DTLS.
For .NET there are Community, Professional and Enterprise editions, from .NET Framework 2.0 to .NET 10.
Compare editions and pricesExtend sgcWebSockets Enterprise with a dedicated transport or media engine.
Buy only the part of sgcWebSockets you need. Most single packages are standalone and bundle the sgcWebSockets Core runtime, with full source code.
Trusted by Delphi, C++ Builder, Lazarus and .NET developers building real-time applications around the world.
sgcWebSockets is amazing and your support is the best!
Your sgcWebSockets library is very useful and easy to setup. Keep up the good work!
Thanks so much for your help and support. I love your components.
Download the trial and run a WebSocket server on your own machine in minutes. Full source, royalty-free deployment, Delphi 7 to RAD Studio 13 and .NET 2.0 to .NET 10.
sgcWebSockets is the flagship. The rest of the suite covers the signatures, the SDKs, PDF, biometrics and the sockets underneath.
Document signatures (XAdES, PAdES, CAdES, ASiC) and code signing (Authenticode, ClickOnce, NuGet, VSIX), with 10 key providers and 21 EU country profiles.
OpenAPI 3.x parser, Pascal SDK generator and OpenAPI server, plus 1,195+ pre-built SDKs for AWS, Azure, Google Cloud and Microsoft Graph.
Create, edit, view, sign, redact and validate PDF files in pure Object Pascal, with no DLL to deploy. Licensed on its own.
Windows Hello, fingerprint sensors and facial recognition for Delphi and C++Builder, built on the Windows Biometric Framework.
An enhanced Indy TCP/IP suite with modern TLS, IPv6 and extended protocol support for Delphi 7 through RAD Studio 13.