Native support for web sockets

We've been attempting to migrate our app from sapper to sveltekit and ran into the problem of web sockets, in sapper we could simply attach the WebSocket server directly to the express server and be done with it, but as per Rich Harris' comments [here](https://github.com/sveltejs/kit/issues/334#issuecomment-804987028) and here [here](https://github.com/sveltejs/kit/issues/334#issuecomment-806289525) in sveltekit we don't want to expose direct access to the middlwares thus promoting the node adapter over the serverless ones. However seeing as some of the serverless providers are starting to support web sockets ([cloudflare](https://blog.cloudflare.com/introducing-websockets-in-workers/)) ([begin](https://blog.begin.com/introducing-architect-5-0-fully-serverless-websockets-20bb97673c4e)) ([AWS Lambda](https://aws.amazon.com/blogs/compute/announcing-websocket-apis-in-amazon-api-gateway/)) should sveltekit provide a way to handle these connections directly? A native approach to this could also potentially provide a tool to solve this [issue](https://github.com/sveltejs/kit/issues/87) and [this](https://github.com/sveltejs/kit/issues/887) **Describe the solution you'd like** An interesting solution could be to expose functions in endpoints in the same way we handle http requests, and then let the adapters handle the rest ```routes/api/index.ts``` ```js // Handle post requests export const post: RequestHandler = async (request) => {....} // Handle web socket requests export const ws: WebSocketRequestHandler = async (request) => {....} ``` A concern with this approach could be mixing protocols, within an endpoint could be confusing. Another could be if this becomes too complicated since as far as I know the initial [handshake](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API/Writing_WebSocket_servers#the_websocket_handshake) to start a WebSocket connection is handled over http, would this then be handled directly by sveltekit which cou

GitHubMay 19, 2021ToolOtherSource

FL score

out of 100

Verdict

VALIDATE

high confidence

Competition

competitors found, nascent market, funded players

Trend

8 community mentions

A SvelteKit-native WebSocket integration via endpoint functions, addressing developer frustration with existing workarounds, but facing direct competition from SvelteKit's own impending solution.

The pain

SvelteKit developers face significant frustration and complexity integrating WebSockets, especially when migrating from Sapper or using serverless environments. Current workarounds are cumbersome and not seamless.

The gap

The gap is for a truly native, idiomatic SvelteKit WebSocket API that works consistently across various adapters, particularly serverless. Existing solutions are mostly external libraries, manual setups, or broad real-time platforms, not integrated framework features.

Build angle

Develop a plug-and-play SvelteKit solution for native WebSocket handling through endpoint functions, focusing on seamless integration across different adapters, particularly serverless (Cloudflare Workers, etc.).

Strengths

Real, specific, and urgent pain point for SvelteKit developers.
Clear demand for better WebSocket integration, especially in serverless.
Growing trend towards real-time applications and SvelteKit adoption.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Native support for web sockets”.

Open FlyBot

Fly Labs Method

Is the pain real, is there a gap, is it the right time, can one person build it.

Problem clarity: 26
Solution gap: 15
Willingness to pay: 14
Buildability: 10

This idea addresses a real and urgent pain point for SvelteKit developers regarding native WebSocket support, but the primary gap is closing fast as SvelteKit itself is developing a solution. Willingness to pay for a third-party tool is low, and the build complexity for a single person to compete with a core framework feature is high.

Value Equation

Dream outcome and how likely it feels, against the time and effort it costs.

While a clear pain exists in a growing market, the viability for a standalone product is low due to SvelteKit's impending native solution and unclear willingness to pay.

One-Person Business

Curiosity pull, identity fit, and a path from free value to paid for a solo creator.

Clear problem for a niche audience, but monetization is unlikely and SvelteKit is already filling the gap, making it a poor fit for a solo SaaS.

Viral Frameworks

Hook strength, shareability, and how cheaply it can be tested.

Specific audience and clear value, but a poor business model, high distribution challenges, and significant risk due to SvelteKit's own development.

Builder Lens

Evidence the problem exists, timing, defensibility, and a model that fits on a napkin.

Strong demand and clear problem, but the 'narrowest wedge' to payment is difficult and the core framework is addressing the need directly, reducing future fit for a third-party tool.

Why this verdict

The composite score is 48, indicating a 'VALIDATE_FIRST' verdict. While the pain is undeniably real and the market for real-time apps is growing, the critical issue is SvelteKit's direct engagement in solving this problem. The research explicitly states 'Native support for Websockets in SvelteKit is now available for testing!' This means a solo builder would be attempting to productize a core feature that the framework itself is providing, making it a 'dominated' competition level. This severely diminishes the gap for a new product, makes monetization highly unlikely (as developers expect core features for free), and creates a significant risk of obsolescence. Building such a feature robustly is also a substantial undertaking for a solo builder. Therefore, extensive validation is needed to find an unserved niche or a specific paid angle that SvelteKit's official solution will not cover, or else this is primarily an open-source contribution opportunity.

Five lenses, one composite. How scoring works

The angle

This weekend

Deeply research the progress of SvelteKit's native WebSocket support (beyond 'testing versions available') to understand its scope, timeline, and capabilities.
Engage directly with SvelteKit developers experiencing this pain to validate their specific needs and, crucially, their willingness to pay for a *third-party* solution (even a highly polished one) if SvelteKit's native solution lands.
Consider contributing to SvelteKit's official efforts if the goal is to solve the problem, rather than create a separate product.
If pursuing a product, identify an extremely narrow, unserved niche or specific problem *within* WebSocket integration that SvelteKit's native solution will *not* address (e.g., a specific advanced security feature, a unique serverless runtime's edge case that no one else is handling).

Who is already there, nascent market

svelte-adapter-bun
SvelteKit adapter for Bun runtime, which supports WebSockets natively via Bun.serve()
Pricing: free
socket.io (with SvelteKit)
Popular WebSocket library that can be attached to SvelteKit server using adapter-node in hooks.server.js
Pricing: free
Supabase RealtimeFunded
Realtime subscriptions over WebSockets, integrates with SvelteKit apps
Pricing: free tier, paid plans
Socket.IOVisit
A popular library for real-time, bidirectional, event-based communication. It works on every platform, browser or device, focusing on reliability and speed.
Pricing: Open Source (free)
ws (Node.js WebSocket library)Visit
A simple to use, blazing fast, and thoroughly tested WebSocket client and server for Node.js.
Pricing: Open Source (free)
AblyFundedVisit
A serverless WebSockets platform that helps developers scale real-time experiences like live chat and multiplayer collaboration for millions of users.
Pricing: Offers various plans, including a free tier, and scales based on usage (messages, connections, etc.)
PubNubFundedVisit
A real-time communication platform offering APIs for chat, live updates, IoT, and more, handling infrastructure for persistent connections.
Pricing: Usage-based pricing, with various plans available.
Financial Modeling Prep (FMP) WebSocket APIsVisit
Provides real-time WebSocket streaming APIs for live financial data (stocks, crypto, forex).
Pricing: Offers individual and commercial plans, including a basic tier for testing. Paid plans are required for real-time data for commercial use.
EODHD Real-Time Data API via WebSocketsVisit
Offers real-time financial data for US market, Forex, and Digital Currencies via WebSockets with low latency.
Pricing: Real-time data is available in paid plans (EOD+Intraday and ALL-IN-ONE).
Finnhub WebSocketVisit
Streams real-time financial data, including press releases, for global companies.
Pricing: Premium access required for real-time press releases and other features.
Finlight.me Real-Time Financial News StreamingVisit
Streams real-time financial news with sub-second latency via WebSocket connections, with advanced filtering.
Pricing: Not explicitly detailed, but implies a service requiring a subscription for real-time data.

Funded players

Gaps they leave open

Seamless native WebSocket attachment across all SvelteKit adapters including serverless (Vercel Edge, etc.)
Plug-and-play like Sapper/Express integration
Zero-config migration from Sapper

What people say, 8 mentions

Drop-in Awesome List
r/SaaS
I switched from email only to multichannel (email + linkedin) and reply rates roughly doubled. sharing what worked and what didnt.
r/Entrepreneur
Today I declined funding, I’m a bit conflicted.
r/Entrepreneur
Closed a small SaaS acquisition, here’s how long it actually took
r/Entrepreneur
Ride Sharing App Development: A Practical Guide Based on Real-World Research (2026)
r/SaaS
Prepping to Start my Business
r/Entrepreneur
Built an AI SaaS tool — here are my takeaways and mistakes.
r/SaaS
Built a Headless CMS That Lets You Update UI Instantly – Without App Rebuilds
r/SaaS

r/r/SaaS r/r/Entrepreneur

Native support for web sockets

SaaS founders lack a platform for finding partners and organizing joint advertising campaigns with bloggers to reduce costs by 5 times while maintaining the same reach

Founders waste hours daily on repetitive tasks that AI could automate instantly

Owners of modern Macs can't launch old games due to complex instructions involving emulators and file conversion