Scala — one of the most widely deployed digital signage CMS platforms in the world — was sold to Swedish software company Vertiseit for approximately $28 million. If you're running digital signage infrastructure on any Stratacache-family platform, that headline matters. But it doesn't mean the same thing depending on which platform you're on.

TL;DR

• Scala is a digital signage CMS. Vertiseit bought it and has explicitly stated a plan to move it toward a SaaS-first, device-agnostic model. If you're a Scala customer, your CMS is under new ownership with a product direction you didn't choose.
• ActiVia is Stratacache's QSR-focused CMS platform — it was not sold to Vertiseit. It remains with a Stratacache organization that just divested its flagship product under significant financial pressure. ActiVia's roadmap and support investment are tied directly to what Stratacache does next.
• Both Scala and ActiVia include device monitoring as part of their CMS feature sets. Neither is a dedicated device management platform. That distinction is invisible when everything is working and becomes operationally critical when the vendor behind the platform is in flux.
• Esper adds a dedicated device infrastructure layer underneath your existing signage platform — independent of Scala's new owner, independent of Stratacache's financial situation, independent of either platform's roadmap. Your hardware stays. Your content keeps running.
• The 60-to-90-day window is when migration is cleanest. The longer you wait, the more you absorb someone else's decisions.

The CMS Is the Headline. The Device Layer Is the Operational Risk.

Most of the industry coverage on the Scala sale is focused on the CMS — who bought it, what Vertiseit paid, what the product roadmap looks like under new ownership. That's the right conversation for content teams. It's the wrong conversation for IT operations.

Here's what's actually worth understanding before you make any decisions.

Scala is a digital signage CMS platform — it schedules playlists, distributes content to screens, and manages what gets displayed across your fleet. It's been part of the Stratacache family since 2018. Vertiseit bought it in May 2026. Vertiseit's stated plan is to "accelerate Scala's transition toward a modern SaaS-based and device-agnostic offering." Device-agnostic is not a vague term. It means Vertiseit is explicitly moving away from device-specific depth. Whatever device management capability was built into Scala is being deprioritized in favor of platform abstraction.

ActiVia is Stratacache's own QSR-focused CMS — not a separate device management layer, but a full content platform that includes scheduling, device monitoring, and network management built for highly distributed restaurant environments. It was not sold to Vertiseit. It stayed with Stratacache. The problem isn't a change in ownership — it's that the organization behind ActiVia just sold its most valuable and recognized brand under documented financial pressure. The team, the investment, and the roadmap continuity for ActiVia now depend entirely on what Stratacache looks like on the other side of this.

In both cases, the operational risk is the same: the device management capabilities your IT team has been relying on are features of a CMS platform — not dedicated infrastructure. When the vendor behind the platform is under pressure, you find out the difference.

You Didn't Choose This. But You Can Decide What Happens Next.

The architectural problem here predates the acquisition. It's what happens when device management gets bundled into a content platform.

When your CMS vendor also provides your device monitoring, your provisioning tooling, and your remote access, you inherit every decision they make — product pivots, acquisitions, restructurings, roadmap deprioritizations. Not because your hardware changed. Not because your content changed. Because a single platform owned the infrastructure between your devices and the rest of your operations.

For Scala customers: Vertiseit's device-agnostic direction isn't necessarily bad for your content workflows. It is a clear signal that the device management depth in Scala is not where Vertiseit is investing. The product you contracted for will not be the same product in 12 months.

For ActiVia customers: Stratacache hasn't announced anything about ActiVia's future. That silence is its own data point. When a company sells its flagship asset under financial pressure, the products that remain don't automatically get more investment — they get less.

Architectural independence means the platform managing your fleet outlasts any vendor relationship, any acquisition, and any product pivot. That independence has to be built in deliberately — it doesn't happen by default when device management is a feature of your CMS.

What "Same Devices, New Infrastructure Layer" Actually Looks Like

Adding dedicated device management underneath your existing signage platform doesn't require replacing hardware, re-architecting content delivery, or absorbing a major operational disruption.

Esper operates at the OS layer — below your CMS, independent of your content player, independent of your hardware vendor. It doesn't render content, schedule playlists, or touch anything in your existing content workflows. It manages the device running your content platform: OS updates, firmware management, boot behavior, network policy, security posture, and fleet-wide state enforcement.

Your Scala installation keeps running. Your ActiVia installation keeps running. Esper manages the device underneath. A top 10 QSR has already made this transition — same devices, same content platform, dedicated device infrastructure layer added — scoped in weeks, not quarters. Esper's Blueprint model defines device state once and enforces it everywhere, so the 10,001st device migrates in exactly the same time as the first.

For the full picture on how migration is scoped and executed — hardware compatibility, workflow continuity, and what day one actually looks like — [see the migration details here →] [LINK TO LP]

The 60-Day Decision Window

There are three paths from here. For both Scala and ActiVia customers, the window is the same and the paths are the same.

Path one: move now, on your terms. Add a dedicated device infrastructure layer before Vertiseit's roadmap or Stratacache's financial situation makes the decision for you. You control the timeline, the scope, and the operational continuity of your fleet.

Path two: absorb the transition passively. For Scala customers, this means accepting Vertiseit's device-agnostic direction and whatever device management depth remains in the platform going forward. For ActiVia customers, this means betting that Stratacache stabilizes and continues investing in the product. Both are bets on someone else's business decisions.

Path three: patch. Extend existing contracts, monitor the situation, defer. This path produces a fragile interim state — legacy tooling without active investment, teams stacking workarounds on top of workarounds as the platform atrophies. It consistently produces the most expensive migration when the inevitable finally happens.

The first path requires a decision. The second and third happen by default.

FAQ

What is Scala, and what does the Vertiseit acquisition mean? Scala is one of the most widely deployed digital signage CMS platforms in the world — it schedules content, manages playlists, and distributes media to screens across QSR, retail, and enterprise environments. Vertiseit, a Swedish software company, acquired Scala from Stratacache in May 2026. Vertiseit has stated its intent to move Scala toward a SaaS-based, device-agnostic model and integrate it within Dise, its partner-only platform offering.

What is ActiVia, and what happened to it in the Scala deal? ActiVia is Stratacache's QSR-focused digital signage CMS platform — it handles content scheduling, device monitoring, and network management for highly distributed restaurant environments. ActiVia was not sold to Vertiseit. It remains with Stratacache, which divested Scala under significant financial pressure in May 2026. ActiVia's ongoing roadmap investment and support continuity are tied to Stratacache's business trajectory, not Vertiseit's.

What's the difference between a signage CMS and a dedicated device management platform? A signage CMS — whether Scala, ActiVia, or any other platform — manages what gets displayed on your screens: content scheduling, playlist distribution, and media delivery. Device monitoring features built into a CMS tell you what's happening at the screen level in the context of content management. A dedicated device management platform operates at the OS layer, below the content player: it enforces device state, manages firmware, handles OS updates, controls boot behavior, and provisions new devices without manual setup. These are different infrastructure problems, and the gap between them becomes operationally visible when the vendor behind the CMS is in flux.

Can I keep using my CMS if I add Esper for device management? Yes. Esper operates below your CMS, independent of your content platform. Scala keeps scheduling and distributing content. ActiVia does the same. Esper controls the device running the CMS — OS state, firmware, security posture, network configuration. The two layers are architecturally independent, which is precisely what makes this migration possible without disrupting what your stores see on screen.

Can I add a dedicated device management layer without re-enrolling devices? Yes, in most cases. Esper works with existing device hardware using publicly available device images. The migration doesn't require disruption to content delivery or existing workflows, and doesn't depend on proprietary tooling from the outgoing platform. See Esper's digital signage management page for specifics.

How long does fleet migration take at enterprise scale? Migration timeline is driven by provisioning architecture, not device count. Esper's Blueprint model means the configuration work happens once — not once per device. Enterprise-scale QSR fleet migrations have been completed in weeks. For a scoped estimate based on your fleet size and configuration, get in touch.

Does Esper support enterprise QSR and retail signage fleets? Yes. Esper is deployed at enterprise scale across QSR, retail, and digital signage environments, including a top 10 QSR and DoorDash. Esper's Blueprint model is built for high-volume dedicated device fleets requiring zero-touch provisioning, OTA update control, and remote access across thousands of locations.

What questions should I be asking my vendor right now? For Scala customers: What specifically does "device-agnostic" mean for the device monitoring and provisioning features you rely on today? What's the explicit timeline for product changes under Vertiseit ownership?

For ActiVia customers: What is Stratacache's stated investment plan for ActiVia going forward? Is support covered under your existing contract and for how long? Is there a formal product roadmap communication planned?

For both: If you're not getting direct answers to those questions within 30 days, that absence is itself operationally relevant information.

The hardware is yours. The content is yours. The device infrastructure underneath your signage platform is the one thing still in question — and it's the one thing you can take back, on your timeline, before someone else's business situation makes the decision for you.

See how the migration actually works →