Skip to contentOutRay/Docs
GitHub ↗
Get started ↗
Documentation

Your services, from local to live.

OutRay documentation

Products

Tunnels

Getting started

InstallationAuthenticationOpening a Tunnel

Features

Reserved SubdomainsPassword ProtectionCustom DomainsTeams & OrganizationsCI/CD Integration

Integrations

Vite Plugin

Reference

TCP & UDP TunnelsCLI ReferenceArchitecture
Tunnels

Teams & Organizations

Select the workspace that owns your tunnels, telemetry, and secrets.

An OutRay organization is the shared workspace for your team. Its members, API tokens, subscription, and product resources belong to that workspace.

Tunnel reservations and custom domains are shared within an organization. Observability services, Secrets vaults, and Uptime monitors also use the selected organization; switching products does not switch the workspace.

Select an organization in the CLI

Browser login asks you to choose an organization:

outray login
outray whoami

Change the saved selection interactively or by slug:

outray switch
outray switch my-team

Override one tunnel

outray 3000 --org another-team

This uses a browser login that has access to the requested organization and leaves the saved selection unchanged.

API tokens already belong to an organization. Passing --org does not move a token to another workspace; create a token in the intended organization instead.

Multiple tunnels

Use [global].org for a shared default or a tunnel's org field to choose a specific organization:

[global]
org = "my-team"

[tunnel.web]
protocol = "http"
local_port = 3000

[tunnel.api]
protocol = "http"
local_port = 8000
org = "another-team"

The CLI uses your saved browser login for outray start. Confirm that login has access to every configured organization; if a configured organization cannot be found, the current implementation warns and falls back to the active organization.

Membership and automation

Manage invitations and roles in your organization's settings. Some actions, including API token management, are restricted to owners and admins.

For automation, issue a separate scoped token for each integration. Grant only its required permissions and revoke unused credentials. See Authentication and CI/CD integration.

Custom Domains

Connect a hostname you own to an HTTP tunnel.

CI/CD Integration

Authenticate a temporary tunnel in a non-interactive runner.

On this page

Select an organization in the CLIOverride one tunnelMultiple tunnelsMembership and automation