ENTHJA
Request a demo

Platform

Inputs, engine, outputs. Inside your perimeter.

Canvas takes in what your systems and sensing produce, resolves it into one picture, and sends dashboards, tickets and responses out. It runs where you decide.

Request a demo

Architecture

One engine between what you have and what you do.

Sensing inputs and operational systems on the left. Canvas in the centre. The ways your people work with it on the right.

Canvas architectureSensing inputs and operational systems feed Canvas. Inside Canvas, the Integration Runtime connects them, the Data and Context Engine resolves them into one picture, and Automations and SOPs act on it. Canvas outputs dashboards and reports, tickets and tasks, alarms with video and maps, chat channels and Power BI.SENSING INPUTS AND SYSTEMSCANVASOUTPUTSVISION INPUTSCorvus, Vailient Plates, FacesCAMERAS AND RECORDERSMilestone XProtect, Luxriot EVO, Dahuarecorders, ONVIF, IMOUBUILDING AND INDUSTRIALBACnet, Edwards fire panels, Dahua accesscontrol, Advantech ADAM, MQTTBUSINESS SYSTEMSPeak Accounting, Huawei eSupplier, SQLdatabases, Excel and CSV foldersSENSORS AND LOCATIONRuhr flood sensors, ThaiWater, Tuya,BlueIOT, generic RESTCanvasThe system of operationsIntegration RuntimeConnects a system, sandboxedData and Context EngineResolves one picture from manyAutomations and SOPsStarts the right procedureDASHBOARDS AND REPORTSBuilt from a sentence, sent on a scheduleTICKETS AND TASKSAssigned, tracked and closedALARMS, VIDEO AND MAPSPlaced on the map, camera beside themCHAT CHANNELSLINE, Telegram, Microsoft TeamsPOWER BI (OUTBOUND)Canvas data, read from Power BI

Only integrations that exist today are shown.

Inside Canvas

Three parts do the work.

  • Integration Runtime

    Each connected system runs in its own sandbox, so adding or changing one cannot disturb the others.

  • Data and Context Engine

    Resolves what the connected systems report into one model of places, assets, vehicles and people.

  • Automations and SOPs

    Acts on that model: opens tickets, starts procedures, notifies people, and waits for approval where you want it.

Deployment

Install it where your operation is.

Your integrator chooses the shape that fits the site. All of them keep the customer's copy of operational truth inside the customer's own perimeter.

Canvas deployment optionsCanvas runs as a Windows installer or in Docker on Linux, inside the customer perimeter. It can also run in the cloud, or as a hybrid with sensors on site and dashboards in the cloud.INSIDE YOUR PERIMETERWINDOWS INSTALLEROne installerYour integrator deploys it withouta development environment.DOCKER ON LINUXServer-classFor servers and larger sites.YOUR SYSTEMS, ON SITECameras, recorders, building systems, sensors, business systems.Canvas holds its copy of operational truth here.HybridCLOUDHosted CanvasRun entirely in the cloud, or keepsensors on site and dashboards inthe cloud.

Four ways to run Canvas.

  • Windows installer

    A single installer your integrator can run without a development environment.

  • Docker on Linux

    For server-class environments and larger sites.

  • Cloud

    Hosted Canvas for operations that do not need to keep systems on site.

  • Hybrid

    Sensors and systems on site, dashboards in the cloud.

Talk through your site with an integrator who has done it.

Request a demoTrust center