Offline-safe edge
A stale cloud schedule triggers a local fallback mode, peak shaving or balancing, or a safe hold. Telemetry is buffered and flushed on reconnect.
Myto / Platform
An edge controller on site, forecasting and optimisation in the cloud, and one model of the energy system joining them. Vendor-neutral below, auditable above.
Edge + Cloud
The edge runs a one-second read–decide–write cycle and never depends on the cloud to stay safe. The cloud forecasts, optimises and sends schedules down. If the link drops, the edge falls back to a local mode and buffers telemetry until it returns.
A stale cloud schedule triggers a local fallback mode, peak shaving or balancing, or a safe hold. Telemetry is buffered and flushed on reconnect.
A Modbus TCP server and an IEC 60870-5-104 outstation expose the site to an existing SCADA or an SLDC-style telemetry link.
Containerised services on your own infrastructure or ours. Where the data lives is a deployment decision you make.
Integrations
Vendor-neutral means nothing without a list. This one is kept to what the edge actually speaks today.
Prediction
We use the word AI sparingly. Where a model makes a decision we say what kind of model it is, how it was tested, and whether it ships today.
An ensemble price forecast in the cloud with Indian calendar effects; persistence and similar-day predictors for load and generation at the edge.
AvailableRule-based fault detection on live channels, raised as alarms. Learned anomaly detection is by design.
AvailableStorage schedules and bid drafts produced in shadow mode, for an operator to review before anything is armed.
By designForecast models are backtested on held-out history, promoted when they measure better, and rolled back when they do not.
AvailableGradient-boosted and neural forecasting models have an interface in the platform but are not in production. We publish no forecast accuracy figures until they are measured on a deployment.
Optimisation
The optimiser turns forecasts, tariffs, prices and constraints into a storage schedule, and prices every cycle in degradation before committing to it.
A per-kWh degradation cost from the asset profile sits inside the objective, so a cycle is only spent when it earns more than it wears.
A floor below which the battery holds its energy rather than selling it cheaply.
A horizon schedule for flexible load and storage, activated to the edge as a schedule to follow.
A built-in dynamic-programming solver by default, with an optional mathematical-programming solver for larger problems.
Optimiser output runs in shadow mode. It becomes a physical setpoint only after live control is armed at the edge.
Digital twin
A storage asset modelled at 15-minute resolution, run against real history before a rupee is committed.
You provide
You get back
Technical credibility
For the engineer who will be asked to sign off on it.
Go services for the API, edge agent and workers. PostgreSQL as the system of record. A web operator console. Containerised deployment.
One-second input, process and output cycle at the edge. Cloud schedules are followed only inside the local envelope, through the dispatch gate.
Control and market actions written to audit tables. Compliance runs checksummed. Backtests replayed without look-ahead leakage.
Meter, storage, charger and thermal simulators, so control logic is exercised before it meets real plant.
Session and API-key authentication, organisation-level roles, and separate privileges for market functions.
Developed in India. No dependence on a foreign closed-source control plane.
Architecture, protocol mapping for your equipment, and the control modes we would start in. For engineers, not for a sales deck.