Layer 03 · Cloud

Where it is all written down.

The street decides for itself. The platform is where the decisions are configured, watched and — above all — kept: every level, every kilowatt-hour, every alarm and the measurement that justified each one.

A control room with a video wall and operator consoles

Operations room — installed site

What you do with it

Four jobs, not forty features.

A platform that is used every day is one that answers a handful of recurring questions quickly.

01

Check your inventory

Every luminaire, cabinet and sensor on a map, located by the device itself at installation, with its live state and its group.

iLCS Cloud inventory map showing the locations of lighting devices
02

Change what it does

Groups, profiles, calendars, lighting classes and switching — applied to one point, one stretch or the whole network.

iLCS Cloud light profile editor with a weekly schedule and dimming graph
03

Know what broke

Faults and threshold alarms with position and time, notified to the people on call, with the history behind them.

Inspection of a disconnected wire inside an electrical cabinet
04

Prove the result

Energy and operating hours per point and per hour, period comparisons, and scheduled reports in PDF, Excel or CSV.

iLCS Cloud email reporting the resolution of a digital input alarm
Where it runs

Your data, in a place you chose.

The platform is built as independent services that can run on a public cloud region, on a private cloud or on your own servers. For a public administration, the answer to "where is the data" is usually the first question and the last obstacle — so it is settled before anything else.

Hosted by us

In the country or region you choose, with the network, backup and access controls described on the security page.

On your infrastructure

The same platform, deployed on your servers, for sites where nothing may leave the perimeter.

Both, over time

A pilot hosted with us can be moved in-house later without changing the devices in the field.

Security in detail →
Two service levels

A larger installation usually needs the hardened, multi-zone service with identity-provider integration, extended retention and a documented recovery plan. A small municipality often does not, and should not pay for it.

Essential Data residency in Italy, standard security controls, local user accounts, basic backup. Sized for a network up to a few thousand points.
Enterprise Dedicated network segregation, web application firewall and anti-DDoS, centralised audit logs, granular roles, SSO through your identity provider with MFA, multi-zone recovery, API and authenticated connectors included.

We put the real differences in a table in the offer, including the options that are quoted separately, rather than describing everything as "included".

Design decision

The cloud is not in the control loop.

Everything on this page describes configuration, monitoring and evidence. None of it is required for the lighting to behave correctly tonight — that runs on the nodes and on the cabinet controllers.

An outage is a gap in the data

Not a gap in the service. Measurements are buffered in the field and sent when the link returns.

Maintenance windows are boring

Updating the platform does not mean coordinating with a city about its street lighting.

The exit is part of the design

Standard export formats and an open API mean your history is portable — a contractual point worth writing into the tender.

Ask for a walk-through on a real installation.

Half an hour on a live network, with the map, the alarms and a report generated in front of you — more useful than any list of features.

Book a demonstration