Strapi's validation and typing setup has kind of evolved organically as the product grew, and it left traces. Right now, data structures get defined all over the place: frontend forms, backend APIs, Content API, Admin API, plus TypeScript types that often don't quite sync up with the actual runtime behavior. The result is several duplication, things drifting out of alignment, and a codebase that's trickier to work with than it needs to be.

Bringing in Zod as Strapi go-to schema layer allows to have just one unified definition handling both validation and typing across the whole stack. One spot to define structure. One source of truth for what data should look like and what's valid.

For contributors, this means way less time wrestling with overlapping systems and way more confidence in making changes.

For devs building on Strapi, it would mean more consistency and reliability. What the Admin UI enforces actually matches what the API enforces. Plugin contracts are clear and stable. Plus, with Zod 4's built-in OpenAPI schema support, this sets us up for way better API docs and stronger guarantees for all the tools and integrations people build on Strapi.