Notta Socket: Managed WebSockets at a price that actually makes sense.

Real-time features kept costing way more than they should. Pusher works brilliantly but the per-message billing gets painful fast at any kind of scale. Self-hosting Reverb or Soketi is the DIY alternative, but that means babysitting servers, which nobody has time for. So I built Notta Socket: a managed WebSocket service that's API-compatible with Pusher and Laravel Reverb (no code changes, just swap credentials), priced by capacity so there are no billing surprises, and treats your data as a pipe, not a bucket. We don't store or mine anything in transit. It's been running in production for a few months. I'd genuinely love to hear what you think, especially whether the pricing model makes sense to you or if there's something obvious I've missed.

Forum Threads

p/notta-socket

•

5mo ago

What are you doing to manage WebSockets in production?

Hi everyone, I am @eagostini, the founder of Notta Socket.

I built this because I kept running into the same two options: pay more than I wanted to for managed WebSocket services, or roll my own and spend time maintaining infrastructure instead of product.

View all