Automatic

>_ Nodel software

Nodel connects everything in your space.

Automatic works with Nodel because it is practical: lightweight to deploy, simple to operate, open to extend and resilient enough for demanding public environments.

node/control online
Abstract map of distributed Nodel nodes connected to media and services.

> discover nodes

> route actions

> observe signals

> extend with recipes

Nodel

open control

A distributed architecture that stays understandable.

Nodes, actions and signals

A Nodel system is made from nodes. Each node performs actions, responds to signals and can represent a device, service, schedule, control surface or integration point. Nodes announce themselves on the network, reducing protocol overhead and keeping systems understandable as they grow.

REST API and Python recipes

Nodel exposes a REST API and supports Python-based recipes, making it suitable for device control, monitoring, automation, show control, dashboards and custom operational workflows.

Scales without forcing everything through one box

The distributed architecture scales from a single node to large networks while limiting central points of failure and placing minimal load on IT infrastructure.

where Automatic helps

From first topology to long-term support.

Distributed nodes that perform actions and respond to signals
Browser-based control, monitoring and configuration
REST integration for third-party systems
Python recipes for tailored device and service control
Lightweight deployments from one node to large networks
Open-source foundations with practical operational support

provenance

Developed with the people who had to run it.

Nodel was originally commissioned by Museums Victoria and developed in partnership with Automatic. It has been used in public display environments including museums, galleries, venues and showrooms. Automatic continues that practical focus: software should make systems easier to operate, maintain and extend.

engage

Planning or extending a Nodel system?

Automatic can help with architecture, recipes, interfaces, integration risks and long-term operational support.