Pre-release

Automated AI defences for web servers

Wake up to servers already patched.

Dawnmender checks your servers against 26 security sources every hour, and patches what it safely can overnight — a copy off the box first, tests before and after, a way back for every change. You wake to a report.

How many servers or sites do you look after?optional

One email when Dawnmender is ready for you. Never shared, never sold.

  1. 02:14PublishedA CVE record: a popular forms plugin, up to 4.2.0, lets anyone upload a file. Fixed in 4.2.1.
  2. 02:15MatchedThree of your hosts run 4.1.x. Each one needs the fix.
  3. 02:22CopiedFiles and database copied, encrypted, sent off the box. Receipt checked.
  4. 02:31RehearsedThe fix tried on an isolated copy of each site. Tests pass.
  5. 02:40PatchedThe official 4.2.1 files swapped in, one site at a time.
  6. 02:43TestedHome, login and the form load. No new errors. Timing normal.
  7. 06:30ReportThree sites patched while you slept. What changed, and the one step that undoes it.
An illustration of how a night’s run is meant to go, not a record of one. Real times depend on the fix and the site.

The problem

More arrives every day than anyone can read.

Measured by Dawnmender’s own observatory on 18 November 2026, from the 26 public sources it watches.

138,739 vulnerabilities and incidents tracked so far, deduplicated across sources.

How it works

Watch. Check. Mend.

  1. Watch

    An observatory reads 26 public sources around the clock — the CVE list, CISA’s exploited list, distro and vendor advisories, security news, exploit releases — and folds duplicates into one record. Every morning a model writes a ranked briefing of what matters.

    26 sources · around the clock

  2. Check

    A small agent on each server takes stock of the whole box every hour: OS packages, web server, PHP, databases, WordPress core, plugins and themes. It reads files, runs as an ordinary user and changes nothing. What it finds is matched against everything the observatory knows.

    841 items in 0.7 s, unprivileged

  3. Mend

    When a fix exists for a WordPress plugin or theme, Dawnmender applies the smallest official release that closes the hole, carefully. Everything else it finds — PHP, the OS, the web server, WordPress core — it reports in plain words, and checks that WordPress’s own updates and your distro’s security updates are switched on and working.

    Plugins and themes in the first release

The scan figure is from a real production server, 18 November 2026.

Why it won’t break your site

Careful is the whole product.

An update that takes a site down overnight is its own kind of outage. Every change goes through the same steps, in the same order, however small the fix looks.

Trust is earned in steps.

  1. Observe

    It reads and reports. Nothing is installed that can change your server.

  2. Approve

    Each fix waits for your click.

  3. Automatic

    Only for sites and plugins that qualify. Shops, membership and learning sites always ask.

Every site shows which step it is on, and the exact reason it is not on the next one.

What it leaves alone in the first release

  • WordPress core — WordPress updates itself; Dawnmender checks that it did.
  • PHP, the OS and the database — reported, never upgraded for you.
  • Premium plugins, major-version jumps and anything with a migration.
  • Deactivating a plugin that has no fix yet. You get the facts and the instructions instead.

The morning briefing

Every morning, the lay of the land.

Written by a model from the day’s sources, ranked by what to act on, with every link taken from the sources themselves — never from the model. This one is real.

Wednesday 18 November 2026 · the 24 hours to 11:49 MST

Patch nginx today: pre-auth HTTP/2 memory corruption; Java4Shell and Puppet also urgent

A heavy day. nginx shipped 1.30.7 and 1.31.9 fixing ten CVEs, including pre-auth memory corruption in HTTP/2 and HTTP/3 handling. Java4Shell drew a patch-now notice from CISA, which also added an exploited Puppet Server RCE to its list. WordPress 7.1.5 landed as a security release, Microsoft’s agent-framework PyPI package was poisoned, and the Optimizely compromise pushed malware through at least 178 major sites.

Act on today

  • Actnginx 1.30.7 and 1.31.9 fix ten CVEs, several rated critical

    nginx released 1.30.7 stable and 1.31.9 mainline. They fix an HTTP/2 flow-control heap overflow, use-after-free bugs in HTTP/2 proxying, HTTP/3, the resolver and the mail proxy (all CVSS 9.2), a TLSv1.3 infinite-loop DoS (8.7) and four medium stream and try_files issues. …

    Why it matters nginx fronts most hosting stacks, and the HTTP/2 flow-control bug is described as affecting any configuration that uses HTTP/2. …

  • ActPuppet Server deserialization RCE is being exploited

    CISA added CVE-2026-115731 (CVSS 9.4) to its exploited list on 17 November with a 1 December deadline. A client holding any CA-signed agent certificate can run code on the Puppet Server as its service user by submitting a crafted report.

    Why it matters One compromised managed node can take over the Puppet server, and from there the configuration of every machine it manages.

An excerpt from the briefing Dawnmender’s observatory wrote on 18 November 2026, quoted word for word; “…” marks a cut. The briefing covers server software broadly. Matching it against your own servers is the agent’s job.

Where it stands

Honest status.

Who makes it

Dawnmender is made by Graphite & Moss, a security and cloud studio in Victoria, BC. It grew out of the tooling we built to keep the sites we host patched. graphiteandmoss.ca

Questions

Before you sign up.

What does the AI actually do?

It reads. A model reads the day’s public advisories and news and writes the morning briefing. In the first release it will also read new plugin releases for security fixes no advisory has announced; a person reviews each of those before anything acts on it.

The model never runs on your server, never sees your data, holds no credentials and issues no commands. Fixed, tested code makes every change, and a check that fails or is missing is never waved through.

What if a patch breaks something?

Then the original files go back, automatically and byte for byte, and you get a report saying what failed. The fix was rehearsed on a copy of your site first, and an encrypted copy of the site left the server before anything changed.

A database is never restored automatically, because that could throw away orders or posts written since. If one ever needs restoring, a person decides.

Which systems does it work with?

The agent takes stock of Linux servers, starting with Ubuntu: packages, web server, PHP, databases and WordPress. Patching in the first release covers plugins and themes from WordPress.org on single-server sites.

Not in the first release: WordPress multisite, cPanel and Plesk servers and managed hosts as places to patch, and premium plugins. It will still tell you what it finds on them.

When can I use it?

Not announced. Dawnmender is in private development. The waitlist gets one email when there is a place for you.

What will it cost?

Not announced yet.

The night’s work, done by morning.

Leave your email and we’ll write once, when Dawnmender is ready for your servers.

How many servers or sites do you look after?optional

One email when Dawnmender is ready for you. Never shared, never sold.