Customer-controlled self-hosting
The self-hosted media core runs on infrastructure your organization operates, with no paid third-party service in the runtime path, so calls and meetings stay inside your boundary.
Deployment you own end to end
Run RoomHex where your organization decides
RoomHex is built to run on infrastructure your organization controls, with a working self-hosted media core and a reviewed process that takes a deployment from first conversation to launch.
- Customer-controlled
- Working media core
- Private single-customer environments
- Reviewed launch
How RoomHex is deployed
One platform, deployed on your terms
The real-time media core is self-hosted and working today. Around it, deployment is planned so each organization keeps its own environment, domain, and data location.
Private single-customer environments
RoomHex is designed to run as a private environment dedicated to one organization, so your users, media, and settings are not shared with any other customer.
On-premises or restricted network
Deployment is designed to fit on-premises data centers and restricted networks, so teams that cannot rely on the open internet still keep a controlled path to their sessions.
Domain and deployment planning
Before launch, we plan how RoomHex sits behind your own domain and how each part is arranged, so the deployment matches your naming, access, and operating model.
Media capacity planning
We size the media core to your expected sessions and participants, so capacity is planned for real use rather than guessed, and can grow as your organization does.
Data residency control
Because you run the platform, you decide where data and media live. RoomHex is built so that content stays on infrastructure you choose and control.
How a deployment works
From first conversation to a live environment
Every RoomHex deployment follows a reviewed process. Each step is agreed with your team before the next begins, so there are no surprises at launch.
-
Discovery
We learn how your organization meets, teaches, and shares media, and what your access, policy, and residency needs are.
-
Architecture review
Together we agree how the deployment is shaped for your environment, capacity, and network, and confirm it fits your operating model.
-
Configuration
We prepare RoomHex for your domain, roles, and policy settings, so the platform is ready to match how your teams work.
-
Validation
We check media, admission, and reconnect behavior against your conditions, so the environment is proven before anyone relies on it.
-
Provisioning
Access is reviewed and provisioned for your administrators, so the right people hold the right controls from day one.
-
Launch
Your environment goes live behind your own domain, with your team ready to bring users on in the order you choose.
-
Operational review
After launch we review how the deployment is running with you, confirm capacity headroom, and plan any next steps together.
Support boundaries
Clear lines on who does what
Because you run RoomHex yourself, it helps to know where our responsibility ends and yours begins. Upgrade and support boundaries are agreed in writing, so both sides know what is covered and how changes are handled.
- Upgrade and support scope agreed before launch
- You control your infrastructure, data, and residency
- Planned upgrades follow a reviewed, agreed path
Plan a deployment for your organization
Start a deployment review with our team, or request a reviewed demo to see the working media core in action.