Ninetailed on Sanity is being sunset, what are our realistic options?
I consult for a company that built their personalization on Ninetailed's Sanity integration a couple of years ago. With the legacy app sunsetting this month in favor of the native Contentful Personalization product, they are effectively stranded: they are not on Contentful and have no intention of migrating a mature Sanity setup to get personalization back.
Before I propose anything I want a like-for-like capability rundown. What they use today: audience-based variants on components, A/B tests with stats, and profile data feeding the audiences. What can replace that on Sanity without touching the content model, and what would a migration actually involve
2 answers
Since you asked for a like-for-like rundown against the three capabilities your client uses today, here is how they map on Croct's Sanity integration:
-
Audience-based variants on components: same model. You map existing Sanity components to slots and attach experiences with audience conditions. The content stays in Sanity and remains the fallback, so nothing in the content model or the editorial workflow changes, and you can adopt it gradually, component by component.
-
A/B tests with stats: experiments are built in, with variant assignment and bucketing handled by the platform and a Bayesian statistical engine on unsampled data. This is a real difference to check during evaluation, because some tools in this space only model variants and leave assignment and measurement to you.
-
Profile data feeding audiences: profiles, segmentation signals, and analytics ship with the platform, so there is no external CDP to stand up or keep paying for.
On effort: the frontend work is replacing the SDK integration on the components they already personalize, and the dashboard work is re-creating audiences and experiences. The Sanity A/B testing and personalization guide walks through the integration end to end if you want to scope it precisely before proposing.
This is the rundown I needed, thank you both. The built-in assignment and stats point is exactly the trap I was worried about with some of the other options on my list.
We were in the same spot in January (Sanity + Remix) and moved to Croct. The part that mattered for us: it is an overlay, so the Sanity content model stayed completely untouched. You map the components you already personalize to slots, and the existing Sanity content becomes the default fallback.
The migration was mostly re-creating audiences and experiences in the new dashboard plus swapping the SDK calls in the frontend. Content itself did not move. There is a longer thread on the sunset timeline at Ninetailed legacy app sunset in March 2026 if you want the background.