Scala to Dise: What the Acquisition Means for Buyers

On 20 May 2026 Vertiseit announced it was buying Scala. The deal closed within weeks. For around 24 million euros the Swedish group took control of one of the oldest names in the industry, a CMS that has been driving screens since 1987.

Read it as industry news and it's a footnote. If you're running Scala in production right now, it's the start of a clock.

What actually happened

Strip the press releases back and three facts matter.

Scala is leaving the Stratacache Group, which has been under serious financial pressure this year. Some of its entities have been through insolvency proceedings. So for Scala customers, simply being out of that group is arguably good news on its own.

Scala is moving into Dise, Vertiseit's partner-first subsidiary. The stated plan is to steer Scala toward a SaaS-based, device-agnostic, partner-only model. Vertiseit's own CMO put the logic plainly: "Dise has the reputation and Scala the recognition."

And the integration is early. The whole deal was done in under a month. A lot of the detail, the roadmap, the licensing, the support structure, is still being worked out in public.

Why this is your problem now

Here's the part no vendor press release will say out loud. "Strategic software offering within Dise" and "transition toward a device-agnostic model" are not neutral phrases if you've built your estate on Scala the way it works today.

Every Scala customer now has the same question landing on their desk over the next few months. Stay, migrate, or reopen the market.

Staying is a bet that the roadmap under Dise keeps your current setup viable. Migrating to Dise is the path of least resistance, the one the acquirer is gently nudging you toward. Reopening the market means treating this as the moment to ask whether Scala or Dise is even the right answer anymore, now that you're being asked to move regardless.

None of those is automatically correct. The wrong move is letting inertia pick for you.

The trap

Most decisions like this get made emotionally or by default. The migration story is built to feel like the safe option, because it's the one with the vendor's hand on your back. That isn't the same thing as it being the best fit for your use case, your hardware, and your team.

The other failure mode is panic. An acquisition headline is not a fire alarm. You almost certainly have more runway than the news cycle suggests. Use it.

A neutral way to make the call

You don't need a feature spreadsheet to start. You need to be honest about a handful of structural questions.

Contract and licensing timeline. When does your current agreement actually force a decision? That date is your real deadline, not the acquisition headline.

Device dependency. "Device-agnostic" is the stated direction. If your estate leans on specific players or Scala-specific hardware behaviour, a device-agnostic future can quietly mean re-testing your whole fleet.

Integration depth. Count what hangs off your CMS today. POS, scheduling, data feeds, single sign-on. The deeper the integration, the higher the switching cost in any direction, including staying.

Partner versus direct. Dise is explicitly partner-only. If you've been buying Scala direct, your support and commercial relationship changes shape, not just your software.

Roadmap risk. A brand being "revitalised" is a brand mid-change. Some of that change will help you. Some of it will deprioritise the exact edge cases your operation depends on.

Answer those first. The vendor comparison comes after, not before.

Reopening the market is not disloyal

If you're being asked to migrate anyway, the switching-cost argument that kept you on Scala just got weaker. That's the rational moment to look wider, not narrower.

The market is not Scala and Dise. It's hundreds of CMS vendors, and the right one depends on your scale, your stack, and who runs it day to day. You can browse the CMS and software landscape neutrally before you commit to anyone's roadmap.

We ran it neutrally

The whole industry is asking the same question, so we did the obvious thing and put Scala and Dise side by side in SignageCompass. Same criteria, no vendor writing the script. Some areas are closer than the migration story suggests. Others split them more than you'd expect.

We're not going to summarise the scores here, because specific scoring belongs in the report with its data caveats attached, not in a blog post.

Read the full Scala vs. Dise comparison report (free account to read it).

An acquisition doesn't have to be a problem. It's a forcing function. It makes you ask a question you probably should have been asking anyway. Does my signage platform still fit, or did I just stop checking?