One device, one build, every tier
Beyond the headline features, every Melanite ships with these too — included in every tier, no add-ons, all part of the same single binary. A couple are marked early access: real and running on hardware, but we're still keeping them short.
A zero-effort operator view: drop HMI nodes — slider, button, momentary push-button, display, text display, colour picker — into the graph and they render as a touch widget grid automatically, bidirectional and live, with an alarm strip on top. The fast path before you build a fully custom HTML HMI.
A built-in historian and live trend charts on any node port — recording, retention and downsampling (per-window average, min and max, or every Nth cycle) to an on-device database, with sparkline charts you can embed in your HMI. No external SCADA needed for the basics.
An industrial alarm pattern built in: active conditions surface as badges and toasts, an append-only journal keeps the history, and acknowledgment is first-class — who, when, and hold-until-acknowledged for latching conditions. Alongside it, the device publishes its own real-time performance: latency histograms, two-point jitter, execution time, fieldbus frame errors and clock deviation, live on a scorecard page. Compile errors and faults appear automatically, no extra wiring.
IEC timers (TON, TOF, TP), a stopwatch and time-warp for the real-time loop — plus wall-clock and astronomical nodes: sun and moon position with scene-ready direction outputs, sunrise and sunset, daily windows, moon phase and illumination. Circadian lighting and blinds that follow the sky, not a fixed clock.
One image, every device: a master drives client panels and their attached I/O from a single node graph. Hardware-verified, in early access.
SoftMotion-class, self-commissioning single-axis motion on CiA-402 servo drives, without a per-axis royalty. Hardware-verified on real servos, in early access.
Export a single project or the whole device as a zip — from the settings page or by asking the assistant — and restore it onto another unit. Machine identity, network configuration and secrets are deliberately excluded, so a restore clones the work without cloning the machine. A full restore is staged and applied at boot with an automatic rollback snapshot; the drill has been run on real hardware, including killing it mid-apply.
On-device users and roles with PIN or password login, and a two-tier model (platform roles plus HMI levels) that gates who can operate versus configure — and who may write from the custom HMI. Access is judged by where the request comes from, so the panel in front of you can be free while the network is gated. Paired clients are a separate credential tier with instant revocation, pairing requires physical presence, and each device carries its own cryptographic identity that a paired app pins — so a swapped device is refused, not trusted.
Each project is a self-contained environment — networks, 3D and 2D scenes, devices, variables, assets and logs — that you can create, copy or switch between at runtime, without a restart.
The device speaks the operator's language: a device-wide default that everyone inherits, plus a per-user override any user can set for themselves — no admin involved. It applies everywhere, including the login screen, the setup wizard, the captive portal and your own /device pages, and the built-in assistant answers in your language. Dates and numbers display locally while the stored and transmitted data stays culture-invariant. String coverage is being extended page by page.
Licences verify cryptographically on the device itself — no account, no activation server, no phone-home, because industrial machines are offline by design. A device with no licence runs the full Community tier; a commercial licence removes the 'powered by Melanite' badge. It is an audit clause and a branding tripwire, not DRM that can strand you.
One binary runs every tier — the licence only toggles entitlements, never the feature set.