Lima
The control channel to your displays stays inside your network.
A signage console maintains a live channel to hardware on the internal network. A hosted platform holds that channel from outside the perimeter, which makes it a security question some time before it becomes a privacy one. Lima runs on the organization's own server, next to the displays it controls.
Every release arrives as a single file.
Each release of Lima is delivered as one archive carrying the application image and its installation files. Nothing is pulled from a registry or an outside server during installation, so it proceeds the same way on a network with restricted internet access.
The installer asks for a port and an administrator password, starts the application, and prints its address. Lima runs as a single container on standard server hardware, alongside existing workloads.
# load the release archive, nothing is pulled zcat lima-<version>.tar.gz | docker load # the installer asks for a port and a password ./install.sh
The organization decides who reaches what.
Lima uses the organization's identity infrastructure and checks authorization on the server for every request.
Directory sign-in. Staff sign in through the organization's directory. A user arriving through LDAP for the first time has no access at all until an administrator assigns a role.
Three roles. Administrators reach everything, editors reach content and device control, and viewers read only. Revoking a role cuts off that user's active session immediately.
Action logs and backup. Actions are logged. Configuration, media, and reporting data sit in one directory, covered by the backup procedures already in place.
A license per installation. The license is tied to the installation, with no monthly fee per screen. Time-limited licenses are issued for evaluation.
Commands to the displays never leave the network.
Lima talks to each display over the local network, through the manufacturer's own control interface. The command that powers a display, switches its input, or changes what it plays travels directly from the server to the panel, and no cloud relay sits in the path. A new display joins the network only after an administrator approves it, and each approved display holds its own key.
Device control, content, and reporting data remain on infrastructure the organization owns, and the platform keeps operating if the supplier relationship ends. For an organization that prefers not to run a server, Lima is also offered as a cloud subscription hosted in Turkey. It covers content, scheduling, and reporting, without device control, directory sign-in, or Zabbix, since none of those reach the internal network from outside.
Evaluate Lima on your own infrastructure.
Tell us about your server estate and the makes, models, and quantities of your displays. You can try Lima in your own environment under an evaluation license.
Request a demo