Every screen.
One console.
A display network answers to as many consoles as it has manufacturers. Lima gives it one, including the hardware already installed. Content, scheduling, device control, and playback reporting run on your own server, with no per-screen subscription.
- Deployed on infrastructure you control
- Licensed per installation, not per screen per month
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, and each manufacturer supplies management software that administers its own brand and nothing else. 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, accept the same commands, and report status in the same format. Adding a manufacturer to the network does not add a system to operate.
No hardware replacement required.
A signage project usually opens with a hardware line nobody budgeted for. This one does not.
Nothing is installed on the display. Lima communicates with each unit over the network using the manufacturer's own control interface, so screens already mounted and in service come under management without being replaced or modified.
The player is written to the constraints of older panels rather than current ones. Displays that hosted platforms have dropped from support remain in service, which removes hardware replacement from the cost of the project.
It runs on the systems you already operate.
A platform that does not fit adds a second credential set, a second dashboard, and a second backup job before it has delivered anything. Lima adds none of them.
Directory. Staff authenticate against the corporate directory. No separate credential set to maintain, and no account to remember to close.
Monitoring. Unreachable displays raise alerts through the monitoring platform already in use, rather than a second dashboard nobody watches.
Server. A single container on standard server hardware, alongside existing workloads. No appliance to buy.
Data. Configuration, media, and reporting in one directory, covered by the backup procedures already running.
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 told something, which is why it is worth being able to seize it in one action.
A predefined message replaces all scheduled content across the network immediately, and the network returns to normal programming when it is cleared.
The same mechanism covers planned interruptions: site closures, maintenance windows, and shutdowns outside operating hours, with the panel darkened while the device remains reachable on the network.
full screen, every site
Delivery is evidenced, not asserted.
Somebody eventually asks whether the notice, the campaign, or the shift board actually appeared. Without a log the answer is an assurance.
Every playback is logged. Availability and playback are reported over 24 hours, 7 days, or 30 days and exported for distribution, so the answer is a file rather than a recollection.
Content that has not played is listed separately. It is usually scheduled outside operating hours, a configuration error that is otherwise difficult to detect.
The control channel 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 is a security question before it is a privacy one.
Lima runs inside the boundary. Device control, content, and reporting data remain on infrastructure the organization owns, and the platform continues to operate independently of any supplier relationship.
# 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 looks at installation. Operations lives with the week after, every week, for years.
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.
Status is the second. The console shows which displays are reachable, what each is playing, and how long any unit has been offline. This is how faults are identified in areas that are not visited daily.
Evaluate Lima against your own network.
Provide the makes, models, approximate quantity, and locations of your displays. We will arrange a demonstration and issue an evaluation license.
- A guided demonstration using simulated displays, with no hardware required
- An evaluation license for a proof of concept on your own screens
- Configuration support for the initial displays, whichever manufacturer