Back to the exact content.
Publications preserve a snapshot. Roll back to the content that was published, even if the editable draft has moved on.
Independent digital signage
Create, schedule and publish from your workspace. See what actually played.
Bring your AI assistant PlannedFor venues and shops in the UK and India
Design & schedule ↗
Publish with control ↗
See the evidence ↗
The picture after “publish”
A file sent isn’t a screen playing. VisionMagic keeps delivery, player state and playback evidence separate, so you can see what needs attention.
| Screen | Delivery | Player state | Latest evidence |
|---|---|---|---|
| Lobby | Received | Playing | Welcome film · completed |
| Reception | Received | Paused | No events since pause |
| Window | Pending | Unknown · offline | Waiting for reconnect |
Received is a delivery acknowledgement. Playback is a separate observation.
From workspace to real space
A considered workflow from the first connection to the last reported play.
Try a screen in your browser or pair the Android player. Give it a name, choose its venue and follow its first playback report.
Upload media, use a template, arrange a playlist or combine widgets in a visual layout. Schedule it for the right place and time.
Review the content and target screens before confirming. Follow delivery and inspect the playback evidence.
Bring your AI assistant · Planned
Connect an MCP-compatible AI app to your VisionMagic workspace. Find screens, prepare content, review a publication and inspect playback evidence from the conversation you already use.
Planned. Not available yet; we will announce it when it is ready.
“Show me which screens need attention.”
Made for the imperfect internet
Cached content keeps playing when the network goes away. The player holds its playback events locally and sends them when it reconnects.
Offline playback needs content already downloaded to the player. Live web pages, streams and external widgets still depend on their source.
The player receives the publication and downloads its media. Delivery is acknowledged separately from playback.
Content cached · playback events reportingPreviously downloaded content continues locally. New playback events wait in the player’s durable queue.
Cached content playing · evidence queued locallyQueued events are reconciled on reconnect. Reports surface known evidence gaps so an incomplete record stays visible.
Connection restored · queued evidence reconciledConfidence is in the details
Behind every display is the work of keeping it right. Your workspace should make that work clearer.
Publications preserve a snapshot. Roll back to the content that was published, even if the editable draft has moved on.
Tenant isolation is enforced in the database. Roles and screen scopes control what each operator can see and change.
Inspect player versions, connectivity and reported device facts across the fleet. Move from a symptom to the individual screen.
Let’s make a little screen magic
Tell us about your screens and we’ll set you up.
Already have a workspace? Sign in