Skip to contentOutRay/Docs
GitHub ↗
Get started ↗
Documentation

Your services, from local to live.

OutRay documentation

Products

OutRay documentation

Connect local services, understand application behavior, manage secrets, and communicate availability.

OutRay has four products in one organization workspace. Start with the product that matches your task; you do not need a tunnel to use Observability, Secrets, or Uptime.

Tunnels

Give a local HTTP, TCP, or UDP service a public address for development, demos, and integrations.

Observability

Send application traces, logs, and metrics; investigate requests and configure alerts.

Secrets

Organize encrypted environment values in vaults and inject them into application processes.

Uptime

Check public endpoints, review detected issues, and publish customer-facing status updates.

Start with a task

  • Share a local server: install the CLI and run outray http 3000.
  • Connect application telemetry: create a Send telemetry token and initialize a server SDK.
  • Run an app with managed secrets: create a vault, select an environment, and run outray secrets run -- npm run dev.
  • Monitor a public endpoint: create an HTTP check before choosing what becomes public.

Shared workspace

Organizations and membership determine who can see and manage workspace resources. API tokens give machine clients explicit permissions. Agent can investigate observability evidence without changing your application or workspace.

Keep machine credentials and exported secret values out of browser bundles, source control, and screenshots. The guides use placeholders and server-side configuration; replace them in your own secret provider.

How the products fit together

A development workflow can use a tunnel for incoming webhooks, Observability to inspect the handler, and Secrets to supply its credentials. Uptime separately probes a public endpoint and can feed a status-page component. Telemetry health, monitor state, and public incident publication are different kinds of evidence—not interchangeable claims that a service is healthy.

The existing tunnel CLI reference, protocol guide, SDKs, and framework integrations remain available in the navigation.

Tunnels

Connect a local service to a public HTTP, TCP, or UDP address.

On this page

Start with a taskShared workspaceHow the products fit together