BeamUp Private SLC Docs

private SLC docs

Deploy a supported Gleam HTTP app, then inspect it in the cockpit.

Start here if you have a private beta invitation. The path is intentionally narrow: register once, authenticate the CLI, deploy an Erlang-targeted Gleam HTTP app, then use logs, runtime health, env keys, safe BEAM snapshots, and rollback.

Open quick start Check supported scope

code-gated betaGleam target: Erlangone steady-state runtimeno Dockerfile on the supported path

supported path

$ beamup login

$ beamup init

$ beamup deploy

$ beamup status

live -> https://<app>.beamup.run

The active deployment changes only after the candidate passes health checks. Failed builds, startup failures, port failures, and health failures do not replace a healthy active deployment.

01 / register

Create browser access

Use WorkOS/GitHub from the invitation URL and redeem the one-time beta code only for first registration. Returning login uses the same WorkOS identity without another code.

02 / deploy

Run the CLI loop

Authenticate with beamup login, initialize beamup.toml, verify your app reads PORT, then run beamup deploy.

03 / operate

Use the cockpit

Inspect build logs, runtime logs, health state, env and secret metadata, rollback targets, drain state, and safe BEAM runtime snapshots.

Start

Quick Start

Follow the complete private-beta path from account setup through deploy, logs, configuration, cockpit, and rollback.

Deploy

Deploy Gleam Apps

Prepare an existing Erlang-targeted Gleam HTTP app, package source, and understand activation behavior.

Operate

Runtime Cockpit

See exactly which BEAM runtime snapshot fields are exposed and which Observer-style powers stay out.

Configure

Env Vars And Secrets

Set runtime strings and write-only secrets without returning plaintext values after submit.

Debug

Logs And Debugging

Read build and runtime logs with explicit truncation, retention, and multiline OTP/SASL behavior.

Scope

Supported Apps And Limitations

Confirm SLC v1 boundaries before relying on databases, custom domains, teams, scaling, clustering, or crash dumps.

trust boundary

SLC v1 is narrow on purpose.

BeamUp documents what is implemented or explicitly in the private-beta path. Unsupported features are named as not supported instead of implied through examples.

custom domains: not supported teams and billing: not supported beamup scale: not supported raw crash dumps: not supported