Cortlet
Cortlet Docs

Cortlet // Gateway

Cortlet Gateway

Cortlet Gateway is in development. The API and implementation details are not stable yet.

In development

Cortlet Gateway

Cortlet Gateway is currently in development.

The goal is to bridge persistent WebSocket connections to ordinary HTTP backends so applications can use realtime connections without requiring their own backend to keep those connections open.

Client
  ↓
WebSocket
  ↓
Cortlet Gateway
  ↓
HTTP
  ↓
Your backend

Development status

The hosted Gateway is not ready for production use yet.

The API is still being designed and implementation details may change before release.

This includes:

  • endpoint paths
  • request and response formats
  • authentication
  • event payloads
  • connection identifiers
  • retry behavior
  • rate limits
  • error formats
  • reliability guarantees

Do not build against undocumented Gateway API behavior yet.

What Cortlet Gateway is intended to do

Cortlet Gateway is being built to handle the persistent WebSocket side of a realtime application.

Your backend can remain HTTP-based while Cortlet manages the long-lived connection.

Conceptually:

WebSocket client
      ↓
Cortlet Gateway
      ↓
HTTP request
      ↓
Serverless function or backend

Why this exists

WebSockets are long-lived and stateful.

Many serverless environments are designed around short-lived HTTP requests.

Cortlet Gateway is intended to sit between those two models.

Instead of your application maintaining every persistent WebSocket connection itself, Cortlet can hold the connection and forward relevant events to your backend over HTTP.

Planned documentation

More documentation will be published as the Gateway becomes stable.

Planned areas include:

  • Quickstart
  • Architecture
  • Connections
  • Authentication
  • Webhooks
  • Incoming messages
  • Outbound messages
  • Event reference
  • Error reference
  • Rate limits
  • Reliability
  • Security
  • API reference

API status

The Gateway API is not stable yet.

Any current internal endpoints, schemas, or implementation details should be considered subject to change.

Stable API documentation will be published once those contracts are ready.

Availability

Cortlet Gateway is currently in development.

For general Cortlet information, visit cortlet.com.