Changelog

How WPCentrify was built, month by month

A dated, honest record of the work: from the first idea in late 2025, through brand, stack and team, to the platform and the site you are reading now. During early access this covers the build and capability status, so you can follow real progress rather than marketing.

September2026

Phase 2 · Product

Phase 2: safe updates, backups and monitoring

Built out the operational core the platform exists for: safe updates with pre-flight risk scoring, visual checks and automatic rollback, alongside bulk core, plugin and theme updates run across every connected site at once.
Added encrypted off-site backups with one-click restore, plus continuous uptime and performance monitoring, so a site that goes down or slows down is caught in minutes rather than reported by the client first.
Rolled the results into plain-language client reports that gather updates, backups and uptime per site into something worth sending, ready to carry your own brand.

Phase 3 · Sentinel

Phase 3: Sentinel security monitoring

Launched Sentinel, WordPress security monitoring that watches every connected site and tells you the moment something changes, from an altered core or plugin file to a new administrator appearing where none should be.
Added sign-in monitoring that tells an ordinary run of failed logins apart from a password that was actually guessed, and raises the serious cases as critical with an email straight away instead of leaving them for a weekly summary.
Grouped every finding by problem across the whole portfolio and split it into a short critical queue and everything else, so the security to-do list stays finishable.

Phase 4 · Product

Phase 4: performance scores in your dashboard

Added performance scoring for every connected site using Google PageSpeed and Lighthouse, with a Mobile and Desktop score at a glance plus the detail behind it: how quickly the page appears, how fast it responds, and how stable it stays while it loads.
Put clear scores straight on the Websites list, so the whole portfolio reads at a glance with no digging, and made one click into any site's Performance tab open its full Core Web Vitals.
Kept the numbers current on their own: checks run automatically on a schedule, any site can be re-scanned instantly with Check now, and it all lives inside WPCentrify rather than in separate testers or spreadsheets, so each site's speed is something you can show a client in seconds.

Phase 5 · Product

Phase 5: on-page SEO for every site you manage

Added Content and SEO, so the search title, meta description, social cards, headings, canonical, robots rules and schema for any page on any connected site can be edited from one dashboard, with a live Google result preview and character counts as you type.
Every change is written into the SEO plugin that site already runs, whether that is Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework or Slim SEO, so no page ends up with two titles or two canonicals and nothing is locked to us. Sites with no SEO plugin are handled by WPCentrify itself, and one action moves everything across if a plugin is added later.
Added a portfolio-wide audit that scores every page out of 100 and names the problems in plain language, so a published page quietly set to noindex, a missing description or a second H1 surfaces in one filtered screen instead of after five months. The launch post walks through it.
Made headings editable inside the page builder that owns them, across Gutenberg, Elementor, Divi, Bricks, Beaver Builder and WPBakery, and put a read-only view of what the live page actually serves next to what you configured, so stale cached HTML is caught rather than argued about.

Phase 6 · Product

Phase 6: every client inquiry in one list

Launched Lead Capture, which collects contact form submissions from every connected site into a single list, reading nine of the major WordPress form plugins and catching submissions from forms it does not recognize so they are flagged for you to confirm rather than lost among the rest.
Added a spam filter that explains itself in sentences rather than scores, so a doubtful inquiry arrives with the reason attached and you can judge it yourself. Nothing is ever deleted: spam is kept behind a filter with its reasoning, and marking something as not spam brings it straight back and counts in that sender's favor next time.
Gave you the rules: alphabets you do not do business in, countries, blocked email domains with an always-accept list that overrides them, phrases you never expect, and a deliverability check. Change any of them and the last 90 days are re-checked at once, except anything a person already ruled on by hand.
Built it to stay out of the way of the client's site. It reads alongside whatever form plugin is already there rather than replacing it, collection is off until you switch it on for a specific website, you choose how long anything is kept, and inquiries are their own permission that nobody holds by default.

Phase 7 · Product

Phase 7: access without passwords, and a door you can close

Rebuilt one-click login around named accounts, so everybody who reaches a client site arrives as themselves at the role you allowed, and the site's own history records who actually did what. Nobody on your team ever holds a password for a client site.
Made access something you grant and take back in one place: a role set per person per site, or across every site including the ones you connect later, re-applied on every sign-in so lowering it today is what they get tomorrow. Remove somebody and every session they hold ends within a minute, with nothing to clean up site by site.
Added a live list of who is signed in where, with a Sign out on each session, and put the whole picture on the record: who, which site, as which account, from where, to which screen, for how long, and what they changed while they were there.
Added lockdown, which is only possible once passwords are out of the picture. Switch off the normal WordPress login for administrators, or turn away any administrator session reaching wp-admin that did not come through WPCentrify, while customers and checkout carry on untouched. The way in is tested before the site is locked, you get a recovery link and a switch in wp-config.php, and a site that loses contact for a day relaxes on its own.

Phase 8 · Atlas

Phase 8: Atlas, a calmer way to read the fleet

Shipped Atlas, a new optional theme for the dashboard. Warm paper instead of a dark sidebar, one blue instead of a gradient, and rules instead of boxes, on the reasoning that a card around every item costs a border, a shadow and sixteen pixels of padding, and pushes the fifth thing off the screen.
Reordered the Overview so it opens with what needs you first. Every open issue across every website, ranked by severity with a plain sentence attached, so a site that is offline and a site with one plugin update stop looking like the same size of problem. The charts moved below the list, because a number is context and a ranked list is a plan.
Added a command palette on Ctrl K, one health verdict per website with a score, the checks behind it and what to do next, and a fleet rolled up by client so a Monday review reads like a report rather than a filter you have to remember to apply.
Made every open screen refresh itself when something on a website moves, so no figure sits there going stale while you look at it. Classic stays exactly as it is and stays the default: Atlas is a per-account preference with light, dark and system modes, nobody is migrated, and nothing is deprecated.

Phase 9 · Aurora

Phase 9: Aurora, a brighter way to run the fleet

Shipped Aurora, the boldest theme yet and the fourth you can choose alongside Classic, Atlas and Meridian. It retires the sidebar and moves navigation up to the top: six clear areas, a violet indicator that follows you, and a bottom tab bar on a phone that your thumb can actually reach.
Rebuilt Home as a bento, arranged around the one website that needs you next, with fleet vitals as a cluster of rings and the headline numbers as their own tiles. Counters count up and rings draw in from a resting state, and it all honors reduced-motion the moment you ask it to.
Gave the whole workspace a fresh violet that runs from indigo through magenta to cyan, spent only on the brand mark, the primary buttons and the active tab, with color otherwise kept for severity. It ships in full light and deep-indigo dark modes, plus system.
Kept it a theme, not a rebuild: every screen, number and workflow stays where it was. Classic is still the default, Aurora is a per-account preference nobody is migrated to, and because the screens are shared, anything built next turns up in Aurora on its own.

August2026

Phase 1 · Product

Phase 1 begins: team foundations and site management

Started building the first production slice of the platform, focused on the account layer teams need before anything else: team access, flexible role-based permissions and two-factor authentication.
Added client grouping, site tags and hosting details so larger WordPress portfolios can be organized the way an agency actually thinks about them, not as one flat list.
Introduced maintenance windows, freeze periods and quiet hours, giving teams control over when work runs and when non-urgent alerts are allowed to interrupt.

Website

Bright redesign and honesty pass

Rebuilt the marketing site in a bright palette with a clearer information architecture and a full internal-linking pass.
Added interactive tools built to be genuinely useful: a care plan pricing calculator and a maintenance checklist, both ungated.
Introduced hand-built charts for maintenance hours and pricing, with no-JavaScript fallbacks so nothing depends on scripts to be readable.

July2026

Team · Content

SEO and content specialists brought on

Hired SEO specialists and content writers to produce genuinely informative material, from maintenance and care-plan guides to honest competitor comparisons and a plain-language glossary, rather than thin marketing copy.
Set the editorial standard the site still runs on: every comparison names who each product is best for, sources are dated and re-checked, and there are no affiliate links anywhere.

June2026

Build

Documentation written and the website build starts

Wrote the product and architecture documentation that the build works from, so the platform and the site were being built against a written spec rather than assumptions.
Began building the marketing site itself: the page templates, the design system and the first content structure.

May2026

Team

Design and engineering hired

Brought on designers and developers to turn the concept and the brand into a working platform and a real website.
Set up the development workflow, environments and review process the team still uses.

April2026

Foundation · Stack

The technology stack is chosen

Chose the stack the platform is built on: Laravel (PHP) for the API, React and TypeScript for the dashboard, and PostgreSQL with Redis behind them, for reliability at portfolio scale.
Decided the connection to WordPress would be a lightweight, framework-free plugin, so the platform stays hosting neutral and adds nothing to a site's front-end page loads.

March2026

Identity

The name and the mark: WPCentrify

Settled on WPCentrify as the product name after working through the alternatives and checking it stood on its own.
Designed the brand mark that now appears across the product, the site and the connector plugin.

February2026

Brand

Brand direction and palette

Developed the visual direction: a bright, legible palette and a typographic system chosen to read clearly across a data-heavy dashboard and a marketing site alike.
Set the design principles the whole product would be held to, before a line of interface was drawn.

January2026

Foundation

The product foundation is laid

Turned the idea into a defined product: the problem it solves, who it is for, and what a first version genuinely needs to do to be worth using.
Scoped the operational lifecycle the platform would own: updates, backups, monitoring, security and reporting, and drew the line between the first release and the roadmap.

November2025

Genesis

Where WPCentrify started

The idea and the brainstorming. It came from a real, recurring problem: managing more than a handful of WordPress sites means doing the same work over and over.
The decision that shaped everything after it: to build an operations layer for WordPress around verified updates and evidence rather than a longer feature list.

Answers

Questions about the changelog

Yes. It is the actual build sequence: the idea in November 2025, the product foundation and brand through early 2026, the team and stack in spring, and the platform and website build over the summer. We would rather post fewer real entries than pad the log.

Not always. A Phase or Foundation entry describes work that has started or shipped into early access, not necessarily a finished capability. The roadmap is the source of truth for what is available now, rolling out, and planned.

Whenever a meaningful, verifiable change ships. As WPCentrify moves through early access, new entries will land at the top of this timeline as each phase of the platform is built.