Patchstack opens early access protection for AI-built apps

Patchstack has opened Early Access to a protection service for AI-built apps, meaning the applications people create with artificial intelligence coding tools. The company says the offering covers Lovable, Replit, Base44, Claude Code and other JavaScript applications, and that it is free while the early access period lasts, after which its standard subscription pricing applies. The announcement was published on September 18, 2026 and written by Oliver Sild, Patchstack's chief executive.

The company's argument for the launch rests on sheer volume. AI-generated apps ship with more packages than the average WordPress site ships with plugins, Patchstack says, and a simple to-do app arrives with over 800 packages from the start. A package is a ready-made block of code that a program installs and reuses instead of writing that function itself, and the number grows with the complexity of the app. Patchstack adds that once these apps are live, most are never properly maintained: even when a vulnerability is known, upgrading feels risky, so it does not happen. That is the same fear-of-breaking-things pattern, the company says, that has driven every major WordPress compromise it has mitigated.

What has changed, in Patchstack's account, is who is doing the building. A year ago, Node.js builders were mostly software engineers, the company says; today they are founders, marketers and independent hobbyist developers who have never used git, the tool programmers use to track changes to code. Most existing JavaScript security tools were designed for the engineers who no longer make up the majority of this audience, Patchstack argues: they assume the user can read a diff, meaning the marked-up comparison that shows what changed between two versions of a file, and can patch the code personally. Most builders cannot do that, the company says, and most cannot afford the enterprise tooling built for teams that can. Patchstack also warns that AI-assisted vulnerability research and AI-powered attacks are making the gap more dangerous every month, that AI-generated patches are useless if nobody applies them, and that rushing a package upgrade now carries its own risk of a supply chain compromise, where malicious code is slipped into a trusted update.

The mechanism Patchstack is offering is called RapidMitigate, and the company says it now runs inside the JavaScript application itself. According to Patchstack, it identifies vulnerabilities, traces their reachability and mitigates them at application runtime. Reachability here means working out whether the flawed piece of code can actually be reached and triggered by an attacker; runtime means the period when the program is running and serving real requests, rather than while it is being built. When a new vulnerability surfaces, a mitigation rule deploys and activates automatically, with no changes to the codebase and no rebuild. Patchstack says this neutralises the vulnerability immediately, without exposing the app to a supply chain attack and without the fear that an upgrade will break something, giving the owner time to patch properly on their own schedule with no exposure in the meantime.

The company is also launching a second component called Live Hardening, described as a new output-filtering module inside the same RapidMitigate runtime. Where mitigation is aimed at incoming exploit attempts, Live Hardening watches what the application serves back out. Patchstack says it blocks leaks of Supabase secret keys and service role keys, vendor API keys and tokens, private keys, and internal error messages that reveal more about a system than they should. Setup is described as a prompt inside the interface the builder already uses, after which Patchstack automatically installs itself and starts monitoring.

Those apps then sit alongside everything else in one account. WordPress sites, AI platform apps and custom Node.js apps hosted anywhere are now managed under a single Patchstack account, the company says, with visibility and control across all of them. On platforms such as Lovable, a quick access widget loads directly into the builder's sandbox, the isolated working environment where the app is assembled, so the controls appear where the work is already happening. Patchstack notes that the widget's interface may change during the Early Access period.

The launch is also a statement about where websites get built. Patchstack says WordPress is no longer the only place people build for the web, and that AI builders and Node.js hosting are now standard offerings from its own hosting partners, a shift that has quietly recreated in a different technology stack every security problem the company spent five years solving in WordPress. Its recent partner announcements point the same way: in March 2026 Manage by Elementor gained Patchstack vulnerability detection, in April 2026 HostArmada added Patchstack to its security stack, and in August 2026 FlyWP added proactive vulnerability protection from Patchstack. Those integrations belong to Patchstack and to those vendors, and they matter here because they show a security vendor pushing its protection into the tools website owners already use.

Some details remain open. Patchstack has not published a list of the specific vulnerabilities its runtime rules cover, nor a list of supported platform versions, and it gives no figures for the pricing that will apply once the free early access period ends, saying only that standard subscription pricing will be used. The company describes the tooling as mitigation, a protective layer applied while software is running, and not as a replacement for updating the software itself: it says builders get time to patch properly, which implies the patch is still expected to happen.

For WordPress owners, the maintenance problem described here cuts both ways. A hosting provider that maintains and secures the platform for the customer removes much of the burden that Patchstack says pushes people to skip updates, and AEU Hosting offers managed WordPress hosting that is secured end to end, which covers that part of the job for readers who would rather not handle it themselves. Whoever builds or hosts a site should still know who is responsible for applying security fixes when they land.