products::litlaunch :: streamlit runtime layer

Runtime governance for Streamlit apps

LitLaunch is the operational launch layer for serious Streamlit applications: explicit backend ownership, health checks, browser/app-window strategy, graceful shutdown, diagnostics, and runtime posture visibility without replacing Streamlit.

RC::RUNTIME_LAYER

Problem

Streamlit apps often accumulate shell scripts, browser-launch glue, and inconsistent local runtime behavior.
Packaged or internal tools need repeatable launch profiles, runtime posture, diagnostics, and clean shutdown behavior.
Teams need operational visibility without pretending a launcher secures the application.

Key Features

CLI and Python APIs that construct Streamlit backend commands explicitly and own only the backend process they start.
Profiles for repeatable launch behavior across local tools, internal dashboards, AI utilities, and packaged apps.
Browser capability detection, managed browser-window flows, Chromium app-mode support, and fallback behavior where available.
Graceful shutdown hooks, runtime event trails, inspect/report diagnostics, support bundles, and generated support pages.
Trust modes, loopback-first defaults, runtime exposure diagnostics, and transport posture reporting for intentional deployments.

Philosophy

Infrastructure, not magic orchestration: LitLaunch owns the backend process it starts and observes browser windows without pretending to control the browser.
Commands are argument tuples, not shell strings; diagnostics are sanitized and practical.
Streamlit remains Streamlit. LitLaunch supplies the runtime discipline around it without claiming to secure the application.

release::download

Release path routes through GitHub

Release and download information stays tied to the product repository so source, docs, artifacts, and support context remain close to the code that owns them.

./github_releases

Roadmap

Keep the release surface focused on runtime governance, diagnostics, profiles, launch discipline, and support artifacts.
Keep diagnostics and support artifacts calm, concise, and app-owned.
Use LitLaunch as the runtime foundation for LatticeFoundry local-first applications where it fits.

Docs Boundary

Product repositories remain the documentation source of truth.
LatticeFoundry will render and style product docs without duplicating source content.
Repository-backed rendering will keep the public reading surface aligned with release ownership.