When people compare hosting plans, they look at what is included — how much CPU, how much space, whether SSL comes with it.
But what makes you regret a choice in daily use is never a missing spec. It is the day you want to do something and find that the environment will not let you.
So this article is written the other way round: every limit of a fully managed environment, listed one by one. By the end you should be able to tell whether you will run into any of them.
The 30-second version
| Question | Answer |
|---|---|
| Why are there limits | A uniform environment is what makes automated operations possible — it is a trade |
| Most common hard requirement | IP allowlisting, unusual PHP extensions |
| Can you install any plugin | Yes, WooCommerce included |
| Can you take your data with you | Yes, and you should confirm it once up front |
| How to tell if it affects you | See whether any line in the list makes you think “ah, I need that” |
Why managed hosting always has boundaries
To be clear up front, this is not a vendor being stingy.
Fully managed hosting can update, back up and automatically restart things for you only if the environment is uniform. The system can apply one set of operational procedures to every instance only because it knows what each instance looks like.
If everyone could change the underlying configuration at will, there would be no “automatic” left — every update would start with checking what you had changed. This is a trade: you give up some control in exchange for not running operations yourself.
Once you see the trade, every limit below makes sense.
The actual list of limits
| What you cannot do | Who cares |
|---|---|
| SSH in and change system settings | Developers who deploy from the command line |
| Compile or install PHP extensions yourself | Anyone needing an unusual payment SDK or image processing library |
| Edit the web server configuration files | Anyone writing complex redirect or custom caching rules |
| Run anything other than WordPress in the same instance | Anyone who wants to tuck a Node.js service or a scraper alongside it |
| Connect to a corporate intranet or pin a fixed outbound IP | Anyone integrating an internal ERP, or whose counterparty requires IP allowlisting |
| Choose your own PHP or database version | Old plugins that only run on an older version |
But these limits do not apply to most sites
Let us be honest: that table looks long, but the vast majority of WordPress sites will never hit a single line of it.
Blogs, company sites, portfolios, ordinary WooCommerce stores — everything those sites need is in a standard WordPress environment. Install plugins, switch themes, attach domains, exactly as you would self-hosted.
The cases that do hit a boundary are usually these, and you generally know it already:
- The system you need to integrate requires IP allowlisting. Many internal corporate systems and bank payment gateways require a fixed source IP, and this is the most common genuine obstacle in a managed environment.
- You depend on a plugin that needs an unusual extension. Some long-established Taiwanese payment and e-invoice plugins have requirements like this.
- You want to run other services on the same machine. That situation calls for a VPS in the first place; it is not that managed plans are bad.
The test is simple: if you read that table and no line made you think “ah, I need that”, you will not run into it.
The most asked question: can I take my data out
This is the most practical of all managed hosting worries, so here is the direct answer: yes, and you should confirm it once before you ever need to.
WordPress’s portability comes from its architecture — site content lives in the database, uploaded files live in wp-content/uploads, and themes and plugins sit in standard directories. Get those three and the site can be rebuilt anywhere.
To judge whether a managed service will lock you in, check three things:
- Whether you can export the complete database yourself
- Whether you can obtain all the files in
wp-content - Whether the domain is registered in your own name
If all three are true, you can leave whenever you want. This is also why we recommend buying your own domain — who holds the domain decides whether migrating takes an afternoon or takes asking someone for a favour.
What you get in exchange
That is the limits covered; to be fair, here is the other half of the trade.
The value of managed hosting is not in normal times, it is when something goes wrong. A core update wrecks the layout, a plugin conflict causes a white screen, database connections max out, a scanner starts attacking you — on a self-hosted setup those events are your weekend; on managed hosting someone has already handled them, or there is a restore point to go back to.
There is one more thing that is easy to underrate: a uniform environment means problems are predictable. Whatever you hit, someone else has hit, and the fix is known. Every self-hosted machine is unique, so when something breaks there is no precedent to follow.
How to decide
| Your situation | Recommendation |
|---|---|
| You read the list of limits and none of it applies to you | Managed — you are not paying for freedom you would not use, and you save the operations work |
| You need IP allowlisting or an unusual extension | Self-hosted — this is a hard requirement with no way around it |
| You want several services on one machine | Self-hosted — managed plans are not designed for that |
| You are not sure whether special needs will come up later | Start managed — WordPress is highly portable, so migrate if you genuinely hit a wall; that costs far less than shouldering operations now |
That last row is the most common situation in practice. Taking on operational costs today for a requirement that has not happened yet is usually a bad deal.
WordPress hosting at RoamerHost: WordPress Basic at NT$3,588/year (avg. NT$299/mo) (1.5 vCPU / 10 GB) and WP × Roamer AI Pro at NT$11,988/year (avg. NT$999/mo) (2 vCPU / 10 GB, plus Business-tier Roamer AI access, so the AI goes into your site to edit and manage it for you). Plugins and themes install completely freely, WooCommerce included, with no installation restrictions.
FAQ
Q: Can I edit php.ini or wp-config myself?
The dashboard lets you adjust the common parameters. But requirements that involve compiling extensions yourself or changing server-level configuration are not supported in a managed environment — that is the price of a uniform environment.
Q: My payment integration needs a fixed IP. What now?
This is the most common genuine obstacle in a managed environment. Many internal corporate systems and some payment gateways require source IP allowlisting, and that case needs a VPS. It is not a question of whether a managed plan suits you; it is architecturally impossible.
Q: Can I run other services in the same instance?
No — one instance is one WordPress. Running n8n or Dify means a separate subscription for each, and the upside is that they are completely isolated from each other.
Q: Will I be locked in if I want to leave later?
No, and we recommend confirming it once before you need to — whether you can export the full database, whether you can obtain wp-content, and whether the domain is registered in your name. If all three are true, you can leave at any time.
Q: I am not sure whether I will have special requirements later
Then start with managed hosting. WordPress is highly portable, so migrate if you genuinely hit a wall; that costs far less than shouldering operations yourself now. Paying operational costs in advance for a requirement that has not happened is usually a bad deal.
Sources and further reading
WordPress ecosystem specs and best practices are as documented officially:
- WordPress official user documentation
- WordPress developer documentation — technical specs for plugins and themes
Further reading
- How long before you know your site is down: which pages to monitor
- Self-hosted vs managed WordPress: a cost table that counts maintenance time
- Hosting requirements for a WooCommerce store: why ordinary WordPress hosting falls short
- WordPress hosting FAQ: plugins, PHP settings and troubleshooting
- Attaching a custom domain to WordPress: DNS settings and SSL certificates
- RoamerHost managed WordPress plans
Want someone to build it for you?
When requirements go beyond what plugins can do, someone has to touch code. Roamer Tech takes on advanced WordPress development:
