Beam Publish

Publish localhost without an inbound origin port.

With an already installed and enrolled agent, the reviewed Beta publish command can request a public HTTPS URL.

Setup neededLinux reference path

Review activation status Inspect the Beta reference

Current first-use boundary

Public activation: Installer distribution is live; publishing requires an installed and enrolled agent
Runtime command after install and enrollment: aasetup publish localhost:3000
Issued hostname pattern: https://<slug>.beam.arivaran.dev

The installed-agent runtime path passed 20 of 20 checks on 2026-07-17. First-use activation is still unavailable while the public distribution hostname does not resolve.

The runtime path starts after activation.

Setup is unavailable. The publish command and hostname remain Beta references for an already installed and enrolled agent.

Beam Publish activation boundary

Setup needed

Setup is unavailable. The publish command and hostname remain Beta references for an already installed and enrolled agent.

Step 1: Resolve public activation
Installed and enrolled agent
Step 2: Run the Beta publish action
Reference command after the prerequisite
aasetup publish localhost:3000
Step 3: Receive an issued hostname
Reference pattern after a successful publish
https://<slug>.beam.arivaran.dev

Resolve public activation
Current status
Setup needed
Required before publishing
Installed and enrolled agent
Run the Beta publish action
Reference command after the prerequisite
aasetup publish localhost:3000
Receive an issued hostname
Reference pattern after a successful publish
https://<slug>.beam.arivaran.dev

Visitor route

Public URL to the local HTTP target

Origin network

No inbound origin port for the publish path

Separate reachability from content visibility.

The outbound origin path, the planned SNI route, and the authenticated edge path have different evidence and status.

The origin stays zero inbound.

After an agent is installed and enrolled, it dials outward. A public visitor does not connect to an inbound origin port.

Provider-blind Publish is not live yet.

Provider-blind Publish is limited to the planned SNI-routing path with no relay-side authentication; live HTTP Publish acceptance for that path is still pending.

Current gateway-terminated HTTP Publish and every relay-side authenticated edge path expose HTTP to the relay and are not provider-blind.

Review the current Beam evidence

Choose by operating boundary.

Compare public reach, setup, origin networking, TLS handling, private routing, and lifecycle without a winner score.

Compare publish paths