How Kernopy works

Follow one reading from the floor to the screen.

Six steps, all on the equipment you already run. Scroll to watch it happen.

01 / 06 · Edge

Edge plugs in where the machines are.

An industrial gateway reads each controller in its own protocol. One gateway can serve a single machine, a cell of two or three, or a whole floor.

1 device2 to 3 devicesWhole floor
02 / 06 · Cloud

Readings travel up, safely.

Each gateway signs in, fetches its configuration and streams readings live. If the network drops it keeps reading and sends the backlog, in order, when the link returns.

Kernopy cloud, your own servers, or fully air-gapped.

03 / 06 · Core

Core onboards every asset you already have.

Each controller becomes an asset with a name, a class and its own measures. Register 40017 becomes chiller_1.power_kw.

04 / 06 · Spaces

Then maps them into the places they live.

Site, building, floor and zone. Every reading now knows where it comes from and what it sits next to, so telemetry has context.

05 / 06 · Pipelines

Pipelines turn readings into KPIs.

Clean once, combine with the asset and space model, and compute the measures that matter: kW per ton, energy per part, OEE.

06 / 06 · Foundry

Foundry puts it in front of your team.

Every asset, zone and KPI on one live screen, for anyone with access: operators, supervisors, plant managers and the CXO.

One reading, start to finish

Walk through Kernopy.

Scroll to walk the floor. Follow one reading from a machine, through the Edge gateway, into Kernopy and back as a safe change.

EquipmentKernopyStored dataApps and AIAlerts and commandsA reading
01Layer 1 · Data capture

Kernopy EdgePlugs in where the machines are.

A small box on site reads your controllers, meters and sensors. If the internet drops, it keeps every reading and sends them when the link is back.

  • Signs in by itself the first time it is switched on.
  • Gets its setup from the cloud. No site visit needed.
  • Streams live, holds through outages, then catches up.
02Layer 2 · Move, check, store

Live and catch-up intakeTwo ways in. Nothing lost, nothing twice.

Live readings come in as they happen. Held readings come in after an outage. Both land in the same place, in the right order.

  • A live lane for what is happening now.
  • A catch-up lane for what was held back.
  • Repeats are spotted and dropped.
03Layer 2 · Move, check, store

Event pipelineEvery reading, three jobs at once.

Each reading is queued once, then sent three ways together: check it, show it, save it. A slow job never holds up the others.

  • Check: is it inside its limits?
  • Show: push it to every open screen.
  • Save: keep it for history and reports.
04Layer 2 · Move, check, store

Rules, live screens, historyCaught, shown and kept.

Rules spot a limit the moment it is crossed. Open screens update within seconds. Every reading is saved along with the device and room it belongs to.

  • Alerts on limits, trends and readings that go quiet.
  • Live tiles and charts. No refresh button.
  • Full history, kept as long as you need it.
05Layer 2 · Move, check, store

PipelinesClean data without writing code.

Pick a source, add steps, test the result, then run it on new data or on a schedule.

  • Clean: drop spikes, fill short gaps.
  • Roll up: minutes into hours into days.
  • Combine: turn raw readings into the numbers you track.
06Layer 3 · Applications

Platform APIsOne secure door.

Every app, tool and Edge box comes in through the same door. Each request is checked for who is asking and what they are allowed to see.

  • Sign-in and roles checked on every request.
  • Each site only ever sees its own data.
  • The same door for screens, reports and AI.
07Layer 3 · Applications

Core, Spaces, Foundry, StudioFour apps. One set of data.

They all read the same numbers, so a reading means the same thing on every screen.

  • Core: connect devices and set things up.
  • Spaces: give every reading a place, from building to room.
  • Foundry: where plant teams run the site day to day.
  • Studio: build your own screens. Coming soon.
08Layer 3 · Applications

Local and global data productsYour numbers, and how they compare.

Local products run your own sites: dashboards, alerts and daily operations. If you opt in, global products compare you with similar sites, with every name removed.

  • Local: built from your sites only.
  • Global: an anonymous average of similar sites.
  • Opt in or out at any time.
09Layer 3 · Applications

Kernopy AIAsk a question. Get a next step.

Ask in plain words. Kernopy AI knows which room, which unit and who is in it, so each answer comes with a change you can make and what it would save.

  • Answers from your own live and past data.
  • Suggests a change and shows the saving.
  • Nothing changes until a person approves it.
10Back down · Commands

Commands, safelyChanges go down carefully.

A setpoint change is approved in an app, checked at the door, sent to the Edge box and confirmed by the machine. Every step is on record.

  • Requested by a person, with a reason.
  • Checked against limits and permissions.
  • Sent, confirmed by the machine and logged.
11Anywhere

Where it runsCloud, your servers, or fully offline.

The same product in every setup. Pick the one your IT team needs.

  • Cloud: run by us, live in days.
  • Your servers: the same platform in your racks.
  • Fully offline: no outside link at all.
The value it delivers

From existing plant data
to measurable margin.

We work with what you already have. No new sensors required.

  1. 01
    Lower cost baseEnergy, maintenance and scrap fall.
  2. 02
    More margin per lineBetter throughput, quality and yield.
  3. 03
    Less downtimeFailures caught before they stop the line.
Book a demo

That was one reading. See how Kernopy can help your site. Talk to a product expert.