InterCore
InterCore, a silver aluminium box, seen from the front left: RJ45, USB-A and RS485 inputs on its front, USB-C on its side, a button and a green status light on top.Status lightButtonRJ45 · USB-A · RS485 inUSB-C

InterCore

A box for every sensor

One box. One cable. Any sensor in, any application out.

What is InterCore?

InterCore is the box every sensor plugs into. It powers the sensor over one cable, carries its data to a PoE switch, and hands it to CoreSpace on the host, which puts every device in the same coordinate space and sends the result to whatever runs the show.

Why InterCore?

Why InterCore? · 01

One box per sensor

LiDAR, depth camera, camera, button array, or a module InterKit built for the project: each gets a box of its own. More devices means more boxes, and nothing else changes.

Why InterCore? · 02

One cable

Power and data on the same line. The box takes PoE from the switch and powers the sensor from it; a LiDAR draws 7.7 W, a ToF camera 2.5 W.

Why InterCore? · 03

One coordinate space

Place each box where it is mounted, aim it, and let CoreSpace align the sensors to one another. In the prototype the error falls from 124 mm to 0.82 mm.

Why InterCore? · 04

Any application

Tracks, zone counts and events go out as channels over OSC and WebSocket, in venue metres or a display surface’s 0–1. TouchDesigner, Unreal, Godot, the browser or CoreApp take them as they come.

How it works

One box per sensor. One cable. Every device in one coordinate space, sent to any application.

LiDARRJ45
In · 01 / 05

LiDAR

A LiDAR reads the room as a ring of distances. It plugs into the RJ45 input; InterCore powers it, 7.7 W, and carries the scan.

ToF depth cameraUSB-A
In · 02 / 05

ToF depth camera

A depth camera sees a cone of the room. It plugs into USB-A; the same box powers it, 2.5 W, and carries the depth frames.

CameraUSB-A
In · 03 / 05

Camera

An ordinary camera has no depth. The picture stays on site; only anonymous positions leave the box.

Button arrayRS485
In · 04 / 05

Button array

A 16-key array on RS485, in development at InterKit. It has no position to set, so it goes from plugged in to online in two steps.

InterKit moduleRS485
In · 05 / 05

InterKit module

A small board InterKit builds for one job: a floor pad, a break beam, a knob, an NFC reader, or a relay that switches a light or a prop. It plugs in the same way, one box each, and shows up in CoreSpace as a device with its own values.

How it connects

One cable per box, every box on one switch

Each sensor plugs into an InterCore of its own. Each InterCore runs one network cable to a PoE switch, which powers it and carries its data. The switch connects to the host computer on site, where CoreSpace puts every device in one coordinate space. In the prototype, a 16-port PoE+ switch with a 240 W budget takes 15 boxes, its 16th port up to the host.

One cable per box, every box on one switchInterCorePoE switchHost · CoreSpace

Then, any application

CoreSpace sends it on: tracks, zone counts and events as channels over OSC and WebSocket, to whatever runs the show.

From sensor to application
  1. Sensor
  2. InterCore
  3. PoE switch
  4. CoreSpace host
  5. Applications
TouchDesigner
Out · 01 / 05

TouchDesigner

For example, an interactive floor in a gallery: wherever visitors stand, the pond ripples and the koi swim clear.

TouchDesigner takes it with OSC In. Positions arrive in the floor’s own 0–1, so nothing needs converting.

Unreal
Out · 02 / 05

Unreal

For example, an LED wall in a pop-up store: as someone walks up, the fireflies in the scene gather in front of them.

Unreal’s OSC plugin takes the same channels; the tracks and zone events drive the scene.

Godot
Out · 03 / 05

Godot

For example, a motion game in a science centre: players step left and right in front of the kiosk to catch the falling stars.

Godot connects with WebSocketPeer and gets one JSON message per update.

Web
Out · 04 / 05

Web

For example, a museum’s live floor map: open a browser and see how many people are in each room right now.

Any page takes it with a WebSocket in the browser, one JSON message per update.

CoreApp
Out · 05 / 05

CoreApp

For example, people counting for a shop: how many came in today and which area is busiest, without writing code.

CoreApp, in development, reads the space, its zones and its channels directly and runs ready-made templates on them.

Any sensor in. Any application out. The box in the middle does not change.

360°

Every side

InterCore from the front and left: the RJ45, USB-A and RS485 inputs, the USB-C on the side, the button and the green status light on top.
  1. FrontThree inputs: RJ45, USB-A and RS485.
  2. SideUSB-C, for firmware and outside power.
  3. BackOne PoE output: power comes in on it, data goes out on it.
  4. TopThe light and the button at the front, clear of the vents.

Meet InterCore

One box, four things to know.

Three inputs
01

Three inputs

RJ45, USB-A and RS485 on the front, so a sensor plugs in on whatever it speaks: a LiDAR on Ethernet, a depth camera on USB, a button array on RS485. One device per box.

RJ45 · USB-A · RS485

One output
02

One output

One network cable from the back to the PoE switch. Power comes in on it and data goes out on it, and the box powers the sensor from it.

RJ45 · PoE 802.3af

USB-C on the side
03

USB-C on the side

For updating the firmware, and for powering the box from an adapter where there is no PoE.

Firmware · Power

Button and light
04

Button and light

On top at the front, clear of the vents. The light says where the box is in the flow. A short press finds the box in CoreSpace; held for five seconds, it returns to factory settings.

Press: locate · Hold 5 s: reset

Works with the sensors you use

InterCore is not a sensor. It is what a sensor plugs into, so a project brings the sensors it needs.

Sensors you bring

  • LiDAR
    LiDAR

    Reads the room as a ring of distances. 7.7 W over the cable.

    Use it for: Floor projections, zone counts, where people walk

  • ToF depth camera
    ToF depth camera

    Sees a cone of the room, in depth. 2.5 W.

    Use it for: Interactive walls and tables, reach and touch

  • Camera
    Camera

    An ordinary camera. The picture stays on site; only anonymous positions leave.

    Use it for: Counting people in a shop or a hall

From InterKit · In development

  • Button arrayIn development
    Button array

    16 keys. No position to set.

    Use it for: Kiosks, quiz and game stations

  • InterKit moduleIn development
    InterKit module

    A small board InterKit builds for one job: it reads a sensor, or switches something, and plugs into InterCore like any sensor.

    Use it for: For example floor pads, break beams, knobs and faders, NFC readers, relays for lights and props

Where it goes

Any sensor on one side, any application on the other. The box and CoreSpace between them stay the same.

  • TouchDesignerOSC In
  • UnrealOSC plugin
  • GodotWebSocketPeer
  • WebWebSocket
  • CoreAppChannels and the venueIn development

Protocols

  • OSC
  • WebSocket
  • TCPPlanned
  • MQTTPlanned
  • HTTP webhookPlanned
  • Art-Net · sACNPlanned
  • MIDIPlanned

Anything that speaks OSC or WebSocket can take the channels today. The list grows with the protocols.

The light says what the box is doing

Seven states. The box and the screen always agree, so a glance at either tells you where a device is in the flow.

The light says what the box is doing

From plugged in to data

Five steps, each a tab in CoreSpace.

  1. 01Plug in

    Sensor into InterCore, InterCore into the switch. About a second later a card marked NEW appears in Devices.

  2. 02AddDevices

    Press Identify to be sure which box it is; the light on the box blinks with it. Then Add to scene.

  3. 03PlaceSpace

    Put it where it is mounted in the 3D venue and aim it. Move it on the axes, or press Auto place.

  4. 04CalibrateCalibrate

    With two or more sensors, one person walks through the overlap and the system aligns them. In the prototype the error falls from 124 mm to 0.82 mm.

  5. 05SendConnect · Live

    Choose the application and the channels. Go live, and the tracking is on its way.

A device with no position of its own, such as a button array, goes straight from Add to Send.

Tech specs

The prototype’s specification. What is marked to be confirmed is settled before production.

Inputs

RJ45, USB-A and RS485, on the front. One device per box.

A LiDAR on RJ45, a depth or ordinary camera on USB-A, the button array and InterKit modules on RS485.

Output

One RJ45 on the back, to the PoE switch. Power and data on the one cable.

Power

Powered over PoE, 802.3af in the prototype, and powers its sensor: a LiDAR draws 7.7 W, a ToF depth camera 2.5 W.

External power over USB-C: voltage and wattageTo be confirmed

USB-C

On the side, for firmware updates and external power.

Status light

RGB, at the front of the top. Seven states, always the same as the light shown in CoreSpace.

Button

One, at the front of the top. Press: find this box in CoreSpace, which flashes it white and selects it. Hold for 5 seconds: factory reset.

Enclosure

Anodised aluminium, in design.

Dimensions and weightTo be confirmed

Mounting

How it mountsTo be confirmed

Environment

Operating temperature and humidityTo be confirmed

Certification

CertificationsTo be confirmed

Switch

In the prototype, a 16-port PoE+ switch with a 240 W PoE budget: 15 InterCores, the 16th port up to the host.

Own switch or recommended modelsTo be confirmed

Host and CoreSpace

Out: OSC and WebSocket; TCP, MQTT and HTTP webhook planned.

Operating system: Windows and macOS under evaluationTo be confirmed

InterCores per host: in prototype testingTo be confirmed

Where it stands

Prototype · 2026

The CoreSpace prototype runs the whole flow on simulated data; no real hardware is connected yet. The first version makes it middleware a venue can run. No dates are set.

  1. NowP0 · Prototype
    • The five tabs
    • The switch’s front panel
    • 3D placement and calibration
    • Connect, as a demonstration
  2. P1 · First version
    • Device discovery and adoption
    • Venue building and placement
    • Multi-sensor calibration
    • Tracks and zone channels
    • OSC and WebSocket out
  3. P2 · Extension
    • Counting lines and zone events
    • Ordinary cameras, privacy mode
    • Button arrays, InterKit modules
    • Record, replay, simulate
    • TCP, MQTT, HTTP
  4. P3 · Advanced
    • Art-Net, sACN, MIDI
    • Projection calibration on displays
    • Several hosts together

Around the box

  • InterCore

    The hardware: one box for every device.

    Prototype · 2026
  • CoreSpace

    The software on the host: devices, venue, calibration and the channels out.

    Prototype
  • CoreApp

    Ready-made application templates, such as people counting with reports, running on the channels CoreSpace sends.

    In development
  • InterKit

    More devices made for InterCore: a 16-key button array, and modules built for a project, such as floor pads, break beams, NFC readers and relays.

    In development

Questions

Is InterCore a sensor?

No. It is the box a sensor plugs into: it adapts the sensor’s interface, powers it, and carries its data and its power over one network cable to a PoE switch. Which sensor to use is the project’s choice.

How many devices does one InterCore take?

One. A box for every sensor: more devices, more boxes, and nothing else changes. The button array and InterKit modules work the same way.

How soon does it work once it is plugged in?

In the prototype, about a second after you plug it in, a card marked NEW appears in CoreSpace’s Devices tab. Press Identify to see which box it is, its light flashing with it, add it to the space, place it and calibrate, and it starts sending.

Do I need to write code?

Plugging in, adding, placing, calibrating and choosing what goes out all happen in CoreSpace, without code. For TouchDesigner, Unreal, Godot or a web page, CoreSpace fills in the protocol, the port and an example; what the application does with the data is up to whoever builds it. Ready-made functions such as people counting will come as CoreApp templates, in development.

How many InterCores can one host take?

That is being tested in the prototype, and the release will say. In the prototype, a 16-port PoE+ switch with a 240 W PoE budget takes 15 InterCores, its 16th port up to the host.

Does it work without a PoE switch?

Its data goes over the network, so it always needs one. Without PoE it can take external power through the USB-C on its side, its specification to be confirmed; a PoE switch is recommended, power and data on one cable.

How do several sensors line up?

Place each sensor in CoreSpace where it is installed, then have one person walk through where the sensors overlap, and the system aligns them. In the prototype’s demonstration the error fell from 124 mm to 0.82 mm.

Does an ordinary camera send out its images?

The aim is to send only anonymous coordinates, never images. Whether people are detected on InterCore or on the host is still being decided; the release will say.

What computer and operating system does the host need?

To be confirmed. Windows and macOS are both being evaluated.

When can I buy it, and for how much?

InterCore is a prototype, and timing and pricing are not announced. If you would like to use it in your venue or project, write to us about a pilot.

Build the first installations with us

InterCore is for studios and integrators who build their own sensing. If that is you, write to us about a pilot: the venue, the sensors you use, what the application needs.

[email protected]