Broch Cloud

The Broch hosted server at trial.broch.io lets prospective customers try Broch tunneling before committing to a self-hosted deployment. It is intentionally limited and is not a production offering.

Broch Cloud is not a substitute for self-hosting

Most of the important benefits of Broch require self-hosting:

• Your own identity provider — SSO via Entra ID, Okta, Auth0, or any OIDC provider. Broch Cloud uses shared Broch authentication.
• Ingress control — Share Policies restrict who can reach your tunnels by IP network (CIDR), geographic region, HTTP header matching, or any combination. Only available on a self-hosted server.
• Audit logs — Full audit trail of who accessed what and when.
• Data sovereignty — Traffic tunnelled through your own infrastructure, never through Broch servers.
• Your own domain — Tunnel URLs under your wildcard domain (*.tunnels.company.com).

If you are evaluating Broch for your organization, plan to self-host. See the Self-Hosting guide.

Already self-hosting? If your organization runs its own Broch server, skip this page. Your admin will give you the server URL to use in place of trial.broch.io.

Step 1: Install the CLI

npm install -g broch

Verify the installation:

broch --version

Step 2: Configure the Server URL

broch config set --server https://trial.broch.io

Step 3: Authenticate

broch auth login

This opens your browser for sign-in. After you authorize, the CLI is ready to use.

Step 4: Create Your First Tunnel

broch share my-app --target http://localhost:3000

Replace 3000 with the port your local service is running on. Broch generates a public HTTPS URL you can share immediately.

Next Steps

• CLI Reference — All commands and options
• Self-Hosting — Deploy Broch for your team

Feedback

broch feedback "Your message here"

Or email [email protected].