Case Study
View Case StudyTray.ai
Migrating hundreds of thousands of pages, re-platforming and extending for the leading composable AI integration platform
We are the Directus to Kontent.ai migration experts
Challenges with Directus
Directus looks fantastic in demos, but things get rocky once you actually try to use it at scale. Cloud plans jump to enterprise the moment your team grows past five users, and the API limits are tight enough that any traffic spike means aggressive caching or a surprise bill. It feels flexible until you realise the platform has a lot of operational overhead baked in.
On the dev side, updates can introduce breaking changes, the documentation doesn’t always keep pace, and the extension ecosystem is pretty thin. Localization is technically supported but fiddly and easy to misconfigure, and large datasets make the UI noticeably sluggish. And if you want anything deeply custom, you’re suddenly living in Vue.js land, which is not where most teams want to spend their weekends.
Key pain points
Breaking update changes
Directus has a habit of shipping updates that occasionally break things you weren’t planning to fix. Unless you're on an enterprise plan, you don’t get clean version control.
Limited extension ecosystem
The plugin ecosystem is still pretty bare. Anything even mildly niche ends up becoming a “let’s just custom build it” moment, which defeats the purpose of picking a CMS with extensions.
Complex localization setup
Yes, it supports multilingual content, but setting it up feels like assembling IKEA furniture blindfolded. It works, but expect extra config, extra steps, and extra patience.
Version control paywall
Want safe rollbacks, controlled releases, and predictable deployments? Great, Directus will tell you to upgrade first. Versioning is locked behind higher-tier plans, which is… bold.
Vue.js knowledge requirement
Custom interfaces and deeper tweaks need Vue.js, so if your team only speaks React, prepare for a small identity crisis (or a hiring plan).
Large dataset performance issues
Heavy tables and deeply relational data can slow down queries and the UI, forcing you to optimise more than you probably wanted to.
Benefits of Kontent.ai
Calling your CMS “Kontent dot ai” is a brilliant way to convince people you’ve built an AI-powered future. And to be fair, the platform does have a clean editor, strong workflow tools, and a respectable multi-channel setup.
It's perfect for the kind of company that has more infosec members than it does have devs. But calling yourself an AI platform doesn’t mean you’re built like one.
Real AI-driven CMS platforms start at the foundation with structured content, flexible modeling, real-time indexing, and an architecture that doesn’t panic the moment you try something complex. Sanity doesn’t even market itself as “AI-first,” but it’s been ahead of the curve for years. They shipped an embedding index before “AI CMS” was a pitch deck buzzword. We even built one of the first AI search tools on top of it.
So yes, Kontent.ai is great. If you want a polished interface and enterprise workflows, go for it. And if you’re dead-set on building your website there, talk to us first. We’ll walk you through it and maybe even find a better way before you spend six months discovering the limits yourself.
Key advantages
Intuitive content management
You shouldn’t need a week of onboarding to publish a paragraph. Kontent.ai nails this with a clean interface that doesn’t punish you for being a marketer instead of a developer.
Flexible content modeling
Build content the way your brain works. Modular, structured, reusable. No dev intervention every time marketing decides “we need one more field.”
Strong API-first architecture
The APIs are predictable, well-documented, and don’t require wild workarounds. Everything connects the way it should and developers stay happy too.
Tech stack integration
React, Vue, Angular, or whatever framework you’re obsessed with this week, Kontent.ai plays nice with all of them and keeps deployments smooth.
Advanced image transformations
You can resize, crop, and optimize visuals without leaving the CMS. Think of it as an in-house designer that doesn’t complain about aspect ratios.
Real-time collaboration
Writers, editors, and developers can work together without stepping on each other’s commits. Instant updates, fewer Slack messages, and zero “who overwrote my draft?” moments.
Get in touch
Book a meeting with us to discuss how we can help or fill out a form to get in touch
