Blog
Guides and news on secure self-hosted realtime communication.
A class held in a meeting room still owes things a meeting never owes. For whoever has to decide whether the setup already in use will carry teaching, this is what those extra obligations turn out to be.
Read guide
When a site has no administrator of its own, who provisions its accounts? Every recurring duty in a multi-site deployment belongs to exactly one role at one location, and the duties that go wrong are the ones left unassigned.
Read guide
Your microphone is open and nobody can hear you. A diagnostic table for the symptoms that come up week after week, written to be used during the call rather than read in advance.
Read guide
Three people touch a meeting record and none of them does the other's job. This sets out where the host stops, what the reviewer is actually reading for, and why the person who ran the meeting is the wrong one to sign the record off.
Read guide
Every fix a group tries for this fails for the same reason, from announcing a pause in the chat to counting down together. The reason is mechanical and it sits in the players. Worth reading before anyone in your group gets blamed for it.
Read guide
Judging a virtual classroom platform from memory once the demo has ended means choosing between presenters rather than products. Four criteria to score while the room is still open, each paired with the thing to make the presenter do live and the answer that should count against them.
Read guide
For a teacher taking a class into class mode for the first time. It follows one hour end to end and stays on the practical side: what is worth preparing in advance, and which of the six class controls earn their place once you are actually teaching.
Read guide
Not every call needs a door on it. A handful of questions about your own week, answerable in a couple of minutes. They tell you whether controls would be doing real work in your organisation or just adding steps.
Read guide
An encrypted meeting can still have the wrong person sitting in it. Encryption is about the wire, not the guest list. Written for whoever configures a deployment, this follows the stages between an account existing and a host removing somebody mid-session.
Read guide
If you have ever had to tell a client where a conversation actually took place, the answer came down to a handful of choices made long before anyone asked. Here they are. Each carries a standing duty for somebody on your side.
Read guide
Every protection in a RoomHex deployment has an edge past which it does nothing, and this is the list of those edges, written so a security team can see in one pass which gaps stay theirs to cover.
Read guide
Nobody thinks about the network until it fails. This describes what a RoomHex call does about a connection that narrows or drops out mid-sentence, and the six states a participant can be in while that is happening.
Read guide
Language tooling is easy to buy and hard to place in a workflow, so this sets out where it fits and who is holding the output at every point, along with what a buyer should ask about accuracy instead of asking for a percentage.
Read guide
Watching one film together is a coordination problem before it is a feature list. This is the shape of the answer: what the session owns, and what a viewer's own controls still do. The content owner's terms come into it before anything plays.
Read guide
Book the install date last. What this covers is the work in front of it, in a form you can hand to whoever runs your network and whoever will own the deployment afterwards.
Read guide
A plain description of the platform for somebody hearing the name for the first time: what one deployment contains, what a user does in a session, and which administrative jobs the arrangement creates.
Read guide