[thecoderpanda]

Solid first SaaS. Shipping something at 16 that solves a real infra pain point is no joke.

WebSocket management is one of those things that sounds simple until you're dealing with connection state, reconnects, and scaling across edge locations. The ephemeral session idea is smart for use cases like temp chat rooms or live event channels where you genuinely don't want messages persisted.

Few questions from a practical standpoint: what happens when a session hits connection limits? And what's the edge infra under the hood, Cloudflare Workers/Durable Objects? That'd be worth mentioning on the landing page since devs evaluating this will want to know what they're building on top of.

Also, since Google auth is broken, Might want to throw a banner on the signup page so people don't bounce thinking the whole thing is down.

Keep shipping. Most devs twice your age are still "planning" their first project.

[ryzmdotdev]

Thank you, I value your feedback. A durable object powers each session. Sessions currently have a fixed connection cap. New connections are denied when the limit is reached. To enable sessions to scale beyond a single object, I'm working on auto-splitting. Because Cloudflare Workers and Durable Objects power the entire system, there are no cold starts and everything operates at the edge. Today, we also fixed Google OAuth and updated the landing page with infrastructure details.