Why We Built the Gridonic Engine
A website isn’t finished once it goes live. It’s maintained, expanded, translated, analyzed, and secured—month after month. It’s precisely in the course of these operations that minor glitches arise that no one anticipates: A new page goes live, but the French translation is missing. An image is uploaded without alt text. A third-party script pushes up the Largest Contentful Paint, and no one notices until someone asks about it.
The Gridonic Engine is our answer to this: a layer between a project’s CMS and the people who work with it. It connects AI agents directly to the respective DatoCMS project—not as a generic chatbot, but with real access to the CMS schema, content models, records, assets, and publishing workflows.
This was made possible because DatoCMS took an early lead in AI and was one of the first CMS platforms to provide its own MCP server. The Model Context Protocol is the standard through which AI systems communicate with external tools in a structured way: no screen scraping, no fragile integrations—just defined operations on the actual data model. We’ve been a DatoCMS partner from the very beginning and maintain close ties with the team in Italy—building on this foundation, we’ve since developed a whole range of AI integrations.
What that feels like in everyday life
The best example is our agent Puja Publishing . It allows customers to access the CMS directly from their familiar AI interface—for example, from within ChatGPT.
A realistic timeline for a hospital project:
"Please create a new doctor's profile using the attached PDF and the portrait photo."
Puja reads the PDF, creates the doctor’s record in the CMS, processes the photo—and then asks for clarification instead of guessing: Where should the entry be linked? In the “Internal Medicine” department, right next to Dr. Peter Fankhauser? And immediately after that: “Should I ask Lana Language to handle the translations?”
Two things are crucial here. First, the agent works within the actual data model, so it is familiar with all areas of the website, including relationships, modules, features, and required fields. Second, if anything is unclear, it escalates the issue to a human instead of publishing an assumption. All new content is saved as a draft—approval remains with the editorial team.
And third, and perhaps even more importantly: agents work together. Publishing calls Language, Language notifies Search, and Search knows the performance baseline. That’s the real leap—from individual assistants to a coordinated team.
The Eight Agents
Optionally, we offer various AI agents through the Gridonic Engine that are directly connected to the respective DatoCMS project. Each has a clearly defined area of responsibility.
Puja Publishing — Content into the CMS
Transfers the final content from the content creation phase into the CMS in a structured manner: text, translations, edited images, SEO configuration, and alt text. A content concept is transformed into a fully populated CMS, eliminating days of copy-and-paste work. It also assists throughout the project by creating the page tree, all pages, and content using modules. It publishes content on command and can even perform migrations involving several hundred pages overnight.
Lana Language — Translation Quality
Continuously checks the front end and back end for translation quality: identifies missing pages or modules as well as incorrectly or inconsistently translated paragraphs and reports them monthly. This is particularly relevant for Swiss websites with three or four languages, where gaps are often only noticed when a customer reports them.
Beny Search — SEO
Audits the website monthly for SEO: identifies missing meta descriptions and alt text, and highlights areas for optimization to improve rankings. This isn’t a one-time audit that ends up gathering dust in a folder—it’s a recurring check against the live version of the site.
Angie Analytics
Monitors traffic, conversions, and goal achievement; identifies notable trends; and provides clear, easy-to-understand monthly insights along with recommendations for action. The difference from a dashboard: Angie explains what the data means and what to do next.
Peter Performance
Monitors key performance metrics such as page speed and Core Web Vitals, and alerts you if load times deteriorate or there is room for optimization. Performance regression is rarely a one-time event; rather, it’s a gradual process—which is exactly why continuous monitoring is essential.
Susan Support
Contact person for support inquiries: Instead of writing a ticket and submitting it, just send Susan a short message—she’ll clarify the inquiry or resolve it directly, either with her agents or our team. The biggest practical hurdle for support is a single sentence in natural language.
Sebi Security
Continuously monitors the website's security: checks for vulnerabilities, keeps systems and dependencies up to date, handles backups, and reports risks before they become problems.
Ina Image
Manages the website's visual content and creates new images as needed, based on the established styles and guidelines. This ensures that the visual style remains consistent, even if an image is missing at the last minute.
What this means in practice
Three patterns emerge time and again:
"Occasional" becomes "continuous." Translation, SEO, and performance checks used to be done whenever someone had time or something wasn't working. Now they're done monthly, automatically, against the live version.
A ticket turns into a conversation. Anyone who needs a change describes it in a single sentence—instead of filling out a form that someone else then has to translate back into work.
It is up to the individual to decide. The agents work in a coordinated manner; they do not publish content on their own initiative. Drafts, inquiries, announcements—the final approval rests with the team.
Who Will Benefit from This
The Gridonic Engine really shines when a website is multilingual, receives new content regularly, and actually requires significant effort to maintain. A static, five-page site doesn’t need it. But for a clinic, association, or brand website with hundreds of records and three languages, it makes a measurable difference.
The agents can be booked on a modular basis—you start with two or three and expand as the benefits become apparent.
