Deploy a WebSocket server
Keep WebSocket connections attached to a normal server process instead of adapting the application to short function invocations. Tokay runs the existing server on a dedicated virtual machine and accepts secure WebSocket connections on its HTTPS hostname.
Last updated
The existing server can stay intact
You do not need a function wrapper or a separate realtime provider to host working WebSocket code. Push or paste the app, and Tokay detects servers built with Socket.IO, ws, FastAPI WebSockets, Django Channels, and other framework upgrade handlers.
We prepare the entry point, packages, and environment variables from the source before deployment.
Connection state stays with the process
Tokay keeps rooms, presence, session state, and connection maps in the process that owns them, so the server behaves as it does locally. Connections do not end because a function reaches a duration limit, and a crashed process is restarted and reported.
Clients should still reconnect after a deploy or machine restart. That is normal WebSocket behavior rather than a platform invocation timer.
The rest of the product runs beside it
A database, Redis resource, worker, or scheduled job can share the same Project, which avoids splitting the application across unrelated hosts. Tokay supplies supported database connections and secrets through the environment variables each Service already reads.
Your AI agent can verify a real connection
A coding agent like Claude Code or Codex can deploy the existing server and test the behavior that matters. Through Tokay's GraphQL API, it can submit the source, deploy the Service, read the returned URL, open a WebSocket connection, and confirm a message round trip.
Point your agent to app.tokay.io/llms.txt for the deployment protocol.
Tokay has a very generous free tier with no credit card. Get started.