Supported Apps And Limitations

This page is the SLC v1 compatibility and non-goal checklist. If a feature is listed as not supported, do not rely on it for private beta usage.

Supported App Shape

SLC v1 supports a narrow app shape:

• Gleam HTTP applications.
• Erlang target, or omitted target which defaults to Erlang.
• Buildable with gleam export erlang-shipment.
• Started with a direct argv command, not a shell script string.
• Reads runtime-provided PORT.
• Binds HTTP traffic on 0.0.0.0:<PORT>.
• Provides a path-only health endpoint returning HTTP 2xx.
• Does not require a BeamUp SDK for basic deploy.

The canonical fixture is Wisp on Mist, but Wisp/Mist is not the product boundary. Mist-direct and other supported Erlang-targeted Gleam HTTP apps are in scope when they satisfy the same build, start, PORT, and health contracts.

Not Supported In SLC v1

BeamUp SLC v1 does not support:

• Managed Postgres, Redis, or first-class database attachment.
• Custom domains.
• Teams, billing, RBAC, SSO setup, audit logs, or enterprise features.
• GitHub auto-deploy or deploy previews.
• Elixir or Phoenix apps.
• Erlang applications that are not Gleam apps.
• JavaScript-targeted Gleam.
• Cloudflare Worker-targeted Gleam.
• Lustre/full-stack hosting.
• Background jobs and cron as first-class app types.
• beamup scale.
• Multiple steady-state runtime nodes per app.
• Multi-region deploys.
• Clustering.
• Private networking.
• Transparent WebSocket/SSE or TCP state migration.
• Hot code upgrades.
• Full remote Observer.
• Process control.
• Tracing.
• Message inspection.
• Process dictionary inspection.
• ETS table inspection.
• Raw erl_crash.dump downloads.
• Compiler-checked runtime env/secret modules generated by BeamUp.
• Connection capacity, uptime, vertical pricing, or fixed build-duration claims.

These are intentional SLC v1 boundaries, not hidden features.

Runtime Configuration Limits

Runtime env vars and secrets are injected as strings. Your app must parse and validate them. BeamUp does not generate type-safe Gleam config modules in SLC v1.

Values are capped at 4,096 bytes and are read at runtime start. Redeploy after changing configuration.

Logs And Crash Artifacts

Runtime logs are retained for seven days or 10,000 entries per deployment, whichever boundary is reached first. Truncation and retention boundaries are shown explicitly.

Raw crash dumps are not available for download in SLC v1.

Long-Lived Connections

Ordinary WebSocket/SSE use must fit the published ingress limits:

• 60-second ALB idle timeout.
• 30-second target deregistration delay.
• Client reconnect handling during deploy or rollback.

BeamUp does not promise no reconnects or state migration.