Devices
Change device settings, send commands, open a Zigbee network for new sensors or set up Modbus equipment. Bulk changes can span several Gateways, with results reported for each one.
Core: manage every Gateway from one place
Core brings your remote Gateways and their devices into one Edge workspace. Check the health of every site, work with devices and automations across the fleet, and add Gateways as you grow.
- Online status follows each Gateway's own reporting interval, so a quiet site stands out.
- Tag Gateways by customer, region or project and filter the fleet by tag.
One workspace for every site
Core runs as part of Edge, so there is no second application to learn. Devices from every registered Gateway appear on the same Devices, Data and Automation pages as local ones, each labelled with the Gateway it belongs to.
What Edge does on each Gateway
Work on any Gateway without going to site
Choose a Gateway, or several, and work as you would locally. Each operation runs on the Gateway you chose, and the result comes back for that Gateway.
Automations
List, create, edit, enable and disable rules on a remote Gateway with the standard automation wizard. The rule runs on that Gateway, not in your browser.
Diagnostics
Check a Gateway’s network status, force a fresh sync, or open a remote terminal session to it when you have the permission to do so.
Only what the Gateway supports
Each Gateway tells Core which operations it accepts, based on its Edge version and configuration. Core sends nothing outside that list, and never raw requests to an arbitrary address.
No inbound access to the site
Every Gateway connects out to Core over an encrypted MQTT connection, and remote work travels over that same connection. Sites do not need an open port or a VPN.
Run Core on a Gateway or on a central server
It is the same software either way. Each site keeps its own Edge, so local recording and rules do not depend on the link to Core.
On a Gateway at a large site
- One Gateway supervises the others on the same site.
- It still monitors its own devices and runs its own dashboards and rules.
- The site gets one login and one place to administer every Gateway.
On a central server
- Run Core on your own server or in the cloud, on Ubuntu Server.
- Look after every site your team or your customers operate.
- Use a hardened self-hosted MQTT broker, or AWS IoT Core.
Add Gateways as the fleet grows
Adding a Gateway takes three steps, one at a time or in a batch. Setup files and tokens identify one Gateway each, so treat them like a password. To back up, restore or upgrade a Gateway from your desktop, use System Manager.
Add the serial
Enter the Gateway’s serial number in Core, for a single Gateway or a batch.
Give it its setup
Download a setup file, or copy a one-time token that expires after a set time. Where you allow it, Gateways can also enrol automatically.
Check it is working
The Gateway connects and registers, and its devices and measurements appear under its name. From then on, Core tracks its health.
Common questions
Do I need Core for a single Gateway?
Do I need Core for a single Gateway?
No. Edge on the Gateway gives you devices, data, dashboards and automation for that site. Core is for looking after several Gateways from one place.
What happens if a site loses its connection?
What happens if a site loses its connection?
The Gateway keeps running Edge, so local recording and rules carry on. Core shows the Gateway as offline once it misses its expected reporting interval, and any health reading it has not received as unknown.
Does Core replace Edge on each Gateway?
Does Core replace Edge on each Gateway?
No. Every Gateway keeps its own Edge. Core brings those Gateways together so you can see and work with them from one place. The operations available on each Gateway depend on its Edge version.
What does Core need on the network?
What does Core need on the network?
Core needs an address the Gateways can reach and an MQTT broker with TLS. Each Gateway connects out to it, so the sites themselves do not need inbound access.
Core pricing
Core is licensed for each Gateway it manages and billed once a year. Every managed Gateway also runs Edge, which is included with an EpiSensor Gateway.
Core fleet management
For each Gateway connected to Core. Volume pricing is applied automatically to larger fleets.
Choose Gateway licences€30per Gateway / month
€360 billed annually
Edge on each Gateway
The software each managed Gateway runs on site. Licences for third-party devices are an Edge choice, separate from Core.
See Edge pricingIncludedon an EpiSensor Gateway
Standalone licence
Install Edge on your own server, a virtual machine or a Raspberry Pi.
€499Once-Off
Prices exclude VAT. Subscriptions are billed once a year. Volume pricing is applied automatically as the fleet grows.
Talk to an engineer about your fleet
Tell us how many sites you look after, where Core should run and who needs access. We will help you work out the setup.