Our story

I installed the same eight plugins a thousand times

I've built thousands of WordPress sites. Every one of them brought me to the same list — and at some point I turned that list into a single plugin.

Overview

Building a WordPress site takes a few hours. Making it work takes days.

I've been doing this for years. Small businesses, agency work, my own projects. Every time, after picking a theme and adding the content, I arrived at the same list: an SMTP plugin, an SSL plugin, a backup plugin, something to hide the login URL, a snippet to clear the notice clutter out of the admin. Eight things, ten, sometimes fifteen.

Each installed separately. Each updated separately. Some of them paid for separately.

The migration that finally did it

I had to move a site to a different server. The plugin I was using let me take a backup for free, but not restore one. So I downloaded the backup to my machine, opened FTP, uploaded the files by hand and imported the database by hand. The plugin had already made the backup; it just would not let me put it back. Do that once and it is annoying. Do it for the hundredth time and you make a decision.

A backup should not disappear with the server

cPanel takes backups, but onto the server's own disk. If you want an automatic backup to Google Drive or another FTP, you either buy a plugin or do it by hand. If the server goes down the backup goes with it, which is nearly the same as having no backup at all. Automatic backup to remote storage is not an option; it is what backup means.

Sending mail should not take twenty minutes

WordPress's own mail function does not work, and everyone knows it. Connect Google Workspace or Microsoft 365 through a free plugin and you are into OAuth setup: create an app, grant consent, copy the keys, set the redirect URI. Twenty minutes of work, and again from scratch for every client. It did not take long to notice that this setup could be one click.

Changing one number across three hundred pages

A client wanted to change a phone number. That number appeared on three hundred pages. Someone who does not know better opens them one at a time. I would write SQL against the database, which is the kind of job a wrong condition can end a site with. Bulk find-and-replace, with a preview and an undo, turns that into ten minutes.

The admin you hand over should not be a noticeboard

Every plugin adds its own notice, its own advert, its own request for a rating. The admin you hand to a client stops being a place to work and becomes a wall of announcements. I used to clear it by adding code to the theme's functions file, and that code disappeared with the next theme update. To be permanent it had to live somewhere else.

The rest of the list is the same story

PHP limits, htaccess edits, changing the login URL, adding site-specific code, caching, redirects, favicons, database cleanup. None of it is exotic. All of it is what anyone building a WordPress site runs into sooner or later. But the answers were scattered across fifteen places: fifteen settings screens, fifteen update notices, and for a few of them, fifteen invoices.

One plugin instead of fifteen

Fifteen modules, one plugin, one price. Backup and restore, remote storage, SMTP, SSL, bulk find-and-replace, admin cleanup, PHP limits, htaccess editor, login manager, code injection, caching, popups, favicons, redirects, database cleanup and a language compiler. Every module can be switched off, so nothing you do not use is ever loaded. I built it for myself, and for anyone else installing the same list for the hundredth time.

See what you get

All fifteen modules are in every plan. The only difference is how many live sites you can use them on.