We're building NeoCMS — a CMS designed from scratch for the AI era

We're building NeoCMS — a CMS designed from scratch for the AI era

Hey everyone 👋

We're building NeoCMS — a content management system designed from the ground up for AI-first workflows.

The problem

Every CMS today stores content as HTML blobs — messy markup with inline styles that AI can't reliably read, edit, or generate. When platforms bolt AI on top, it's a wrapper guessing its way through unstructured content. It breaks things. It hallucinates layouts. It can't be trusted to ship production pages.

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.

What's shipped so far

This isn't a pitch deck. We've built and tested:

🔹 50+ widgets (13 live, 37+ in development) — all schema-validated, all AI-native
🔹 Visual drag-and-drop page builder with responsive controls
🔹 Full posts system — Lexical editor, categories, tags, custom fields, permalinks
🔹 Template engine with dynamic placeholders
🔹 SEO insight bar — readability score, keyword density, meta length warnings
🔹 WCAG 2.1 accessibility built in from day one
🔹 First-party auth with RBAC — no third-party auth dependencies
🔹 Multi-level caching (L1 + L2 + L3) with graceful fail-open
🔹 403 tests passing across the entire codebase

Screenshots:

The stack

Next.js 16 · React 19 · TypeScript · PostgreSQL 17 · Prisma v7 · Redis 8 · Docker · Vitest

Every dependency is intentional. No plugin sprawl. No magic.

Where we're at

Currently in pre-launch with 470+ early bird signups. Aila 2.0 identity phase is live — soul personality, contextual memory, and auto-generating widget catalog. The roadmap runs through SaaS beta with Stripe billing and tenant provisioning.

We're looking for founders, agencies, and developers who want early access and direct input on features.

👉 neo.tawaar.net — check it out and join the early bird list if it resonates.

Happy to answer any questions about the architecture, the AI pipeline, or why we think structured schemas are the future of content management.