KSoft EMS cloud operations for fleets that still respect local control.
The public site and the cloud console now share one brand system: the same dark control-room surfaces, teal-led hierarchy, and technical rhythm already established in the local EMS UI.
Controllers online
1,284
Live KSoft EMS endpoints across distributed sites.
History retained
36 mo
Operational telemetry, alarms, and optimization history in one timeline.
Dispatch handoff
<2 s
Cloud decisions handed to field controllers without losing the local fail-safe path.
Cloud Console
Fleet operations without switching visual systems.
Fleet posture
Stable rollout ring
Controllers online
1,284
Live KSoft EMS endpoints across distributed sites.
History retained
36 mo
Operational telemetry, alarms, and optimization history in one timeline.
Dispatch handoff
<2 s
Cloud decisions handed to field controllers without losing the local fail-safe path.
Optimization trace
Strategic, near-term, and reactive signals aligned.
Today
GREEN / PEAK_SHAVING
Alerts
Exceptions worth operator attention
Ljubljana HQ
Forecast confidence degraded
Vienna Demo
Device pairing incomplete
Trieste Port
Upgrade ring paused
Deployment rail
Platform structure
A single frontend split cleanly into a promotional surface and a console surface.
`/` carries the product story and the first impression. `/ui` becomes the operator workspace. Both inherit one token system and one compositional language, so the brand does not reset when a customer signs in.
Fleet command
One operating surface for every KSoft EMS controller.
Commission new sites, review telemetry quality, and trace optimization plans from a single cloud workspace without splitting the brand between marketing and product.
Operational certainty
Cloud insight layered on top of the same local-first control model.
The console stays legible for operators: device health, site exceptions, strategy drift, and rollout status are visible without dashboard noise.
Unified brand
The public site and the console share the same KSoft visual language.
Dark control-room surfaces, teal-led emphasis, restrained magenta tension, and technical micro-typography carry straight from the current on-device web UI.
Operator model
Structured like a control system, not a marketing dashboard.
Onboard fleets with the same EMS vocabulary
Sites, tariffs, device roles, optimization modes, and alarms use the same mental model from controller setup through fleet supervision.
See strategy quality, not just raw telemetry
Cloud views prioritize plan intent, site status, forecast confidence, and exceptions before drilling into the data stream.
Ship changes without losing field safety
Deployment status, rollback posture, and controller reachability are treated as first-class operating signals.
Theme translation
The local EMS design language becomes cloud-native without changing identity.
The existing web UI already set the visual rules: dark slate canvas, soft clay surfaces, teal for live state, magenta for tension, and crisp micro-labels for telemetry. This scaffold carries those rules into a CDN-friendly Astro frontend with Svelte islands and shadcn components.
Delivery target
Static-first for Bunny CDN.
The structure is built to publish as static assets, while keeping clear seams for future API integration, auth wiring, and real console data.
Console route
`/ui` is treated as a real product shell, not a styled placeholder.
The route already includes navigation rail structure, workspace actions, and tabbed operational views using shadcn-svelte components. It is ready for API-backed site lists, auth, and live fleet telemetry.
Shell
Shell
Persistent app header, side rail, and workspace framing for authenticated routes.
Theme
Theme
Shared KSoft tokens translated into Tailwind v4 and shadcn color variables.
Components
Components
Buttons, badges, tabs, separators, cards, and sheet scaffolding via shadcn-svelte.
Deployment
Deployment
Static Astro output prepared for Bunny CDN hosting with Svelte islands where interaction matters.