Every screen.
One console.
A display network answers to as many consoles as it has manufacturers. Lima administers all of them from a single console, including the hardware already installed. It runs on the organization's own server under a per-installation license, or as a cloud subscription hosted in Turkey, with nothing to install.
- On-premises: licensed per installation, not per screen per month
- Cloud: a subscription, with nothing to install
Display network
3 makers
All sites
One console across every manufacturer.
Display networks are rarely single-vendor. Screens are procured over several years, from whichever supplier held the contract at the time. Each manufacturer then supplies management software that administers its own brand and nothing else, and operations teams end up running two or three consoles in parallel.
Lima administers all of them from one place. Samsung, LG, and ViewSonic displays appear in the same inventory, take the same content and schedules, and report status in the same format. A PC, a media stick, or a kiosk joins the same way through the Web Player, because any screen that runs a web browser can play. Adding a fourth manufacturer to the network does not add a fourth system to operate.
On an on-premises installation, each display is also controlled in its own manufacturer protocol over the local network: Samsung MDC on port 1515, LG RS232 over LAN on 9761, and ViewSonic CDE on 5000, with no cloud relay in the path. That is how power and input are switched from the console. The cloud edition does not offer device control, because those protocols do not reach a customer network from outside.
No hardware replacement required.
A signage project usually opens with a hardware line nobody budgeted for, because most platforms will only address panels manufactured within the last few years.
Displays play through their built-in browser. LG and ViewSonic panels need only the player address, and Samsung panels receive a small signed Lima app through the display's own menu, so screens already mounted and in service come under management without being replaced. The player is written to the constraints of older panels, and displays that other platforms have dropped from support generally remain in service. In the cloud, a new screen shows a code and is added by typing that code into the console.
The approach has a defined limit. Device control requires a panel that exposes its manufacturer control interface on the network, and a panel too old to run the player falls outside what Lima can administer. We establish both during the site survey, before any commitment is made.
It runs on the systems you already operate.
A platform that does not fit an existing environment adds a second credential set, a second dashboard, and a second backup job before it has delivered anything. The on-premises edition is built to attach to the systems an operations team already runs.
Directory. Staff authenticate against the corporate directory, so there is no second credential set to maintain and no account left open when somebody leaves. Provisioning follows the directory, which means the leaver process you already run is the leaver process for the signage system as well.
Monitoring. Unreachable displays raise alerts through the monitoring platform already in use. Alerts leave as a webhook or a Zabbix trapper push, so faults arrive in the queue an operations team is already watching.
Server. A single container on standard server hardware, running alongside existing workloads. A prepared virtual machine is available on request for environments that standardize on them.
Data. Configuration, media, and reporting sit in one directory, covered by the backup procedures already in place. In the cloud edition, backups are taken nightly by us.
Every screen switches to the same message in one action.
An evacuation is not the moment to open three consoles. In a plant or a multi-floor building the display network already reaches every area that has to be notified, which is what makes single-action takeover worth having.
A predefined message replaces all scheduled content across the network immediately, and the network returns to its normal programming when the message is cleared. The same mechanism covers planned interruptions such as site closures and maintenance windows. On-premises, displays can also be shut down outside operating hours, with the panel darkened while the device remains reachable on the network.
full screen, every site
Somebody will ask what actually played.
Somebody eventually asks whether the notice, the campaign, or the shift board actually appeared on the screens, and without a playback log the answer is an assurance. Every playback is logged instead. Availability and playback are reported over 24 hours, 7 days, or 30 days and exported as CSV, so the answer to that question is a document that can be attached to an invoice, a safety file, or an audit response.
Content that has not played is listed separately. The usual cause is a schedule set outside the site's operating hours, a configuration error that no other part of a signage system reports, because from the platform's point of view nothing has failed.
The operations team decides where Lima runs.
On-premises. A signage console maintains a live channel to hardware on the internal network, and on-premises that channel never leaves it. Device control, content, and reporting data remain on infrastructure the organization owns, directory sign-in and monitoring alerts are available, and the platform continues to operate independently of any supplier relationship, including the termination of one. The license is tied to the installation, and one screen runs without a license in every installation.
Cloud. There is nothing to install or maintain. Each organization signs in to its own workspace on a subscription for a set number of screens and a set term, hosted in Turkey. Content, scheduling, emergency messaging, and reporting work as they do on-premises; device control, directory sign-in, and Zabbix alerting do not, because they depend on reaching the internal network.
We license both editions commercially and discuss terms, screen counts, and duration on contact.
# set the time zone and administrator password cp .env.example .env # start the platform docker compose up -d
After go live, two jobs remain.
Evaluation concentrates on the installation. The ordinary week that follows it is where an operations team spends the next several years, and it deserves the same scrutiny.
Content is the first. It is uploaded once and assigned wherever it is required, with a record of where each file is in use, so the effect of a change is visible before it is made. Files still on air cannot be deleted by accident.
The ticker along the bottom of the screen reserves its own space. Both a flat playlist and a zoned layout resize to fit it, so a running message never covers the content underneath, which is the failure every operator has seen on some other system.
Screens carry tags, so a change can be aimed at every lobby or every production line and the inventory filtered the same way. Video walls are arranged by drag and drop, and sync groups keep several screens playing in step. Where artwork is missing, AI images are generated at the exact resolution of the screens that will show them, at one credit per image.
Status is the second. The console reports which displays are reachable, what each one is playing, and how long any unit has been offline, which is how faults are identified in areas that are not visited daily. A new display joins the network only after somebody approves it.
Evaluate Lima against your own network.
Provide the makes, models, approximate quantity, and locations of your displays. We will arrange a demonstration and set up an evaluation of the edition you intend to run.
- A guided demonstration using simulated displays, with no hardware required
- An evaluation license for your own server, or a 14-day trial workspace in the cloud, set up on request
- Configuration support for the initial displays, whichever manufacturer