Both products give a Delphi developer WebSocket client and server components, and both go well beyond WebSocket. Outside the part that overlaps they cover different ground. This page sets out what each one does, protocol by protocol and platform by platform, and every claim is taken from the vendor's own published material and linked in the Sources section.
IPWorks is a family of separately licensed toolkits, not a single product. Attributing a feature from one toolkit to another would make this page useless, so the products in scope are named here and named again in every row that depends on them.
eSeGeCe · Commercial, source code included
One Delphi and C++ Builder suite covering WebSocket client and server, HTTP and HTTP/2, MQTT, AMQP, STOMP, WAMP, Kafka, WebRTC, LLM and MCP clients, and third-party API integrations. Sold in Standard, Professional and Enterprise editions, with optional add-on packs. Version verified from sgcBase_Const.pas in the shipping source tree.
/n software · Commercial
The core toolkit, build 24.0.9716, released 7 August 2026. Its published component reference documents 46 components, including WSClient and WSServer for WebSocket, plus HTTP, REST, GRPC, OAuth, JSON, XML, SOAP, FTP, SMTP, IMAP, POP, LDAP, DNS, XMPP, WebDAV, CalDAV and more. A 2026 version is published as a beta.
/n software · Commercial, sold separately
The messaging toolkit. Its published component reference documents AMQP, AMQPClassic, AmazonSNS, AmazonSQS, AzureRelayProxy, AzureRelayReceiver, AzureRelaySender, CertMgr, JSON, MQTT, STOMP and XMPP. Where this page compares MQTT, AMQP or STOMP, this is the toolkit it means.
/n software · Commercial, sold separately
The IoT toolkit. Its published component reference documents AMQP, AMQPClassic, CertMgr, CoAP, JSON, MQTT, MQTTBroker, MQTTSN, STOMP and XMPP. It is the toolkit that carries the embedded MQTT broker and the CoAP component.
/n software · Commercial, sold separately
/n software describes it as “a set of components for bi-directional communication between LLMs and your custom code, data, and context”, covering the Model Context Protocol over standard input and output or over HTTP, with tools, resources, prompts and sampling. It is the toolkit referenced in the MCP row of the matrix.
Named so you know what was left out
/n software also publishes IPWorks SSH, SSL, SFTP, VoIP, IPC, NFS, Encrypt, S/MIME, OpenPGP, Auth, Zip, SNMP, BLE, NFC, EDI, the Cloud toolkits, Secure PDF, PDF SDK, 3-D Secure, SecureBlackbox and enterprise adapters. None of them is used to support a claim here. Where a capability lives in one of those toolkits rather than the four above, the matrix says so in the row.
All /n software facts on this page were read from nsoftware.com and cdn.nsoftware.com on 6 September 2026, against IPWorks 2024 Delphi Edition, build 24.0.9716. All sgcWebSockets facts were read from the 2026.9.0 source tree on the same date. Both products ship often. If you are reading this months later, follow the links and check.
A check () means the vendor's own component reference documents it. A dash (—) means it does not appear in the published component reference of the products named in the Scope section above, which is not the same as saying it cannot be done. A tilde (~) means it is documented but with a stated limit, and the row text says which.
| Feature | sgcWebSockets 2026.9.0 | IPWorks 2024 Delphi Edition |
|---|---|---|
WebSocket client
TsgcWebSocketClient against TipwWSClient, both over ws and wss
|
||
WebSocket server
TsgcWebSocketServer against TipwWSServer. IPWorks documents a default ceiling of 1,000 simultaneous connections, raised through the MaxConnections setting to at most 100,000
|
||
HTTP server on the same port
Serving pages, files or REST routes from the process that also terminates the WebSocket. sgcWebSockets provides TsgcWebSocketHTTPServer with DocumentRoot, sessions and OnCommandGet. IPWorks documents WSServer as a WebSocket server, and its 2024 component reference lists no HTTP server component
|
— | |
per-message-deflate, RFC 7692
sgcWebSockets exposes Extensions.PerMessage_Deflate with window bits, context takeover and memory level. IPWorks exposes CompressionMethod on the client and the EnablePermessageDeflate setting, on by default, on the server
|
||
Subprotocol negotiation
IPWorks takes a comma-separated SubProtocols list on the client and hands the server the requested list in WebSocketOpenRequest. sgcWebSockets negotiates through its protocol components, which carry a read-only Protocol name
|
||
Ping and pong keepalive
sgcWebSockets uses the HeartBeat option set. IPWorks documents a Ping method and a Ping event on both components
|
||
Outgoing message fragmentation
IPWorks fragments at MaxFrameSize, default 131072 bytes, and flags completeness with the EOM parameter of DataIn. sgcWebSockets streams through the aStreaming argument of WriteData and raises OnFragmented
|
||
Client auto-reconnect
sgcWebSockets ships a WatchDog with Interval, Attempts, fixed or exponential Backoff, MaxInterval and Jitter. The IPWorks WSClient reference lists no reconnect property, method, event or setting, so reconnection is application code
|
— | |
TLS 1.3
IPWorks selects between the platform and an internal TLS stack through SSLProvider, and documents TLS 1.3 groups and signature algorithms. sgcWebSockets selects between OpenSSL, SChannel, Android TLS and Apple TLS through TLSOptions.IOHandler, with TLSOptions.Version up to tls1_3
|
| Feature | sgcWebSockets 2026.9.0 | IPWorks MQ / IPWorks IoT 2024 |
|---|---|---|
MQTT 3.1.1 and 5.0 client
sgcWebSockets: TsgcWSPClient_MQTT, MQTTVersion of mqtt311 or mqtt5. /n software states IPWorks MQ is “fully compliant with MQTT version 3.1.1 and 5.0”
|
||
Embedded MQTT broker
IPWorks IoT ships MQTTBroker, documented as a “lightweight, fully-featured MQTT broker implementation with support for version 3.1.1”, listening over plaintext TCP, TLS, WebSocket and secure WebSocket. sgcWebSockets has no MQTT broker component. Its MQTT support is client side
|
— | |
MQTT-SN
IPWorks IoT documents an MQTTSN component. There is no MQTT-SN unit in the sgcWebSockets source tree
|
— | |
CoAP
IPWorks IoT documents a CoAP component. There is no CoAP unit in the sgcWebSockets source tree
|
— | |
AMQP 1.0 and 0.9.1 client
sgcWebSockets: TsgcWSPClient_AMQP1 for 1.0 and TsgcWSPClient_AMQP for 0.9.1. /n software states “AMQP 1.0 and 0.9.1 fully supported” and ships AMQP plus AMQPClassic
|
||
STOMP client
sgcWebSockets ships TsgcWSPClient_STOMP plus RabbitMQ and ActiveMQ variants. /n software states STOMP versions 1.1 and 1.2 for IPWorks MQ
|
||
WAMP client and server
sgcWebSockets ships TsgcWSPClient_WAMP, TsgcWSPClient_WAMP2 and TsgcWSPServer_WAMP. WAMP does not appear in the IPWorks MQ or IPWorks IoT component reference
|
— | |
Kafka client
sgcWebSockets ships TsgcWSPClient_Kafka. Kafka does not appear in the IPWorks MQ or IPWorks IoT component reference
|
— | |
Azure Relay
IPWorks MQ documents AzureRelaySender, AzureRelayReceiver and AzureRelayProxy. sgcWebSockets has no Azure Relay component
|
— | |
Amazon SQS and SNS
IPWorks MQ documents both AmazonSQS and AmazonSNS. sgcWebSockets registers TsgcHTTPAWS_SQS_Client for SQS and has no SNS component
|
~ | |
Managed cloud IoT brokers
sgcWebSockets registers TsgcIoTAmazon_MQTT_Client and TsgcIoTAzure_MQTT_Client, preconfigured for AWS IoT Core and Azure IoT Hub. IPWorks IoT provides the generic MQTT component to reach the same brokers
|
~ |
| Feature | sgcWebSockets 2026.9.0 | IPWorks 2024 Delphi Edition |
|---|---|---|
HTTP/1.1 client
Both ship one. IPWorks documents the HTTP component with cookies, redirects, proxy, ranges and streams
|
||
HTTP/2 client
IPWorks accepts HTTPVersion of “2.0” and falls back to HTTP/1.1 when the server does not offer it. sgcWebSockets ships TsgcHTTP2Client, gated on the SGC_HTTP2 define
|
||
HTTP/2 server
The sgcWebSockets HTTP server exposes HTTP2Options with settings, an alternate service advertisement and a thread pool. No HTTP server component appears in the IPWorks 2024 component reference
|
— | |
HTTP/3 and QUIC
/n software documents HTTPVersion of “3.0” and states plainly that “HTTP/3 is supported only in .NET and Java”, so it is not available to the Delphi Edition. sgcWebSockets ships TsgcHTTP3Client, TsgcHTTP3Server, TsgcQUICClient and TsgcQUICServer in the sgcQUIC add-on pack
|
— | |
gRPC client
IPWorks 2024 documents a GRPC component. sgcWebSockets registers TsgcGRPCClient, gated on the SGC_GRPC define
|
||
Server-Sent Events
The sgcWebSockets server carries an SSE fallback, FallBack.ServerSentEvents, for clients that cannot upgrade. SSE does not appear in the IPWorks 2024 component reference
|
— | |
Model Context Protocol
sgcWebSockets registers TsgcWSAPIClient_MCP and TsgcWSAPIServer_MCP. /n software covers MCP in a separate product, MCP SDK 2026 Delphi Edition, over standard input and output or over HTTP
|
||
| LLM chat clients sgcWebSockets ships dedicated clients for OpenAI, Anthropic, Gemini, DeepSeek, Grok, Mistral and Ollama, one unit each. No LLM chat client appears in the /n software product catalogue; its AI Integration category contains MCP SDK | — | |
WebRTC, STUN, TURN and ICE
sgcWebSockets registers TsgcSTUNClient, TsgcSTUNServer, TsgcTURNClient, TsgcTURNServer, TsgcICEClient and TsgcRTCPeerConnection. None of these appears in the IPWorks 2024 component reference
|
— |
| Item | sgcWebSockets 2026.9.0 | IPWorks 2024 Delphi Edition |
|---|---|---|
| Delphi versions Vendor statements | Delphi 7 to Delphi 13 | Delphi 6 to RAD Studio 13 |
| C++ Builder sgcWebSockets ships C++ Builder packages from C2007 to C13. /n software sells a separate C++ Builder Edition of IPWorks with native VCLs | ||
Lazarus and Free Pascal
sgcWebSockets ships sgcWebSocketsLazarus.lpk and an FPC branch in sgcVer.inc. /n software states “Support for Lazarus IDE and Free Pascal” on its Delphi platform page
|
||
| Desktop and server targets The IPWorks Delphi Edition documents Windows 32-bit, Windows 64-bit, Linux 64-bit, macOS 64-bit and macOS ARM 64-bit | ||
iOS and Android from Delphi
sgcWebSockets carries IOS and ANDROID branches throughout sgcVer.inc, including a JNI TLS handler for Android and a Network.framework handler for Apple. The IPWorks Delphi Edition platform list stops at Windows, Linux and macOS. /n software addresses mobile through its separate Java, macOS, Android and iOS editions
|
— | |
Runtime files to deploy
/n software states that on Windows “no additional files are required when deploying (no .dll dependency)”, and that on Linux libipworks.so.24.0 and on macOS libipworks.24.0.dylib must be deployed next to the executable. sgcWebSockets compiles from Pascal source into the executable on every target, so nothing of its own is deployed alongside
|
~ | |
| Same API in other languages The IPWorks download page lists ten editions: .NET, Java, C++, macOS, JavaScript, Delphi, C++ Builder, PHP, Python and ActiveX/ASP/COM. The /n software platform menu additionally lists Node.js, Go, Rust, Android, iOS, Swift and BizTalk. sgcWebSockets is published for Delphi and C++ Builder, and as a separate C# port | ~ |
Every matrix row above that is not a check in both columns, restated with the evidence behind it. Grouped by topic rather than by product, because most projects care about two or three of these and nothing else.
IPWorks IoT ships MQTTBroker, documented by /n software as “a lightweight, fully-featured MQTT broker implementation with support for version 3.1.1”, listening over plaintext TCP, TLS, WebSocket and secure WebSocket, with events for session requests, subscriptions and publishes. The same toolkit ships MQTTSN and CoAP. sgcWebSockets has none of the three: no MQTT broker component, and no MQTT-SN or CoAP unit anywhere in its source tree. Its MQTT support is a client, TsgcWSPClient_MQTT, speaking MQTT 3.1.1 or 5.0.
IPWorks MQ documents AzureRelaySender, AzureRelayReceiver and AzureRelayProxy, and both AmazonSQS and AmazonSNS. XMPP appears in the component reference of IPWorks, IPWorks MQ and IPWorks IoT alike. sgcWebSockets registers TsgcHTTPAWS_SQS_Client for Amazon SQS, and has no component for Azure Relay, Amazon SNS or XMPP.
sgcWebSockets registers TsgcWSPClient_WAMP, TsgcWSPClient_WAMP2 and TsgcWSPServer_WAMP for WAMP, TsgcWSPClient_Kafka for Kafka, and TsgcIoTAmazon_MQTT_Client and TsgcIoTAzure_MQTT_Client preconfigured for AWS IoT Core and Azure IoT Hub. Neither WAMP nor Kafka appears in the IPWorks MQ or IPWorks IoT component reference. Both products reach a managed cloud broker through a generic MQTT component as well.
IPWorks 2024 documents 46 components in a single toolkit, taking in FTP, SMTP, IMAP, POP, LDAP, DNS, SOAP, OData, WebDAV, CalDAV, SMPP, Telnet, TFTP and SysLog alongside the WebSocket pair. The wider /n software catalogue adds separate toolkits for SSH and SFTP, SNMP, EDI including AS2Sender and AS2Receiver, S/MIME, OpenPGP, VoIP, Bluetooth LE and NFC. sgcWebSockets covers none of that ground. Outside WebSocket its surface is HTTP, HTTP/2, gRPC, the messaging protocols, the cloud and exchange API clients, and the P2P stack.
sgcWebSockets provides TsgcWebSocketHTTPServer, which terminates HTTP and WebSocket on the same binding, serves a DocumentRoot, keeps sessions, does HTTP compression, exposes OnCommandGet for routes and carries an HTTP2Options block. Around it sit a firewall, a rate limiter, a circuit breaker, an API key manager, a proxy and a load balancer, each registered as its own component. /n software documents WSServer as a component “used to create a WebSocket server”, and the IPWorks 2024 component reference lists no HTTP server component, so HTTP is served from elsewhere in the stack.
sgcWebSockets exposes a WatchDog on the client with Enabled, Interval, Attempts, Backoff of wdbFixed or wdbExponential, BackoffMultiplier, MaxInterval and Jitter. The published property, method, event and configuration lists for the IPWorks WSClient contain no reconnect facility, so a reconnect loop is application code. Both components raise a disconnect event to drive one from.
The IPWorks download page lists ten editions of the same toolkit: .NET, Java, C++, macOS, JavaScript, Delphi, C++ Builder, PHP, Python and ActiveX/ASP/COM, and the /n software platform menu additionally lists Node.js, Go, Rust, Android, iOS, Swift and BizTalk. /n software describes the result as “common component interfaces across platforms and technologies”. sgcWebSockets is published for Delphi and C++ Builder, with a separate C# port that mirrors the same Tsgc class names.
/n software states support for “all Delphi versions between Delphi 6 and RAD Studio 13”, for “Windows, Linux, and macOS”, and for “Lazarus IDE and Free Pascal”. Its Delphi Edition documentation names five targets, Windows 32-bit, Windows 64-bit, Linux 64-bit, macOS 64-bit and macOS ARM 64-bit, with libipworks.so.24.0 or libipworks.24.0.dylib deployed next to the executable on Linux and macOS, and no DLL dependency on Windows. sgcWebSockets ships runtime packages from Delphi 7 to Delphi 13, C++ Builder packages from C2007 to C13 and a Lazarus package, and carries IOS and ANDROID branches through sgcVer.inc including a JNI-backed TLS handler on Android and a Network.framework handler on Apple platforms. It compiles from Pascal source into the executable on every target.
Both have a Delphi HTTP/2 client: IPWorks through an HTTPVersion of “2.0” with automatic fallback to HTTP/1.1, sgcWebSockets through TsgcHTTP2Client. Above that they part. The sgcWebSockets HTTP server exposes an HTTP2Options block, and the sgcQUIC pack adds TsgcQUICClient, TsgcQUICServer, TsgcHTTP3Client and TsgcHTTP3Server. /n software documents an HTTPVersion of “3.0” and states that “HTTP/3 is supported only in .NET and Java”, so the Delphi Edition does not carry it.
Both cover the Model Context Protocol: sgcWebSockets through TsgcWSAPIClient_MCP and TsgcWSAPIServer_MCP, /n software through the separate MCP SDK 2026 Delphi Edition, over standard input and output or over HTTP. Beyond MCP, sgcWebSockets ships chat clients for OpenAI, Anthropic, Gemini, DeepSeek, Grok, Mistral and Ollama, and a WebRTC stack of TsgcSTUNClient, TsgcSTUNServer, TsgcTURNClient, TsgcTURNServer, TsgcICEClient and TsgcRTCPeerConnection. The published /n software catalogue lists no LLM chat client and no WebRTC components.
The sgcWebSockets source code editions include the full Delphi and C++ Builder source, and that source is what the project compiles; the Basic editions ship precompiled DCU files instead. The published /n software purchase options for the IPWorks Delphi Edition list a single licence line with no source option, and its end user licence agreement states that you agree “not to adapt, translate, reverse engineer, decompile or otherwise derive the source code for the Software”. /n software Premium Support does include what it calls “limited source code analysis related to the components”.
Connect to a secure WebSocket endpoint, ask for compression, and print what arrives. The sgcWebSockets listing uses classes, properties and events read from the shipping source tree. The IPWorks listing uses only names and signatures printed in the IPWorks 2024 Delphi Edition reference, and is written here rather than copied from a /n software sample.
uses
sgcWebSocket, sgcWebSocket_Classes, sgcWebSocket_Types, sgcTCP_Classes;
var
WSClient: TsgcWebSocketClient;
begin
WSClient := TsgcWebSocketClient.Create(nil);
WSClient.URL := 'wss://stream.example.com/feed';
// TLS backend and floor
WSClient.TLSOptions.IOHandler := iohOpenSSL;
WSClient.TLSOptions.Version := tls1_3;
// RFC 7692 compression
WSClient.Extensions.PerMessage_Deflate.Enabled := True;
// Reconnect with exponential backoff and jitter
WSClient.WatchDog.Enabled := True;
WSClient.WatchDog.Interval := 5;
WSClient.WatchDog.Attempts := 0; // keep trying
WSClient.WatchDog.Backoff := wdbExponential;
WSClient.WatchDog.BackoffMultiplier := 2;
WSClient.WatchDog.MaxInterval := 60;
WSClient.OnConnect := WSConnect;
WSClient.OnMessage := WSMessage;
WSClient.Active := True;
end;
procedure TForm1.WSConnect(Connection: TsgcWSConnection);
begin
Connection.WriteData('{"op":"subscribe","channel":"ticker"}');
end;
procedure TForm1.WSMessage(Connection: TsgcWSConnection;
const Text: string);
begin
Memo1.Lines.Add(Text);
end;// The component is dropped from the IPWorks 2024 palette tab, or the unit is
// added to the uses clause as described on the Supported Platforms page.
begin
ipwWSClient1.URL := 'wss://stream.example.com/feed';
// TLS stack selection. Automatic is the documented default.
ipwWSClient1.SSLProvider := sslpAutomatic;
// RFC 7692 compression, off by default
ipwWSClient1.CompressionMethod := cmtdDeflate;
// Comma-separated, in order of preference; read back after connect
// to learn which one the server chose
ipwWSClient1.SubProtocols := 'ticker';
ipwWSClient1.Connect;
ipwWSClient1.SendText('{"op":"subscribe","channel":"ticker"}');
end;
procedure TForm1.ipwWSClient1DataIn(Sender: TObject; DataFormat: Integer;
const Text: String; const TextB: TBytes;
EOM: Boolean; EOL: Boolean);
begin
Memo1.Lines.Add(Text);
end;Two differences are worth naming rather than scoring. IPWorks delivers every message through one DataIn event with an EOM flag, so partial messages are visible to you unless you set BufferMessage, while sgcWebSockets raises OnMessage for text, OnBinary for binary and OnFragmented for partials. And /n software notes that its server components expect DoEvents to be called in a loop after the server starts, which shapes how a console or service host is written.
Prices move. These were the published figures on 6 September 2026, and both vendors publish them openly, so check before you budget.
| sgcWebSockets | IPWorks 2024 Delphi Edition | |
|---|---|---|
| Licence unit | Per developer, with Single, Team of two and Site options, in Standard, Professional and Enterprise editions. | Per developer. The Delphi Edition is listed as “Single Developer Subscription, Royalty-Free Distribution, Free Upgrades for One Year, License is Perpetual” at $999. |
| Multi-platform bundle | The Delphi and .NET products are licensed separately. | The Red Carpet Subscription covers all editions and platforms for one developer, at $1,999, or $2,499 with premium support. A four-developer team licence is $5,999, or $7,999 with premium support. Site and enterprise licensing is by quote. The term is twelve months. |
| Buying only what you need | Editions are tiered, and several capabilities ship as separate add-on packs. | /n software states “our products are offered as part of a toolkit and are not available for sale individually”. WebSocket, MQTT and CoAP therefore sit in three different toolkits. |
| Source code | Source code editions include the full Delphi and C++ Builder source, and that source is what your project compiles. Basic editions ship precompiled DCU files. | The published Delphi Edition purchase options list a single licence line with no source option. The end user licence agreement states that you agree “not to adapt, translate, reverse engineer, decompile or otherwise derive the source code for the Software”. |
| Redistribution | Paid licences include royalty-free binary redistribution. | Royalty-free where the order form says so: applications may be distributed “without owing additional fees” provided they contain no modifications, are in compiled executable form, and do not provide substantially the same functionality as the Software. |
| Support | Email support with the licence, and optional support plans quoting a four, three or two hour response target on weekdays depending on edition. | “Free email support is available to all users. Questions are answered on a first-come-first-serve basis.” Premium Support is a paid add-on for Red Carpet Subscription customers, guaranteeing a response “within one business day”, and including unpublished samples and “limited source code analysis related to the components”. |
| Trial | Free Trial edition, downloadable without an order. | Fully functional trial versions, licensed for thirty days from first use. |
Taken from the compiler defines in sgcVer.inc, which is what actually gets compiled, rather than from a marketing table.
| Edition | Feature defines enabled | What that means here |
|---|---|---|
| Standard | SGC_WS_CLIENT, SGC_PROTOCOLS, SGC_MQTT, SGC_AMQP, SGC_AMQP1, SGC_STOMP, SGC_WAMP, SGC_KAFKA, SGC_IOT, SGC_APIS, SGC_OAUTH, SGC_JWT |
Everything on the client side, including all of the messaging protocols compared above. It corresponds to the client side of an IPWorks plus IPWorks MQ project. |
| Professional | SGC_WEBSOCKET_SERVER, SGC_REST_SERVER, SGC_FIREWALL, SGC_RATELIMITER, SGC_CIRCUITBREAKER, SGC_APIKEYMANAGER, SGC_SCHANNEL |
The WebSocket and HTTP servers and the edge components. SGC_WEBSOCKET_SERVER sits inside the SGC_EDT_PRO block, so any server side comparison starts here. |
| Enterprise | SGC_HTTP2, SGC_GRPC, SGC_HTTPAPI, SGC_INDY_IOCP, SGC_INDY_EPOLL, SGC_OPENAI, SGC_ANTHROPIC, SGC_GEMINI, SGC_DEEPSEEK, SGC_GROK, SGC_MISTRAL, SGC_OLLAMA, SGC_AI_MCP, SGC_ICE, SGC_DTLS, SGC_TURN, SGC_RTCPEERCONNECTION, SGC_OAUTH_SERVER, SGC_JWT_SERVER, SGC_WEBAUTHN |
HTTP/2, gRPC, the http.sys and IOCP or epoll high-performance servers, the LLM and MCP components, and the WebRTC stack. |
| sgcQUIC pack | SGC_QUIC, SGC_HTTP3, SGC_WEBTRANSPORT |
QUIC, HTTP/3 and WebTransport arrive through the SGC_PACK_QUIC block rather than through the three editions above. |
Short answers, each traceable to the sources listed below.
WSClient and WSServer ship in the core IPWorks toolkit. MQTT, AMQP and STOMP ship in IPWorks MQ. CoAP, MQTT-SN and the MQTT broker ship in IPWorks IoT. MCP ships in MCP SDK. /n software also states that its products are sold as toolkits and not as individual components, so a project needing WebSocket and MQTT and CoAP needs three toolkits. The Red Carpet Subscription bundles the whole catalogue for one developer.
WSServer as a component “used to create a WebSocket server”, with a WebSocket open request event, per-connection identifiers and TLS. The IPWorks 2024 component reference does not list an HTTP server component, so pages, static files and REST routes would come from something else in your stack. sgcWebSockets provides TsgcWebSocketHTTPServer, which handles both on one port, with a DocumentRoot, sessions, HTTP compression and an HTTP2Options block.
WSServer instance handles up to 1,000 simultaneous connections by default, and the MaxConnections setting raises that to at most 100,000. sgcWebSockets publishes no equivalent ceiling. It exposes a MaxConnections property, a thread pool, and on Enterprise the IOCP, epoll and http.sys transports, and the number you reach depends on which of those you pick and on the host. Benchmark rather than take either number on trust.
WatchDog property on the client, which exposes Enabled, Interval, Attempts, Backoff of wdbFixed or wdbExponential, BackoffMultiplier, MaxInterval and Jitter. The published property, method, event and configuration lists for the IPWorks WSClient contain no reconnect facility, so that logic is yours to write. Both components do expose a Disconnected or OnDisconnect event to hang it from.
CompressionMethod on the client, defaulting to cmtdNone, and an EnablePermessageDeflate server setting that defaults to True and honours whatever the client asks for. sgcWebSockets exposes Extensions.PerMessage_Deflate with Enabled, ClientMaxWindowBits, ServerMaxWindowBits, ClientNoContextTakeOver, ServerNoContextTakeOver and MemLevel, so the negotiation parameters are yours to set.
HTTP component accepts an HTTPVersion of “3.0”, and the same page states that “HTTP/3 is supported only in .NET and Java”, so the Delphi Edition does not have it. sgcWebSockets ships TsgcHTTP3Client, TsgcHTTP3Server, TsgcQUICClient and TsgcQUICServer, though not in the three main editions: they arrive with the sgcQUIC pack, through the SGC_PACK_QUIC block in sgcVer.inc. HTTP/2 is a different story, and both products have a Delphi HTTP/2 client.
ipw for IPWorks and sgc for sgcWebSockets, so there is no name collision by construction. A team that already owns IPWorks for SFTP or EDI and wants the sgcWebSockets server for its real-time tier is a normal arrangement, and neither vendor asks for exclusivity.
All /n software pages were read on 6 September 2026. Where this page quotes /n software, the words in quotation marks are theirs. sgcWebSockets claims are grounded in the shipping 2026.9.0 source tree, and the unit or define is named in the row so a licensee can check it.
| Source | URL |
|---|---|
| /n software: full product catalogue | https://www.nsoftware.com/products |
| IPWorks: product overview and component list | https://www.nsoftware.com/ipworks |
| IPWorks: download page, current version and build | https://www.nsoftware.com/ipworks/download |
| IPWorks 2024 Delphi Edition reference, component list | https://cdn.nsoftware.com/help/IPJ/dlp/ |
| IPWorks 2024 Delphi Edition: WSClient component | https://cdn.nsoftware.com/help/IPJ/dlp/WSClient.htm |
| IPWorks 2024 Delphi Edition: WSServer component | https://cdn.nsoftware.com/help/IPJ/dlp/WSServer.htm |
| IPWorks 2024 Delphi Edition: HTTP component, HTTPVersion and the HTTP/3 note | https://cdn.nsoftware.com/help/IPJ/dlp/HTTP.htm |
| IPWorks 2024 Delphi Edition: Supported Platforms and deployment files | https://cdn.nsoftware.com/help/IPJ/dlp/platforms.htm |
| /n software: Delphi platform page, compiler and OS statements | https://www.nsoftware.com/platforms/delphi |
| IPWorks MQ: protocol versions supported | https://www.nsoftware.com/ipworks/mq |
| IPWorks MQ 2024 Delphi Edition reference, component list | https://cdn.nsoftware.com/help/ITJ/dlp/ |
| IPWorks IoT 2024 Delphi Edition reference, component list | https://cdn.nsoftware.com/help/IOJ/dlp/ |
| IPWorks IoT 2024 Delphi Edition: MQTTBroker component | https://cdn.nsoftware.com/help/IOJ/dlp/MQTTBroker.htm |
| IPWorks EDI: protocols and component list, source for the AS2 mention | https://www.nsoftware.com/ipworksedi |
| MCP SDK: product overview | https://www.nsoftware.com/mcpsdk |
| IPWorks: purchasing options for the Delphi Edition, part IPDJ-A | https://www.nsoftware.com/ipworks/order |
| /n software: Red Carpet Subscription | https://www.nsoftware.com/subscriptions |
| /n software: sales FAQ, toolkit only sales and support terms | https://www.nsoftware.com/order/faq |
| /n software: support options, standard and premium | https://www.nsoftware.com/support |
| IPWorks: end user licence agreement, trial term, royalty-free clause, reverse engineering clause | https://www.nsoftware.com/ipworks/license |
| sgcWebSockets: product page | https://www.esegece.com/products/websockets/ |
| sgcWebSockets: pricing, editions and what each includes | https://www.esegece.com/products/websockets/pricing/ |
| sgcWebSockets: full Delphi feature matrix | https://www.esegece.com/products/websockets/features/feature-matrix-delphi/ |
| sgcWebSockets: comparison against Indy, ICS, TMS FNC and mORMot 2 | https://www.esegece.com/products/websockets/comparison/ |
| RFC 6455, The WebSocket Protocol | https://datatracker.ietf.org/doc/html/rfc6455 |
| RFC 7692, Compression Extensions for WebSocket | https://datatracker.ietf.org/doc/html/rfc7692 |
IPWorks, IPWorks MQ, IPWorks IoT, MCP SDK, Red Carpet Subscription and /n software are trademarks of /n software inc., which has no involvement with this page. It is written by eSeGeCe, and eSeGeCe sells one of the two products compared. That is exactly why every claim above carries a link: go and check the ones that matter to your decision.
Other comparisons. The same treatment for TMS Software and for Chilkat, or the wider survey of Delphi and C++ Builder WebSocket libraries covering Indy, ICS and mORMot 2. If the library question is settled and you would rather see the code, the Delphi use cases take one job per page from an empty form to something that runs.