Reviewed access
Working today. There is no public signup or instant account. Accounts are provisioned after review, so your organization keeps a clear picture of who is allowed onto the platform at any time.
Feature directory
Every RoomHex capability, grouped and marked honestly
This directory lists what RoomHex does, area by area. Each capability is marked as working today, designed, or planned, so you always know what ships now and what is on the roadmap.
- Working today
- Designed
- Planned
- Self-hosted
Identity and access
Who gets in, and on what terms
Access to RoomHex is reviewed and provisioned, never open to public signup. These controls decide who can join and what they may do.
Secure session admission
Working today. Every session uses secure admission control, so a participant must be approved before they can obtain media. This keeps uninvited clients out of meetings on the working media core.
Role-based access
Designed. Role-based access and delegated administration are planned so owners grant the right permissions to admins, hosts, and members, and each person sees only what their role allows.
Meetings and calls
The working core, live today
This is the part of RoomHex that runs now, on a real self-hosted media core with an existing client app.
One to one calls
Working today. Place and receive one to one audio and video calls with ringing, answer, and end handling, carried by a low-latency self-hosted media core that keeps the call on your infrastructure.
Meeting rooms
Working today. Create and join meeting rooms with a participant grid, join approval, picture in picture, and a host and guest model, so group meetings have real structure rather than a flat call.
In-meeting controls
Working today. Share your screen, chat in the meeting, raise your hand, and manage mic and camera state, giving hosts and participants the everyday controls a working meeting needs.
Contacts and schedules
Working today. The existing client app keeps contacts and schedules, and warns about duplicate sessions, so people can find each other and plan meetings ahead without extra tools.
Classroom delivery
Structure that helps teachers teach
Classroom is a designed experience, not shipping yet. It is planned to turn a plain meeting into structured teaching.
Teacher command view
Designed. A calm command view is planned to give teachers attendance, hand raise, and a private help signal, so they can run a class with low effort while keeping an eye on every learner.
Polls and quizzes
Designed. Polls, quizzes, whiteboard, and breakout rooms are planned so teachers can check understanding and split a class into small groups, turning a lecture into an interactive session.
Lecture replay
Designed. Lecture replay and session outputs are planned so a live class becomes a lasting resource that learners can revisit, review at their own pace, and use to catch up after an absence.
Smart Sync Cinema
Watch together, in step, with respect for content owners
Smart Sync Cinema is a designed experience. It is planned to keep a shared session aligned while honoring content-owner rights, consent, and playback policy.
Coordinated playback
Designed. A shared session is planned to keep playback aligned for everyone, with catch-up for late joiners, so a group watches the same moment together instead of drifting out of step.
Reactions and spoiler-safe chat
Designed. Reactions, frame notes, and spoiler-aware chat are planned so a shared viewing feels social, letting people respond in the moment without giving away what is coming next.
Content-owner controls
Designed. Playback is planned to apply content-owner rights, consent, and viewing policy before it begins, so shared sessions respect licensing and never encourage unlicensed use of a work.
Content protection
Modest protection for shared content
Content protection is designed and described modestly. It is built to deter end users, not to promise absolute protection against every party.
Tokenized playback
Designed. Playback is planned to use short-lived access rather than direct file links, so content is not left sitting behind an open address that anyone could share or fetch on their own.
Playback audit
Designed. A playback audit is planned so owners can see how protected content was viewed. It raises the effort required to copy content, and is described as deterrence, not an unbreakable guarantee.
Honest limits
Designed. Protection defends against end users viewing content, and is not presented as absolute. We do not claim protection that cannot be bypassed, and we describe what this feature can and cannot do plainly.
Recording and meeting outcomes
Turn a session into a lasting record
Recording and post-session outcomes are designed, not shipping. They are planned to gather what happened into one clear record.
Session recording
Designed. Recording is planned to run on your own storage, so captured sessions stay inside your boundary. This keeps a replayable record without sending media to an outside service you do not control.
Meeting Capsule
Designed. A meeting summary is planned to collect decisions, action items, unresolved questions, and mentions, so a team leaves a session with a clear written record instead of scattered notes.
Permission-gated export
Designed. Export of outcomes is planned to respect permission and content-owner policy, so recordings and summaries are shared only with people who are allowed to receive them.
Language workflows
Captions and translation inside your boundary
Language features are planned and provider-neutral. They are designed to run inside your own boundary, with human review and respect for content-owner rights.
Live captions
Planned. Live captions are designed to run inside your own boundary, without naming any outside provider. Human review is expected before a caption is trusted, so accuracy is checked rather than assumed.
Translation and subtitles
Planned. Live translation and translated subtitles are designed to help mixed-language groups follow along, with a correction workflow so a person can review and fix wording before it is relied on.
Rights-aware dubbing
Planned. Dubbing and translation are designed to respect content-owner rights and run only when license and policy allow. No external model or provider is named, and output stays inside your boundary.
Network Doctor and diagnostics
Turn connection trouble into plain language
Network Doctor is a designed surface. It is planned to explain session problems in plain words, on top of the working media core's diagnostics.
Plain-language reasons
Designed. Instead of raw technical data, Network Doctor is planned to tell users why a session is struggling in plain words, so people understand the problem without needing a support engineer to translate.
Device, network, or region
Designed. The surface is planned to show whether the device, the network path, or a busy region is the cause, so a user and support both know where a problem sits before they start fixing it.
Less guesswork for support
Designed. By turning connection signals into clear reasons, the diagnostics view is planned to cut the time support spends guessing, so common session problems get resolved faster and with less back and forth.
Activity rooms
Interactive rooms that bring people together
Activity rooms are a designed set of interactive experiences, not shipping yet. They are planned to make sessions more engaging.
Games and activities
Designed. A set of light group games and activities is planned to warm up meetings and classes, giving hosts a simple way to build energy and connection without leaving the RoomHex session.
Phone as controller
Designed. Using a phone as a controller is planned so participants can join an activity from a second device, keeping the main screen clear while everyone still takes part in the room.
Class and team challenges
Designed. Team and class challenges are planned to fit teaching and workplace sessions, so a group can compete, review, or reflect together in a way that supports the goal of the meeting.
Administration and branch governance
Set policy once, delegate to every site
Organization and branch governance is a designed capability rendered in scaffold today. It is planned to let owners govern the whole organization from one console.
Organization and branch controls
Designed. Organization, branch, and user level controls are planned so an owner sets policy at the top, local admins apply it per site, and each branch stays within the organization's rules.
Delegated administration
Designed. Role-based access and delegated administration are planned so day to day management can be handed to the right people at each site, without giving everyone the keys to the whole organization.
Tiered licensing and policy
Designed. Tiered licensing and policy management are planned so an organization can manage plans, users, and permissions from one self-hosted admin console. Plans are presented positively, not as security guarantees.
Integrations
Designed to fit the systems you already run
Integrations are planned and provider-neutral, not built yet. They are designed to connect RoomHex with the tools your organization already operates.
Identity and calendar
Planned. Connections to your identity directory and calendar are designed so people sign in through systems you already run and schedules line up, without RoomHex becoming yet another separate account to manage.
Storage and reporting
Planned. Storage and reporting connections are designed so recordings land on storage you control and activity flows to your own reporting systems, keeping data inside the boundary your organization operates.
Provider-neutral by design
Planned. Integrations are designed to be provider-neutral, so you are not locked to one vendor. They are meant to fit around your existing systems rather than force your organization to adopt a fixed stack.
Deployment options
Self-hosted today, multi-region by design
Single-node self-hosted deployment is real and documented. Multi-server and multi-region topology is designed and on the roadmap.
Self-hosted deployment
Working today. RoomHex runs self-hosted behind your own domain, with no paid external service in the runtime path. Single-node deployment of the media core is verified and documented, so your organization can run it on its own.
Fail-closed security
Working today. The media core fails closed, refusing to run without its signing secrets, and applies strict security headers and rate limiting. Communication stays inside your boundary rather than passing through an outside service.
Multi-region topology
Designed. Multi-server and multi-region deployment is planned so larger organizations can place capacity close to their sites. Today, single-node is the verified path, and multi-region is on the roadmap.
Want a closer look at any of these?
Request a reviewed demo to see the working core live, or contact sales to talk about the roadmap for your organization.