Rutba Meet Coming soon

Where Rutba Meet actually stands. Part of Meet runs today, in the Comms app: the shared calendar, scheduling and a calendar feed to subscribe to. Invitations sent and answered by email, and reminders on every occurrence of a recurring event, are built and are not switched on in production yet. The meeting room waits on one deployment. The media server it talks to is not running yet, which is why Meet is not sold on its own. The room itself is built and tested: screen sharing, host mute and remove with a guarantee that a room is never left with nobody in charge, a lobby you knock at and are admitted from, meeting lock and passcode, guest join without a Rutba account (passcode-only, off until a host turns it on, rate-limited so a six-digit code cannot be swept), raised hands and reactions, polls, breakout rooms, a shared whiteboard, background blur, noise suppression, audio-only fallback when the line struggles, a pre-join camera and microphone check, active-speaker and grid with per-viewer pinning, in-meeting chat, a shared document everyone edits at once, an attendance report with CSV, and recording retention that detaches rather than destroys. Recording happens on the server or on your own machine, only after every participant has seen the notice, with the server refusing an undeclared one, and the file is stored in Drive. Still absent: transcripts and live captions, AI summaries, background replacement, dial-in from an ordinary phone, and end-to-end encryption, which would rule out recording on the server and is still an open decision.