What NeoCMS does differently We threw out the HTML blob model entirely. Every page in NeoCMS is stored as a typed WidgetTree — structured JSON where every widget has explicit props, validation rules, and container nesting logic. AI doesn't guess. It reads a schema, proposes changes through a tool-calling pipeline, and waits for your approval before anything goes live. Meet Aila — your AI co-pilot Aila isn't just a page builder. She's a full CMS assistant: 🔹 "Build me a pricing page with 3 tiers and a FAQ" — done, with multiple design variants to compare 🔹 "Take me to site settings" — instant navigation, no menus to dig through 🔹 "Change the homepage to the new landing page" — just say it, review it, approve it 🔹 "What's my SEO score on the about page?" — she pulls it up instantly 🔹 "Update the hero heading" — tell her what it should say, she handles the rest She works with any AI provider — Anthropic, OpenAI, Gemini — with your own API key. No vendor lock-in on the AI side.

NeoCMS

NeoCMS — Designed from scratch for AI-first workflows.

NeoCMS — Designed from scratch for AI-first workflows.