One module per job
No twelve competing SEO plugins. We develop a single official module for each capability, held to one standard, so there is never a question of which one to trust.
Plugins made WordPress endless, and impossible to trust. Modules are our answer: one curated, API-first extension per job, reviewed by us and supported in the core. Anyone can build one. Only the ones we approve ever show up in your install.
No twelve competing SEO plugins. We develop a single official module for each capability, held to one standard, so there is never a question of which one to trust.
Every module is built API-first and connected through the core, permissions, migrations and the headless API included. Not bolted on the side, part of the system.
Build your own freely. But until it meets our every demand and we sign off, it is unsupported and invisible to the platform. No marketplace, no surprise CVEs.
Each is built and maintained by Atypisch, reviewed against the same bar, and free to self-host.
Meta tags, sitemaps, canonical URLs, structured data and redirects. Managed in the admin, served by your themes and the API.
Per-field localisation, language fallbacks and a translation workflow. One content model, every locale, one API.
Accounts, comments, profiles and moderation. A members layer for any project, scoped and API-first.
Each one ships only once it meets the bar, API-first, fully wired and reviewed. Want a say? The roadmap is public.
Products, carts and orders as native collections, with a checkout API.
Build forms against your schema, with validation, spam protection and submissions.
Full-text search across collections, with facets and typo tolerance.
Privacy-first, self-hosted analytics wired to your content model.
Some modules are commercial. Built and maintained by Atypisch, they fund Modular's open-source core, so the platform itself stays free and open, for good.
The CMS and its core capabilities are MIT-licensed, forever.
Commercial modules pay for full-time maintenance and security review.
Self-host everything. Cancel a module and your content is untouched.
Anyone can build a module. Test against the core, meet the review bar, and submit it. Until it is approved it runs only in your install, and never appears in anyone else's registry.
Read the guideAdd a reviewed module in one command, or build your own to the same standard. Either way, your install stays clean.