Once Screenly is reachable from code, a handful of uses come up again and again. Most teams reach for one or two of them, not all.
Automate the busywork
Provisioning screens, pushing content, changing schedules across a whole fleet: the repetitive work no one should do by hand a hundred times over can run from a script or a pipeline instead.
Weave it into your own systems
Signage can become part of the software you already run, rather than a separate place to visit. You can extend Screenly into your own tools, and build integrations with the data and services around it on your own terms.
Build your own apps
When the App Store does not have what you need, you can build your own apps and run them on Screenly like any other content.
Build your own product on it
Because the dashboard is only one client of the API, you can put a different one in its place: your own front-end, under your own branding, with Screenly running underneath. This is how managed service providers and partners run signage for many clients from a place that is theirs, and your users may never know Screenly is there.
These are shapes, not limits. The rest of this group is about the tools that reach the API: the CLI for scripting, the MCP server for AI assistants, predicates for live data, and building apps for custom content.