WordPress often gets discussed as if the choice is already settled: either you love it, or you believe modern stacks should have replaced it long ago.
That is not a useful way to evaluate it. The practical question is simpler: when does self-hosted WordPress still solve a real business problem better than the alternatives in front of you?
In many cases, it still does.
When WordPress is still a practical choice
Self-hosted WordPress makes sense when you need:
- a controllable content platform;
- a familiar admin interface for non-technical users;
- broad plugin and theme flexibility;
- ownership of hosting, backups, and surrounding infrastructure;
- the ability to shape the stack around your own operational preferences.
That is especially relevant for small businesses, content-heavy sites, internal publishing teams, and operators who want a mature CMS without turning content management into a custom software project.
Why self-hosted WordPress still survives
Content teams can use it without a large implementation cycle
A practical CMS has to be usable by the people who publish content, not just by the people who deploy containers.
WordPress still works because it lets teams move quickly on content, structure, and plugins without requiring an engineering-heavy workflow for every small change.
The ecosystem is still enormous
In infrastructure terms, ecosystem depth is not a weakness. It is one of the reasons WordPress remains operationally useful. There are still many situations where plugin availability, community familiarity, and hosting flexibility outweigh the appeal of moving to a newer platform.
Self-hosting restores control over the stack
This is where the decision becomes more interesting for infrastructure-minded teams.
When you self-host WordPress, you control:
- where the site runs;
- how traffic is exposed;
- how backups are handled;
- which reverse proxy or TLS layer sits in front;
- how the database is maintained;
- how the rest of the stack connects to it.
That makes WordPress a better fit when the website is part of a broader infrastructure strategy rather than a standalone SaaS purchase.
When WordPress is a bad fit
Self-hosting WordPress is not automatically the right answer.
It becomes less attractive when:
- the site should really be static and rarely changes;
- plugin risk and long-term maintenance are unacceptable;
- the organization wants a very constrained publishing model;
- the site is only one small page and a CMS is unnecessary.
In those cases, a static site or another simpler deployment model may be cleaner.
Where WordPress fits in this stack
WordPress becomes more compelling when the rest of the environment is already self-hosted.
For example, it fits naturally beside:
- When Self-Hosted MySQL Is Still the Practical Choice as the application database;
- When Self-Hosted Caddy Is Enough for Your Reverse Proxy Layer for clean publishing and TLS;
- When Self-Hosted Authentik Becomes Worth It if surrounding admin or internal services need stronger access patterns;
- When Self-Hosted n8n Is the Better Choice when you want automation around content or form-driven workflows.
This is where WordPress stops being “just a website” and becomes part of an operational stack.
A practical starting point
If you want a reusable baseline, start with AiratTop/wordpress-self-hosted.
The repository includes:
- WordPress itself;
- MySQL as the database;
- phpMyAdmin for administration;
- WP-CLI for operational and content tasks;
- persistent storage for both WordPress files and database data;
- a sample
Caddyfilefor use behind a reverse proxy.
That combination is useful because it supports both day-to-day site management and surrounding infrastructure integration.
What the real trade-off looks like
The real trade-off is not “WordPress versus modernity.” It is:
- faster content operations and a mature ecosystem;
- versus plugin discipline, patching, and CMS maintenance responsibility.
If your team can accept that maintenance responsibility, WordPress often remains a very efficient way to run a controllable site.
Summary
Self-hosted WordPress still makes business sense when you need a mature CMS, want infrastructure control, and value a publishing workflow that non-technical users can operate.
It is not the right default for every website. But when the site is content-driven and the stack around it already matters, WordPress is still one of the most practical options available.