Vertex Monitoring

Know which screen is failing before your client calls.

A cloud dashboard that gathers the status of every videotron you run. Each Vertex Player reports in, and the devices that need attention climb to the top row by themselves.

Made forOperators running a fleet of videotrons
Runs onCloud web app · NestJS, React 19
Starting from$9.72per device / month
Vertex Monitoring: the dark fleet dashboard with device status tiles

Get the highlights.

  • Failures rise to the top

    The fleet grid is sorted failing first, not by name. The screen that needs you is the first one you see.

    Vertex MonitoringFleet
    Online64/66
    Attention2
    Plays today14,820
  • Licences flagged in time

    A licence that expires within 30 days puts its device on the attention list, long before the screen stops.

    30days of warning before a licence expires
  • Health you can read

    CPU, memory, temperature and connection for every machine, reported by the player itself.

    4health signals per device
  • One screen, many advertisers

    Each advertiser signs in to a separate view and sees only their own campaigns, plays and payments.

    3roles: Platform Admin, Account Admin, Account Viewer

Every videotron you run, on one screen.

Vertex Monitoring collects what each Vertex Player reports, stores it and shows it to the right people. Nothing else in the field has to change.

  1. A fleet grid sorted failing first

    Every device has a tile with its status badge. A device needs attention when it is offline or when its licence expires within 30 days, and it moves up the grid on its own. High CPU or memory changes the order, it never raises a false alarm.

    • Online, Offline and Needs Attention at a glance
    • Status, schedule, transactions and activity per device
    The Vertex Monitoring fleet grid with device tiles
  2. Telemetry sent by the player itself

    Each Vertex Player sends a heartbeat, the freshness of its content and a preview thumbnail of what is on screen. Reports that arrive late and out of order are recognised by their timestamp and set aside, so the dashboard never steps back in time.

    • Heartbeat, now playing and scheduled plays
    • Telemetry kept apart from player commands
    Vertex MonitoringFleet
    Online64/66
    Attention2
    Plays today14,820
  3. Separate access for every advertiser

    One videotron can serve many advertisers. Each sees the full timeline, so they know how busy the screen is, but the names and visuals of other campaigns are masked in the database itself. Payments and deposits of others never appear at all.

    • Device health shared with every advertiser on that screen
    • Play events visible only to the owner of the content
    Schedule · Window 1Today
    Exclusive
    Sharing
    Blocking
    Screensaver
    0006121824
  4. Registry, roles and an audit trail

    The platform admin registers each videotron and grants or revokes access to an account. Account admins add their own read-only viewers. Sign-in uses a one-time password, and every action taken in the cloud is written to an activity log.

    • Permissions checked against the database on every request
    • Grant and revoke access per device

Read the whole fleet in one glance.

A few rules, applied the same way to every device, so the grid means the same thing every morning.

30days before expiry, a licence is flagged
90days of log retention on every plan
3roles, from platform admin to read-only viewer
0connections opened by the cloud to your devices

The cloud listens, it never reaches in.

Vertex Monitoring only receives. Devices push their reports to a single entry point, and the cloud never opens a connection back to a machine in the field. That leaves no door open on your network.

Status is what the device says about itself. If a machine loses power without warning, its last status stays on the grid until a new report arrives. Monitoring is visual: the grid and its badges are where your team looks.

  • Gateway protected with mutual TLS and a shared ingestion secret
  • Reports from unregistered devices are rejected
  • No push alerts today: the dashboard is the alarm
NetworkLine down
ScreenStill airing

Schedule, rates and balance live on the machine at the site.

Made for the people who answer for uptime.

Vertex Monitoring is the watch layer of the Kliktron AOS. Vertex Player airs, Vertex Cloud delivers, Vertex Monitoring tells you how it went.

Fleet

Media owners

Run more than a handful of videotrons and see every one of them from the office, sorted by what needs you.

Field

Operations teams

Know which site to visit before you leave: offline machines, ageing licences and hot hardware are already at the top.

Tenants

Advertisers on shared screens

Give each client a login of their own. They see the screens they air on, their plays and their payments, and nothing that belongs to anyone else.

Priced per device, lower as the fleet grows.

One price per monitored device per month. The tier follows the number of devices you register.

  • BASIC

    1 to 10 devices · 90-day log retention

    $9.72per device / month
    • Fleet dashboard
    • Licence expiry alerts
  • Best seller

    PRO

    11 to 50 devices · 90-day log retention

    $7.50per device / month
    • Separate access per advertiser
    • Audit trail
  • SCALE

    51 to 200 devices · 90-day log retention

    $5.28per device / month
    • API access
    • Uptime reports
  • ENTERPRISE

    More than 200 devices · 90-day log retention

    $4.44per device / month
    • Integration with your NOC
    • SLA follows the contract agreement

Devices are counted from the units registered as active in the current month. Online status comes from the device report, and monitoring is passive. SLA follows the contract agreement.

Prices exclude 11% VAT. US dollar prices are converted from rupiah at Rp 18,000 = $1; invoices are issued in rupiah.

Tech specs.

Application

Type
Cloud web application, fleet dashboard
Backend
NestJS 11, Kysely, PostgreSQL
Interface
React 19, Vite, TanStack Router, TanStack Query
Access
Any modern browser

Telemetry

Source
Vertex Player
Signals
Heartbeat, content freshness, preview thumbnail, schedule, device health
Health
CPU, memory, temperature, connection
Order guard
Older reports than the last one stored are ignored

Status rules

Online
As reported by the device
Needs Attention
Offline, or licence expiring within 30 days
Alerting
Passive, read on the fleet grid
Log retention
90 days on every plan

Security

Ingestion
Push only, mutual TLS at the gateway, secret checked in constant time
Sign-in
One-time password, session token
Roles
Platform Admin · Account Admin · Account Viewer
Data isolation
Enforced in the database queries

Questions, answered.

Not today. Monitoring is passive: devices that need attention move to the top of the fleet grid, with a badge, so your team sees them first when they open the dashboard.

Status is taken from the device report, not guessed from silence. A machine that loses power cannot report, so its last status stays until it sends a new heartbeat.

Videotrons that run Vertex Player. The player sends the telemetry, so there is no extra agent to install on the machine.

Yes. Each advertiser gets an account with its own admin and read-only viewers. They see the occupancy of the screens they use, their own campaigns, plays and payments, and the health of those screens.

Every plan keeps device logs for 90 days, whatever the size of your fleet.

Let’s make it Broadplay,
Anyone,
Anywhere,
Anytime.

See your fleet on one grid in a 30-minute demo.