Digital signage hardware that runs itself.
Signage fails in the quiet hours: a frozen player, a screen left on all night, an update nobody installed. Our displays and players boot into your content, follow a power schedule, reboot themselves daily and accept remote updates.
From your content to every screen.
Content is managed in your CMS — or LUMA AI Studio — and delivered over the network. On the screen, our firmware keeps the player running: it starts the app at boot, switches the screen on and off with opening hours and restarts it once a night.
- ContentYour CMS, a web player or LUMA AI Studio
- FirmwareBoot to app · power schedule · nightly reboot · OTA
- PlayerAndroid board inside the display, or a box over HDMI
- ScreenWall, stretched bar, round, square or touch
The checklist we build to.
- Boots straight into your content or player app
- Scheduled power on/off for opening hours
- One scheduled reboot a day for long-term stability
- Remote updates for content and firmware
- The right shape for the space — standard, stretched, round or square
Where this hardware works.
Common applications by industry, and the setup we would typically build for each. Every project starts from your site, so sizes and parts change with it.
Menu boards that change with the day
Indoor and drive-thru menu boards switch from breakfast to lunch to dinner on their own, and a sold-out item disappears from every screen at once.
- Typical setup
- Wall displays from 43 to 65 inches in portrait or landscape, or an Android box behind existing screens; power schedule and nightly restart set in the firmware.
- What matters here
- Readable from the counter and the car lane, with no frozen screen at rush hour.
Promotions where the decision is made
Screens at end caps, cooler doors and checkouts show promotions and brand campaigns, often sold to suppliers as in-store media.
- Typical setup
- Stretched bar displays on shelves and fixtures, wall displays at checkouts, all managed from one CMS.
- What matters here
- Content scheduled per store and per campaign from one place.
Passenger information at stops and stations
Departure times, platform changes and service alerts on screens at stops, in stations and on board.
- Typical setup
- Stretched bar displays for overhead and on-board positions; e-paper signs where power is limited.
- What matters here
- 24/7 operation that recovers without a site visit.
Waiting rooms that call the next patient
Queue displays call patients by ticket number rather than by name and point them to the right room; between calls they show health information.
- Typical setup
- Wall displays in waiting areas connected to the queue system; touch displays for wayfinding.
- What matters here
- Privacy-friendly content, and a screen that always stays on your app.
Rates and queues in the branch
Exchange and interest rate boards, queue numbers inside the branch, and bright window screens facing the street after hours.
- Typical setup
- Wall displays inside; window-facing displays with a higher-brightness panel and a power schedule.
- What matters here
- Rates updated centrally the moment they change.
Communication on the floor
Production figures, safety messages and shift information on screens at the line and in break areas.
- Typical setup
- Wall displays, or Android boxes on existing TVs, fed from dashboards or a CMS.
- What matters here
- Runs without an IT team on site.
One team, from the board to the software.
A typical rollout stitches together a board vendor, a panel supplier, a firmware contractor and a software team. We design the board, build the display and write the firmware ourselves, then integrate your software — so when something has to change, one team changes it.
-
01 BoardDesigned in-house
RK3568 to RK3588 boards designed in-house — the same boards behind our displays, players and the 6 TOPS AI Box.
-
02 Display and enclosureBuilt in our factory
Panels from 10 to 65 inches, stretched, round and square, assembled with housing and mounting in our factory.
-
03 FirmwareWritten by our team
// ItempApiPub — opening hours setPowerOnTime(ctx, "8", "0", "0", true); setPowerOffTime(ctx, "22", "30", "0", true); // and a restart every night setRebootTime(ctx, "4", "0", true);Our Android build: rooted, with a system API for power schedules, brightness, rotation and kiosk lockdown — no platform signing.
-
04 Software and testingIntegrated and burned in
Your CMS or player app preinstalled, or LUMA AI Studio. Every unit runs a one-to-two-day burn-in before it ships.
Built to your spec.
Standard products ship as they are. For a project, any of these can change — and because the board, display and firmware are ours, the change is made at the source.
- Screen size, shape and brightness
- Housing colour, mounting and your boot logo
- Your player app preinstalled and set to start at boot
- I/O such as RS232, GPIO or PoE on some models
- Firmware features for your rollout, delivered by OTA
- An Android box for displays you already own
Hardware for this job.
Android touch displays
View products 02Stretched, round and battery signage
View products 03Android players and the RK3588 AI Box
View productsAny Android app or web player runs on our devices — your own CMS, or LUMA AI Studio from our family company. Power API
Digital Signage
Can we use our own CMS?
Yes — any Android app or web player runs on our devices.
How do we keep screens stable 24/7?
Continuous operation is supported on every model; we recommend one scheduled reboot a day, set with a single system API call.
Which display suits a shelf, a menu or a brand wall?
A stretched bar display for shelf edges and window strips, a slim-bezel wall display for menus and promotions, and a round or square display for brand interiors. Tell us the space and we will propose a size.
Do we need a separate media player?
No — our displays have the Android board inside. For screens you already own, an Android box plays your content over HDMI.