Klorad Platform

One platform for every twin you run.

Klorad connects a place, its systems and the people who run it into one live picture. One core runs every Klorad Solution, and your systems stay where they are.

Map2D GIS: points, lines, parcelsSurveyPhotogrammetry and LiDAR point cloudsBuildingsBIM, georeferenced to the surveyLive dataSensors and systems over IoT networksRulesAlert rules across every systemActionAuthorised commands back to the field
01How it works

A twin senses, thinks and acts.

Every Klorad twin runs the same loop between the place and its model, and a person decides every action.

PHYSICAL PLACEDIGITAL TWINSenseActThink
02Worlds

One twin, a view for every team.

A World is a team's own view of the site, on the same live twin. Four things define it.

  • Scope

    Which objects and layers its members see, filtered on the server.

  • Capabilities

    Which actions they may take and which modules they get.

  • Members

    The users, teams or roles allowed in. Nobody, until named.

  • Presentation

    Theme, camera, layers, and whether it is public or signed in.

03Built in

Everything a twin needs, built in.

The same on every site; each Solution adds what its domain needs.

SeeEvery system's readings on one live twin, in 3D and in plan.
DecideAlerts by rule as Alarm, Warning or Notice, escalated when unanswered.
ActWork orders, incidents with procedures, and commands checked against each role.
RunA view per team, single sign on, reports and an audit log.
04Licensing

A licence for each site.

The twin you hand over keeps working for as long as the asset does. Implementation is scoped as its own project, and support levels are agreed for each site.

AI-generated scene: three engineers around printed site plans on a meeting table.
  • Editions that grow with your site

    Start with what the site needs. Add modules as it grows.

  • Klorad Cloud, Dedicated or Sovereign

    Our cloud, a dedicated environment, or your own servers.

  • Need a module we do not have?

    We build it and maintain it.

05The SDK

Extend your twin in code.

A TypeScript SDK on the same system model, rendered by three.js and OpenLayers today. Package access for the developers of our customers and partners.

import { createScene } from "@klorad/api/world";

const scene = createScene({
  coordinateSystem: { origin: { lat: 40.6401, lon: 22.9444 } },
});

scene.add({
  name: "Pump 07",
  position: { east: 12, north: -4 },
  geometry: { kind: "model", uri: "/models/pump.glb" },
  correspondence: "shadow",
  binding: { source: "scada", entity: "pump-07" },
});
A georeferenced scene and a Digital Shadow, in the Klorad SDK.
06Architecture

Built on a published system model.

Three layers with one rule: the World layer owns meaning, and Access and Integration depend on it, never the reverse.

  • World

    The scene, its objects, their state and the rules that change them.

  • Access

    Who reaches the twin, through which device, with which entitlement.

  • Integration

    Sensors, systems, location services and AI, coupled to the twin through connectors.

Talk to the people who built it.

A technical briefing on the architecture, the connectors and where your systems plug in.