Loading RoomHex
RoomHex
Request a demo Sign in

Run RoomHex on your own servers

Our team works through each step with yours to plan the environment, size it, and launch it.

Before install

We learn how your organisation meets and teaches, then agree how the deployment is built for your environment, capacity, and network.

Install and launch

We configure RoomHex for your domain and your roles, test it under your own conditions, provision access for your administrators, and go live.

After launch

We review with your team how the deployment is running, check the remaining capacity, and plan the next steps together.

Request a demoContact sales

From first conversation to a live environment

A RoomHex deployment moves step by step. We agree each step with your team before the next one starts.

  1. Discovery

    We learn how your organisation meets and teaches, and what you require for access, policy, and where data is stored.

  2. Design review

    Together we work out how the deployment is built for your environment, capacity, and network, and confirm that it suits the way you operate.

  3. Configuration

    We prepare RoomHex for your domain, your roles, and your policy settings.

  4. Validation

    We test the platform under your own conditions and confirm that calls and meetings stay secure and steady before anyone relies on it.

  5. Provisioning

    We review and provision access for your administrators before your users are brought on.

  6. Launch

    Your environment goes live on your own domain, and your team brings users on in the order you choose.

  7. Operational review

    After launch we review with you how the deployment is running, check the remaining capacity, and plan the next steps together.

What a deployment includes

Calls and meetings run self-hosted. Each organisation gets a separate environment on its own domain, and its administrators choose where the data is stored.

Self-hosting you control

There is no paid third-party service. Before launch we agree which domain serves RoomHex, and the naming and the way access is granted then follow your organisation.

Private single-customer environments

RoomHex runs as a private environment dedicated to one organisation. Your users, recordings, and settings are not shared with another customer.

On-premises and restricted networks

A deployment works in on-premises data centres and on restricted networks, so teams that cannot rely on the open internet still reach their sessions over a controlled route.

Capacity sizing

We size the deployment for the number of sessions and participants you expect, and the capacity can grow as your organisation grows.

Where your data is stored

Because you run the platform, your administrators choose where data and recordings are stored.

Responsibilities, written down YOUR TEAM CONTROLS The infrastructure The data Where it is stored AGREED BY BOTH TEAMS The scope of upgrades The support terms Every upgrade is reviewed and agreed before it is applied Signed before launch Signed before launch

Who is responsible for what

Because you run RoomHex yourself, we write down which tasks belong to our team and which belong to yours. Upgrade and support terms are agreed in writing, so both sides know what is covered and how changes are handled.

Plan a deployment for your organisation

A deployment review is a working conversation with our team. These are the points we agree with yours before anything is installed.

Start a deployment review
  1. The infrastructure your organisation will run RoomHex on
  2. The domain your environment is served from
  3. How large the environment has to be sized for your organisation
  4. Which tasks belong to our team and which to yours
  5. When you want the environment live