The agency sysadmin trap works like this. To protect your margins you run your own VPS cluster, or you spread client sites across five hosts, and then you spend your best hours keeping all of it breathing. WordPress.com for Agencies is the pragmatist’s way out of that, and it is what I keep pointing agencies toward when they are drowning in infrastructure they never wanted to own.
I have spent 14 years debugging race conditions and clearing broken transients at 3 AM because a cheap server ran out of inodes. So the LUBUS story landed with me. Ajit Bohra has been doing this since 2008, and he moved 80% of his agency’s projects onto the WordPress.com ecosystem. His reasoning is hard to argue with: nobody hires an agency for its server administration.
What WordPress.com for Agencies actually buys you
Mostly it buys standardization. When LUBUS moved to WordPress.com for Agencies, they got one platform and one workflow across every client site, with automated backups and one-click rollbacks underneath. The Jetpack Activity Log is the first place I look when a client swears nobody touched anything.
I have watched junior devs lose days trying to reproduce a production bug on their laptop. WordPress Studio takes most of that away. You work locally, sync to the cloud, and keep the custom logic in GitHub, which gives you a CI/CD pipeline that nobody has to babysit. Clients can also open a support ticket directly, so you are no longer the middleman for basic troubleshooting.
From local to production
The efficiency people credit to WordPress.com for Agencies is really this workflow. Every LUBUS developer starts in a local environment synced through Studio, and nothing reaches the live server until it has been signed off in staging. For custom block prototyping they use AI tools like Telex to get a working demo out faster.
Custom functionality still has to stay decoupled from the host. When I build blocks or client logic on this stack, I use filters to keep the admin UI narrow, so a curious client cannot update the one plugin the whole site leans on. Something like this:
<?php
/**
* Prefix: bbioon_
* Logic: Prevent specific plugins from being updated by non-technical users
*/
add_filter( 'plugin_install_action_links', function( $action_links, $plugin_meta, $plugin_file ) {
$protected_plugins = [ 'my-custom-logic/custom-logic.php' ];
if ( in_array( $plugin_file, $protected_plugins ) && ! current_user_can( 'manage_network' ) ) {
return []; // Remove 'Update' and 'Delete' links for non-admins
}
return $action_links;
}, 10, 3 );
AI is growing the consulting side
Ajit’s read on AI is that it makes clients smarter rather than developers redundant. They arrive with clearer briefs because they have already prototyped the idea themselves, which pushes the agency toward architecture and away from assembly work. On WordPress.com for Agencies that shift is easier to make, since SSL renewals and security patches are someone else’s job.
If moving to WordPress.com for Agencies is eating your dev hours, hand it over. I have been wrestling with WordPress since the 4.x days and I know how to get a messy legacy site onto a managed stack without a rewrite.
I have written more on managed WordPress hosting, and on how Automattic for Agencies fits a WooCommerce workflow.
Ship better, sleep more
Stop playing sysadmin. Your agency gets paid for work the client can see, not for tuning Nginx at midnight, and WordPress.com for Agencies moves that entire category of work off your desk. The margin you were protecting by self-hosting is usually smaller than the hours it quietly costs you.
If you want to look at it yourself, the WordPress.com for Agencies page lays out how it fits into a stack. It is the same setup LUBUS runs its client work on.
