WebSockets are stateful.
Serverless isn't.
Cortlet keeps persistent WebSocket connections alive while your backend stays stateless, short-lived, and HTTP-native.
CONNECTION
Persistent
Cortlet stays connected
TRANSPORT
HTTP
Your backend stays ordinary
COMPUTE
Stateless
Functions come and go
WebSocket
Realtime wants to stay alive.
Serverless
Compute wants to disappear.
WebSocket
Persistent.
One connection can remain active long after the request that created it.
Serverless
Temporary.
Functions execute when needed, return a result, and disappear again.
Cortlet
The layer between.
Keep the connection. Keep serverless.
Cortlet handles the persistent layer while your application continues working through ordinary HTTP.
Cortlet explained
Keep the socket.
Keep your backend simple.
Cortlet owns the persistent connection layer. Incoming WebSocket activity becomes ordinary HTTP events your existing backend can process.
Persistent at the edge
Cortlet maintains the long-lived connection between your client and the realtime layer.
HTTP at your backend
Socket events are translated into ordinary HTTP requests instead of forcing your application to stay alive.
Your architecture stays yours
Keep your existing framework, functions, API routes, databases, and deployment platform.
One separation
Connection lifetime
≠ compute lifetime.
Cortlet separates the two so each part of your system can behave the way it was designed to.
The translation layer
Persistent connection in.
Ordinary HTTP out.
WebSocket
wss://connect
HTTP endpoint
POST /events
Good fits
Realtime where you need it.
Notifications
Push realtime notifications to connected clients without running your own always-on socket server.
Background jobs
Send progress and completion events from serverless workloads back to connected users.
Application events
Deliver low-frequency realtime state changes while your backend remains HTTP-first.
Intentionally focused
Built for realtime.
Not every kind.
Cortlet is designed for notifications, job progress, server-generated events, and similar serverless workloads. It is not trying to replace specialized multiplayer engines or high-frequency collaborative state systems.
Your stack stays your stack
If it speaks HTTP,
it speaks Cortlet.
What we believe
Realtime shouldn't decide your backend architecture.
You should not have to abandon serverless architecture just because one part of your application needs a persistent connection.
