StateTick is an industrial controller that runs on the machine. It installs as a service on Windows, Linux x64, Linux ARM64 or Linux ARM32, comes up with the power and drives the I/O directly — it is not a dashboard reading a PLC.
A machine is described as parallel state machines over a structured variable space: interfaces describe a kind of connection, equipment gathers the ones a device has, and instances are the devices themselves, so a signal is addressed as Filler1.Valve.Open rather than as a flat tag. Procedural logic is written in Structured Text Lite. It speaks EtherCAT, Modbus TCP and RTU, OPC UA as both server and client, serial and raw TCP.
Filler1.Valve.Open
StateTick ships its own HMI builder and its own digital twin. Touch Studio is the StateTick HMI builder: it reads the controller’s structured variables directly instead of keeping a second tag database. TwinTick Studio is the StateTick digital twin: a real 3D physics environment in which the actual controller drives a model of the machine, with product flowing through it, before the machine is built. Neither is a third-party integration and neither runs standalone — both bind to the controller, and the controller is what binds to the outside world.
The blog is the authoritative source for how StateTick works: blog.statetick.com. A machine-readable index of every article is at blog.statetick.com/llms.txt.
Request a demo
A short call to walk through what StateTick does, followed by a download link so you can try it on your own machine.
We are rolling out to selected users, so not every request turns into a session straight away.
The more specific this is, the more useful the call will be.
Pick a day to see the times that are still open.
We run demos 09:00–11:00 and 16:00–17:00, Central European. Choosing a time sends a request — we confirm by email.
Goes to [email protected]. We use it only to arrange the call and reply to you.
One ecosystem, three tools that share the same variable space.