[{"data":1,"prerenderedAt":132},["ShallowReactive",2],{"blog-en-websocket-infrastructure-real-time-1tool":3},{"id":4,"title":5,"body":6,"categories":112,"date":114,"description":12,"draft":115,"excerpt":116,"extension":117,"image":118,"lang":119,"meta":120,"modified":121,"navigation":122,"noindex":115,"path":123,"related":116,"seo":124,"seoDescription":125,"seoTitle":126,"slug":127,"sourcePath":128,"sourceRoute":116,"stem":129,"tags":116,"translated":115,"type":130,"wpId":116,"__hash__":131},"blog\u002Fen\u002Fblog\u002Fwebsocket-infrastructure-real-time-1tool.md","Real-time updates without detours: the WebSocket infrastructure behind 1Tool",{"type":7,"value":8,"toc":103},"minimark",[9,13,18,21,25,28,32,35,39,70,77,81],[10,11,12],"p",{},"Chat messages, live notifications and other real-time features depend on information reaching the right user without any noticeable delay. Many providers solve this by plugging in an external third-party service for the real-time connection. 1Tool takes a different route: the WebSocket infrastructure is operated by 1Tool itself — on its own servers, without customers having to install, configure or run anything. Technically, it is based on Laravel Reverb and is compatible with the widely used Pusher protocol — complemented by its own authorisation check that determines who is actually allowed to receive which real-time channels.",[14,15,17],"h2",{"id":16},"why-doing-without-an-external-provider-means-more-control","Why doing without an external provider means more control",[10,19,20],{},"Real-time connections run permanently in the background and sometimes carry sensitive information — such as chat content or notifications about business transactions. If 1Tool used an external third-party service for this, some of that data would inevitably leave the 1Tool platform, and the availability of these features would also depend on another provider. Because 1Tool instead runs this infrastructure itself on the basis of Laravel Reverb, all communication stays entirely within 1Tool's own servers. For customers, this means more control over the data flow and less dependence on the availability and terms of an external service — without having to run or manage anything themselves, and without giving up a proven, widely used protocol, since compatibility with the Pusher protocol provides a solid, established technical foundation.",[14,22,24],{"id":23},"channel-based-authorisation-real-time-data-only-for-those-entitled-to-it","Channel-based authorisation: real-time data only for those entitled to it",[10,26,27],{},"A real-time infrastructure is only as secure as its access control. If every user could receive events from every channel, information could quickly spread to unauthorised people — such as chat messages from a conversation you are not even part of. That is why 1Tool secures access to individual real-time channels with its own channel authorisation. Before a client is allowed to receive events from a particular channel, the system checks whether it actually has permission to do so. Only if this check is positive are events from that channel delivered at all.",[14,29,31],{"id":30},"what-this-means-for-users-in-practice","What this means for users in practice",[10,33,34],{},"In everyday use, this architecture delivers two things at once: real-time features such as chat or live notifications feel instant, because updates arrive directly and without delay — and at the same time it is ensured that every user only sees the events they are actually authorised to see. Customers don't have to take care of any part of this infrastructure themselves: operation, maintenance and security are entirely handled by 1Tool. This combination of infrastructure firmly built into the platform and granular authorisation checks is a key difference compared with a pure third-party solution — especially for a business system in which chat and notifications often involve confidential business information.",[14,36,38],{"id":37},"frequently-asked-questions","Frequently asked questions",[10,40,41,45,48,49,52,54,55,58,60,61,64,66,67],{},[42,43,44],"strong",{},"Do I as a customer have to host or run anything myself for 1Tool's real-time features?",[46,47],"br",{},"\nNo. The entire WebSocket infrastructure is operated by 1Tool itself on its own servers and is already included in the platform's feature set.\n",[42,50,51],{},"Does 1Tool use an external provider for real-time features?",[46,53],{},"\nNo. 1Tool runs its WebSocket infrastructure itself, based on Laravel Reverb and compatible with the Pusher protocol.\n",[42,56,57],{},"How do you prevent users from seeing events from channels that don't concern them?",[46,59],{},"\nThrough a dedicated channel authorisation: access to each real-time channel is checked before events from that channel are delivered.\n",[42,62,63],{},"Which features use the WebSocket infrastructure?",[46,65],{},"\nAmong others, chat and live notifications — that is, features where information should reach the user without delay.\n",[42,68,69],{},"Would you like to see how real-time features such as chat and notifications fit into your daily work with 1Tool?",[10,71,72],{},[73,74,76],"a",{"href":75},"\u002Fen\u002Fappointment-request\u002F","Book a demo",[14,78,80],{"id":79},"read-more","Read more",[82,83,84,91,97],"ul",{},[85,86,87],"li",{},[73,88,90],{"href":89},"\u002Fen\u002Fblog\u002Fapi-rate-limits-tailored-to-use-case\u002F","API access with rate limits that fit the use case",[85,92,93],{},[73,94,96],{"href":95},"\u002Fen\u002Fblog\u002F1tool-api-documentation-openapi-live\u002F","The 1Tool API: more than 2,500 endpoints, documented live",[85,98,99],{},[73,100,102],{"href":101},"\u002Fen\u002Fblog\u002Fai-agents-automated-document-processing\u002F","AI agents behind the scenes: automated document processing",{"title":104,"searchDepth":105,"depth":105,"links":106},"",2,[107,108,109,110,111],{"id":16,"depth":105,"text":17},{"id":23,"depth":105,"text":24},{"id":30,"depth":105,"text":31},{"id":37,"depth":105,"text":38},{"id":79,"depth":105,"text":80},[113],3330,"2026-07-06T09:00:00",false,null,"md","\u002Fmedia\u002F2026\u002F07\u002Fwebsocket-infrastruktur-echtzeit-1tool.jpg","en",{},"2026-07-25T08:26:45",true,"\u002Fen\u002Fblog\u002Fwebsocket-infrastructure-real-time-1tool",{"title":5,"description":12},"Self-hosted real-time infrastructure instead of a third-party service: how 1Tool technically delivers chat and live notifications.","Real-time updates: the WebSocket infrastructure","websocket-infrastructure-real-time-1tool","\u002Fen\u002Fblog\u002Fwebsocket-infrastructure-real-time-1tool\u002F","en\u002Fblog\u002Fwebsocket-infrastructure-real-time-1tool","posts","XWmS25LLFP1uBlWVwd3BQDF2KHewWdxTtAHKYM55N7Y",1791582058413]