Beta platform program

The Cloudmore 5.0 beta lets you use the new platform alongside your current interface before your tenant switches over. This page explains what the beta is for, how to join, what to do once you are in, and how to bring your customers along.

Goal of the beta

The beta gives you time to get comfortable with 5.0 on your own terms, before it becomes the only interface.

• Learn the new platform at your own pace. The functions are much the same, but the navigation is new. The beta gives your team a week or two to settle in without pressure.

• Prepare your own materials. Refresh your manuals, screenshots and customer-facing guides while both interfaces are available.

• Set things up before you switch. Review your branding, dashboard links and billing report schedules so they are ready on day one.

• Shape the final release. Your feedback during the beta decides what we fix before the general rollout.

Who is it for and how to get in

The beta is for brokers. Brokers are invited in turn from November 2026. Once invited, you receive a separate URL for 5.0, which you can use alongside your current interface. Your current interface is not affected.

• Want to join sooner? To move up the invitation list, email the support team at support@cloudmore.com.

• Start with a few people. You choose who on your team gets the beta URL. Everyone else carries on in the current interface until you decide to widen access.

• No new accounts. Sign in with the same credentials you use today. Existing MFA and SSO setups keep working.

During the beta, the sign-in page is shared by all beta brokers and carries no branding. Your branding appears after sign-in. Your branded login moves to 5.0 on your switch date, not before.

The full timeline, including how branded login moves across, is in Switching over your Broker tenant.

What to do when you get access

Work through the New platform setup checklist at your own pace. It takes you in eight steps from your first sign-in to ready to switch:

1. Access the new platform beta.

2. Get familiar with the menu and navigation.

3. Set up your branding.

4. Set up the Organization dashboard and check its links.

5. Set up your billing report schedules.

6. Review your branded login page and test SSO.

7. Update your knowledge base.

8. Tell us how it went.

Also worth doing early: if anyone on your team still relies on the previous general billing report, move them to the current one. Access to the previous report ends when your tenant switches.

How to roll this out to your customers

Your customers do not need to do anything. They keep using your branded URL and their existing logins throughout the beta. On your switch date, your branded URL starts opening 5.0, with the same address, the same branded sign-in page and no new link or account.

To make the change smooth for them:

1. Get your own team ready first. Your team answers your customers' questions, so make sure they are comfortable in 5.0 before you switch.

2. Update what your customers see. Refresh your customer-facing knowledge base, screenshots and menu paths, and check the links on your Organization dashboard.

3. Tell your customers what is coming. We provide brandable announcement templates and short guides you can adapt for your end customers, so you do not have to write them from scratch.

4. Point out what is new for them. Customers gain clearer billing views, approvals of their own, easier quoting, passkeys and app-based MFA, and a branded sign-in page. See Cloudmore 5.0 and What has changed.

5. Choose your switch date. When you are ready, email support@cloudmore.com with your preferred date, at least three business days ahead. You can do this at any point from November 2026 through the transition period in January and February 2027. Your customers move with you on that day.

If you want selected customers to try 5.0 before your switch date, talk to the support team first.

When is the final deadline?

The beta period runs from November to the end of December 2026. January and February 2027 are the transition period: both interfaces continue to run side by side and you can switch at any point. You can switch your tenant to 5.0 at any time from November 2026.

On 1 March 2027, every broker that has not already moved is switched to 5.0, whether or not they took part in the beta and whether or not they chose a date of their own. From March 2027, all brokers and all customers are on 5.0.

There is no separate deadline for joining the beta, but the side-by-side window closes with the global switchover on 1 March 2027. Join early enough to leave your team a week or two to settle in and to update your materials, and remember to give us three business days' notice for your switch date.

How to report a bug, and known issues

Before you report something, check Known Issues and Bugs. It lists the pages that are not rebuilt in 5.0 yet and still open the old page, the pages being retired, and things that look like gaps but are by design.

To report something that is not on that list:

1. Click the Feedback button in the header.

2. Tell us which screen you were on, which role you were signed in as, and what you expected to happen.

You can also email support@cloudmore.com. Every beta broker has a named contact, so your feedback always has somewhere to go and you hear back about fixes. Please send feedback even when it is small.

Any other questions?

The questions brokers ask most, such as whether anyone needs new logins, whether the API keeps working and whether branding carries over, are answered in Frequently Asked Questions about 5.0.

If yours is not there, email the support team at support@cloudmore.com. That covers your rollout window, the beta invitation, questions about the platform and help with any step of the setup.