Statamic, AI-built addons, and the maintenance problem

Over the past few months, the number of new extensions for PHP-based content management systems has grown faster than at any point I can remember. Craft and WordPress see a steady stream of new plugins, and Statamic of new addons and starter kits. Many of them come from people who were not part of the developer community a year ago, and many were built with an AI coding assistant in a matter of hours.

That in itself isn't a problem. A lower barrier to building software is a good thing, and plenty of useful tools will come out of it. I want to know whether these addons will still be supported in two or three years. Some of them seem built for a quick sale, and if sales don't come, I doubt the authors will keep maintaining them.

Why maintenance matters in client work

When I install an addon in a client project, I take on a dependency for the lifetime of that site, often five years or more. The addon has to keep up with every major Statamic release, every Laravel upgrade, and every new PHP version. If the author stops caring, the cost falls on my client and me: either I fork the code and maintain it myself, or I replace the addon and migrate content modeled around it.

For a long time, choosing an addon was mostly a question of reputation. In the Statamic community, you knew the handful of developers whose work you could rely on. Their names showed up on Discord, in GitHub issues, and at conferences, and they had a track record of supporting new releases on day one. That was never a formal quality system, but it worked because the number of addon authors was small enough to keep track of.

Today I often find several addons for the same task, released within a few weeks of each other, all with tidy listings and extensive documentation. I have never heard of most of the authors. A well-written README no longer tells me much, because generating one takes minutes. None of it tells me whether the author will still respond to an issue next year, and that makes it harder to recommend an addon to a client or to estimate what maintaining it will cost.

What Statamic changed in September

On September 14, Statamic published Stewarding the Marketplace, in which Jack McDade writes about this problem. He describes a sharp rise in submissions and acknowledges that AI tools now let almost anyone turn an idea into a working addon in very little time. Statamic keeps 25 percent of every paid addon sale on the marketplace, so his conclusion is surprisingly direct. In his view, the barrier has become too low, and he writes that "friction will increase quality."

The most visible change is a set of submission guidelines with eleven numbered rules, each with examples of what is and isn't acceptable. Creators can also download a review skill and run it with their own coding assistant to check their product against the same rules before submitting.

On top of that, every product is now reviewed before it is listed. AI skills handle the first pass, with people involved in the review.

Many of the rules match what I check before I recommend an addon to a client. Products must add original value instead of repackaging the same kit under different names (Rule 01). They must integrate through supported extension points rather than modifying core files (Rule 02). A tagged release has to install cleanly into a fresh site, and updates must preserve existing content and configuration (Rule 06). Permissions, credentials, and external requests have to be handled safely (Rule 07). And there has to be documentation, a changelog, and a support channel that actually works (Rule 09).

The guidelines explicitly welcome AI tools, but the creator remains responsible for reviewing, testing, and maintaining what they ship. Statamic judges the result, not the tools. Suspecting AI involvement is not enough to reject a product.

The rules also apply to products that are already listed. Addons that fall short can be unpublished and have to pass a new review. For me, that is the more important part, because many of these addons are already running on client sites.

For creators, a listing has clear advantages. Marketplace products appear on statamic.com and are pulled into tools like Sherpa, Laravel Forge, and Ploi. For paid products, Statamic handles checkout, VAT, license delivery, and refunds, and pays out through Stripe. Creators can still sell their work elsewhere, but for most developers, the official marketplace is the first place to look, which gives the guidelines real leverage.

Automatic renewals

Three days later, on September 17, Statamic introduced Automatic Renewals. Licenses for Statamic Pro and eligible marketplace products can now renew updates and support every year with a saved payment method. The feature is opt-in and can be switched off at any time.

For my client work, this mainly cuts down on admin work, because renewals can become part of the maintenance agreement instead of a yearly round of reminders and approvals.

For long-term support, the more important question is what renewals mean for creators. Statamic presents recurring revenue as a way to make multi-year maintenance financially viable. Bug fixes, support requests, documentation, and compatibility with new Statamic and Laravel releases take time every month, not only at launch. The marketplace announcement had already mentioned renewal subscriptions for larger products that need ongoing development. To me, both changes aim for fewer products in the marketplace, but ones whose authors can afford to keep working on them.

Statamic itself is careful to say that recurring revenue does not guarantee a good product. I agree. But a one-time sale creates exactly the incentive I am worried about. The money comes in at launch, and every hour of support afterward is unpaid. A renewal model at least ties income to continued use, which makes it more rational to keep a product alive than to abandon it and publish the next one.

What remains open

I think Statamic's decision is right. Still, a review at the time of submission can only check what exists on that day. Whether an addon is really maintained only becomes clear over time. I see it in how quickly it supports the next major release, how the author handles issues, and whether new versions keep coming. I would like the marketplace to show that history as prominently as the listing itself, so customers can see whether an addon is actually being maintained.

Scale is the other open question. Reviewing every product takes time, and Statamic already expects an adjustment period. If submissions keep rising, the review queue will show how sustainable this approach is.

For my own client work, the routine stays the same, but it matters more now. I check who is behind an addon, look at the release history and the issue tracker, prefer authors with a track record, and include license renewals in maintenance contracts. Automatic renewals make that last step easier. The new review process makes the first one a little less of a gamble.

Other ecosystems face the same flood. WordPress reports record plugin submissions and has responded with more reviewers and automated security checks for every release. Craft reviews new plugins too, but explicitly not for code quality or security. As far as I can see, Statamic is the first to combine stricter quality rules with a business model for long-term maintenance, and I would like to see more CMS vendors follow.