[{"data":1,"prerenderedAt":236},["ShallowReactive",2],{"docs:list:en":3,"docs:page:en:credits\u002Ftechnologies\u002Foverview":66},[4,10,14,19,23,27,32,36,40,44,49,53,57,62],{"path":5,"title":6,"description":7,"section":8,"order":9},"\u002Fdocs\u002Fen\u002Fcredits\u002Foverview","Overview","The open source work Alluno stands on, grouped by the layer each project lives in.","Credits",1,{"path":11,"title":12,"description":13,"section":8,"order":9},"\u002Fdocs\u002Fen\u002Fcredits\u002Ftechnologies\u002Foverview","Stack","How the host, the services, the web client and the real time layer fit together.",{"path":15,"title":16,"description":17,"section":18,"order":9},"\u002Fdocs\u002Fen\u002Fgetting-started\u002Fintroduction","Introduction","What Alluno is, how a session actually works, and which parts of the product you will meet first.","Getting started",{"path":20,"title":6,"description":21,"section":22,"order":9},"\u002Fdocs\u002Fen\u002Fprivacy-policy\u002Foverview","What Alluno collects, what it deliberately never sees, and the choices you keep over both.","Privacy policy",{"path":24,"title":6,"description":25,"section":26,"order":9},"\u002Fdocs\u002Fen\u002Fterms-of-service\u002Foverview","The agreement between you and Alluno: what you may do, what we owe you, and where each ends.","Terms of service",{"path":28,"title":29,"description":30,"section":8,"order":31},"\u002Fdocs\u002Fen\u002Fcredits\u002Ftechnologies\u002Ffrontend","Frontend Architecture","The web client that decodes, syncs and paints a session in your browser, and what it is built from.",2,{"path":33,"title":34,"description":35,"section":18,"order":31},"\u002Fdocs\u002Fen\u002Fgetting-started\u002Finstallation","Installation","Install the host on the machine you want to reach, pair it once, and open it from any browser afterwards.",{"path":37,"title":38,"description":39,"section":22,"order":31},"\u002Fdocs\u002Fen\u002Fprivacy-policy\u002Fdata-collection-types","Data Types","Every category of data the service touches, why each one exists, and how long it is kept.",{"path":41,"title":42,"description":43,"section":26,"order":31},"\u002Fdocs\u002Fen\u002Fterms-of-service\u002Fbilling-payments-payment-terms","Payment Terms","Plans, billing cycles, how payment is taken, and what happens when one fails.",{"path":45,"title":46,"description":47,"section":8,"order":48},"\u002Fdocs\u002Fen\u002Fcredits\u002Ftechnologies\u002Fbackend","Backend Systems","The host on your machine and the services behind alluno.io, both written in Rust, and what they are built from.",3,{"path":50,"title":51,"description":52,"section":18,"order":48},"\u002Fdocs\u002Fen\u002Fgetting-started\u002Ffaq","FAQ","Straight answers on transports, encryption, what Alluno can and cannot see, plans and licensing.",{"path":54,"title":55,"description":56,"section":26,"order":48},"\u002Fdocs\u002Fen\u002Fterms-of-service\u002Fbilling-payments-commercial-disclosure","Commercial Disclosure","The trading details a subscription requires: who sells the service, from where, and on what terms.",{"path":58,"title":59,"description":60,"section":8,"order":61},"\u002Fdocs\u002Fen\u002Fcredits\u002Ftechnologies\u002Frealtime","Real-time Systems","The media and transport layer that moves a frame from the host to your screen in a few milliseconds.",4,{"path":63,"title":64,"description":65,"section":26,"order":61},"\u002Fdocs\u002Fen\u002Fterms-of-service\u002Facceptable-use-guidelines","Guidelines","What a machine on Alluno may be used for, and the handful of things that will end an account.",{"id":67,"title":12,"body":68,"description":13,"extension":229,"meta":230,"navigation":231,"order":9,"path":11,"section":8,"seo":232,"stem":233,"updated":234,"__hash__":235},"docs\u002Fdocs\u002Fen\u002Fcredits\u002Ftechnologies\u002Foverview.md",{"type":69,"value":70,"toc":220},"minimark",[71,75,108,113,141,145,212],[72,73,74],"p",{},"Four pieces move a frame from a machine to your browser. Each has its own page; this one shows how they connect.",[76,77,79,84,87,91,94,98,101,105],"steps",{"level":78},"3",[80,81,83],"h3",{"id":82},"the-host-captures-and-encodes","The host captures and encodes",[72,85,86],{},"A Rust application on the machine you reach. It captures the display, encodes on the GPU and publishes to whichever transport the session uses. On Windows it can run as a service and drive a virtual display.",[80,88,90],{"id":89},"the-services-broker-the-session","The services broker the session",[72,92,93],{},"A Rust API handles accounts, machines, plans and invites. A signaling server introduces host and viewer to each other and hands out relay access when a room needs one.",[80,95,97],{"id":96},"the-transport-carries-the-media","The transport carries the media",[72,99,100],{},"WebRTC for one to one, Media over QUIC for rooms. Both are encrypted end to end by the protocol itself.",[80,102,104],{"id":103},"the-web-client-paints-it","The web client paints it",[72,106,107],{},"A Nuxt application decodes in the browser, keeps video, audio and input on one clock, and sends your input back.",[109,110,112],"h2",{"id":111},"by-layer","By layer",[114,115,116,125,133],"card-group",{"cols":48},[117,118,122],"card",{"icon":119,"title":120,"to":121},"lucide:cpu","Backend","\u002Fdocs\u002Fcredits\u002Ftechnologies\u002Fbackend",[72,123,124],{},"Rust, Tokio, Axum, PostgreSQL, Redis.",[117,126,130],{"icon":127,"title":128,"to":129},"lucide:layout","Frontend","\u002Fdocs\u002Fcredits\u002Ftechnologies\u002Ffrontend",[72,131,132],{},"Nuxt, Vue, TypeScript, Tailwind CSS, Vite.",[117,134,138],{"icon":135,"title":136,"to":137},"lucide:zap","Real time","\u002Fdocs\u002Fcredits\u002Ftechnologies\u002Frealtime",[72,139,140],{},"FFmpeg, WebRTC, QUIC, Media over QUIC, ViGEmBus.",[109,142,144],{"id":143},"what-each-layer-owns","What each layer owns",[146,147,148,164],"table",{},[149,150,151],"thead",{},[152,153,154,158,161],"tr",{},[155,156,157],"th",{},"Concern",[155,159,160],{},"Lives in",[155,162,163],{},"Why there",[165,166,167,179,190,201],"tbody",{},[152,168,169,173,176],{},[170,171,172],"td",{},"Capture and encode",[170,174,175],{},"Host",[170,177,178],{},"Closest to the GPU and the display",[152,180,181,184,187],{},[170,182,183],{},"Accounts, plans, invites",[170,185,186],{},"Services",[170,188,189],{},"One source of truth for who may open what",[152,191,192,195,198],{},[170,193,194],{},"Introductions and relays",[170,196,197],{},"Signaling",[170,199,200],{},"Neutral ground both sides can reach",[152,202,203,206,209],{},[170,204,205],{},"Decode, sync, input",[170,207,208],{},"Web client",[170,210,211],{},"Nothing to install on the viewing side",[213,214,217],"callout",{"icon":215,"type":216},"lucide:info","note",[72,218,219],{},"Media never passes through the API. The services know that a session exists; they do not carry its frames.",{"title":221,"searchDepth":61,"depth":61,"links":222},"",[223,224,225,226,227,228],{"id":82,"depth":48,"text":83},{"id":89,"depth":48,"text":90},{"id":96,"depth":48,"text":97},{"id":103,"depth":48,"text":104},{"id":111,"depth":31,"text":112},{"id":143,"depth":31,"text":144},"md",{},true,{"title":12,"description":13},"docs\u002Fen\u002Fcredits\u002Ftechnologies\u002Foverview",null,"lYT37LOaYW8XhubILJ6nXmJh8R9FTYnbxUXjNH0hLy0",1789362703363]