We personalize Storyblok with Ninetailed, what does the Contentful acquisition mean for us?

Your read on acquisitions like this is the standard one and it is usually right: the acquirer pays for the tech to strengthen its own platform, and integrations with competing CMSs become maintenance items rather than roadmap items. The March 2026 sunset of the standalone legacy app confirmed it, and the incentive structure was never subtle.

For Storyblok specifically, the option I would look at first is the slot overlay approach. Croct ships an Optimize app that runs inside Storyblok's own interface, so the personalization tooling is CMS-native to Storyblok rather than a generic layer with a Storyblok adapter. Structurally that matters for your worry: you would be on an integration that is a flagship for the vendor, not a legacy edge case.

Mechanically it works by linking your existing blocks to slots, with the Storyblok content staying as the default fallback. Which leads to the practically useful part for you: evaluating a switch does not require any content migration. Your blocks stay where they are, so you can trial it on a couple of components before committing to the rest of the move.

We went through this exercise after the announcement too. My advice is less about picking the replacement and more about scope: write down which Ninetailed features you actually use (for us it was audiences and two running experiments, far less than we thought) and verify that at least one alternative covers that list. Turns a forced migration into a scoped, boring project. The fallback-based options are nice for exactly this because the trial costs you nothing on the content side.