[{"data":1,"prerenderedAt":221},["ShallowReactive",2],{"compare:/compare/supabase":3},{"id":4,"title":5,"body":6,"description":213,"extension":214,"meta":215,"navigation":216,"path":217,"seo":218,"stem":219,"__hash__":220},"compare/compare/supabase.md","NoLag vs Supabase Realtime",{"type":7,"value":8,"toc":204},"minimark",[9,13,17,20,25,124,128,151,155,166,170,181,185],[10,11,5],"h1",{"id":12},"nolag-vs-supabase-realtime",[14,15,16],"p",{},"Supabase is an all-in-one backend built around Postgres, with authentication, storage, edge functions, and a Realtime feature for broadcasting database changes, presence, and messages over WebSocket. NoLag is dedicated realtime messaging infrastructure with the same pub/sub foundation, plus two things Supabase Realtime does not focus on: blueprint SDKs for common app patterns, and a coordination layer built for AI agents.",[14,18,19],{},"Short version: if you want a managed Postgres backend and realtime is one feature alongside it, Supabase is a great fit. If realtime messaging and agent coordination are the core of what you are building, and you do not want to be tied to a specific database, NoLag is built for that.",[21,22,24],"h2",{"id":23},"at-a-glance","At a glance",[26,27,28,43],"table",{},[29,30,31],"thead",{},[32,33,34,37,40],"tr",{},[35,36],"th",{},[35,38,39],{},"NoLag",[35,41,42],{},"Supabase Realtime",[44,45,46,58,69,80,91,102,113],"tbody",{},[32,47,48,52,55],{},[49,50,51],"td",{},"Core model",[49,53,54],{},"Realtime pub/sub over WebSocket",[49,56,57],{},"Realtime over WebSocket, coupled to Postgres",[32,59,60,63,66],{},[49,61,62],{},"Database",[49,64,65],{},"Database-agnostic, bring your own",[49,67,68],{},"Postgres, part of the platform",[32,70,71,74,77],{},[49,72,73],{},"High-level SDKs",[49,75,76],{},"Blueprints for chat, notify, feed, dashboards, tracking, sync, and more",[49,78,79],{},"Realtime channels: broadcast, presence, Postgres changes",[32,81,82,85,88],{},[49,83,84],{},"AI-agent coordination",[49,86,87],{},"Built in: dispatch, share state, observe, approve",[49,89,90],{},"Not a focus",[32,92,93,96,99],{},[49,94,95],{},"Delivery",[49,97,98],{},"Presence, QoS levels",[49,100,101],{},"Presence, broadcast, change data capture",[32,103,104,107,110],{},[49,105,106],{},"Authentication",[49,108,109],{},"Actor tokens with per-topic ACL; short-lived browser JWTs minted offline",[49,111,112],{},"Postgres Row Level Security via JWT",[32,114,115,118,121],{},[49,116,117],{},"SDKs",[49,119,120],{},"JavaScript/TypeScript, Go, Python",[49,122,123],{},"Client libraries across several languages",[21,125,127],{"id":126},"where-nolag-is-different","Where NoLag is different",[129,130,131,139,145],"ul",{},[132,133,134,138],"li",{},[135,136,137],"strong",{},"Not tied to a database."," NoLag is a messaging layer you can put in front of any stack, rather than realtime bound to Postgres change feeds.",[132,140,141,144],{},[135,142,143],{},"Blueprint SDKs."," A domain-specific API for chat, notifications, dashboards, tracking, and more, so you skip the plumbing.",[132,146,147,150],{},[135,148,149],{},"A coordination layer for AI agents."," Dispatch, share state, observe decisions, and gate actions with human approval, framework-agnostic and on the same infrastructure as your app features.",[21,152,154],{"id":153},"where-supabase-is-a-strong-fit","Where Supabase is a strong fit",[129,156,157,160,163],{},[132,158,159],{},"You want a managed Postgres backend with auth, storage, and functions in one place.",[132,161,162],{},"Your realtime needs are mostly reacting to database changes.",[132,164,165],{},"You are happy to standardise on the Supabase ecosystem.",[21,167,169],{"id":168},"when-to-choose-nolag","When to choose NoLag",[129,171,172,175,178],{},[132,173,174],{},"You are building AI-agent features and want coordination primitives, not just transport.",[132,176,177],{},"You want higher-level SDKs to ship common realtime patterns quickly.",[132,179,180],{},"You want realtime messaging that is independent of your database choice.",[21,182,184],{"id":183},"try-it","Try it",[14,186,187,188,193,194,198,199,203],{},"Follow the ",[189,190,192],"a",{"href":191},"/docs/getting-started","5-minute quick start",", then look at the ",[189,195,197],{"href":196},"/docs/high-level-sdks","high-level SDKs"," and the ",[189,200,202],{"href":201},"/docs/agents","AI agents"," guide.",{"title":205,"searchDepth":206,"depth":206,"links":207},"",2,[208,209,210,211,212],{"id":23,"depth":206,"text":24},{"id":126,"depth":206,"text":127},{"id":153,"depth":206,"text":154},{"id":168,"depth":206,"text":169},{"id":183,"depth":206,"text":184},"NoLag vs Supabase Realtime: both give you realtime over WebSocket. Supabase ties realtime to a Postgres backend; NoLag is dedicated realtime infrastructure with blueprint SDKs and a coordination layer for AI agents.","md",{},true,"/compare/supabase",{"title":5,"description":213},"compare/supabase","ZA8uo1X6oiRC8bMIWKc-66zwSeqLKSpqCDndBFhh3kU",1788160342078]