Gluon

Deploy and scale the app your template defines

Gluon is the control-plane story for Unified Field: register applications, coordinate environments and credentials, and promote the same Leptos app into deployable units, worker pools, and provider targets so Boson and Photon have somewhere real to run.

Why this family exists

Shipping a template locally is not the same as operating it. Gluon exists so setup, agents, applications, and delivery share one deployment model—guided first-run flows, consistent packaging and health hooks, and automation that keeps sensitive work out of ad hoc scripts while staying observable.

Where it lands

Gluon maps the composed Unified Field app into deployable units and provider targets so background work (Boson) and realtime (Photon) scale on the same delivery spine as the UI.

The control plane coordinates environments, credentials, and platform services as teams approach go-live. Agents cover remote execution paths; Applications register and run with lifecycle hooks across targets; CI/CD templates align build, test, and promote with the same deployment assumptions; the Setup Wizard connects local development to control-plane expectations without losing context. Gluon is still maturing as a standalone crate—the product surface is what the template and marketing stack describe today.

In the workspace

Gluon maps the composed Unified Field app into deployable units and provider targets so background work (Boson) and realtime (Photon) scale on the same delivery spine as the UI.

← Platform overview