Compatibility
What Nodark connects to
Nodark reads your CMS through its API. That means support is per-platform, and it is honest to say so. Two platforms are supported and running in production today. Others are not, and we would rather tell you that now than discover it in week two. If your platform is on the “not yet” list, there is a path, and it is described below.
Supported today
In production
Scala
In production, monitoring a 9,000-screen estate across Ireland, the UK and Europe.
In production
OnSign / DAMOC
In production on the same estate, alongside Scala, in one view.
Running both at once is the normal case, not the exception. Screens from either platform appear in the same list, with the same incident handling.
Not supported yet
- BrightSign
- Xibo
- Yodeck
- SignageLive
BrightSign, Xibo, Yodeck and SignageLive are not supported today. No connector has been built for any of them. Nothing on this page should be read as universal CMS support.
What it takes to add one
The requirement is small but specific. Nodark needs an API that returns:
- 01a list of players
- 02a stable identifier per player
- 03a last check-in time or an online/offline state
- 04ideally a site or location field
Most CMS platforms expose this. If yours does, a connector is a scoped piece of work, and we will quote it and give you a date before you commit to anything. If yours does not expose last check-in, Nodark cannot tell a dark screen from a healthy one, and we will tell you that instead of taking the work.
If your platform isn’t listed: send us the API documentation. You will get a straight yes, no, or “yes and here is what it costs” — usually within a few days.