Rails today: what should you reasonably expect from a host?
Rails 7/8 expects recent Ruby, precompiled assets, Active Job and often PostgreSQL + Redis. Few generic PHP hosts cover that scope without PaaS or a dedicated VPS.
Independent tests, comparisons and explainers on European web hosting — updated regularly.
No results for this search
Rails 7/8 expects recent Ruby, precompiled assets, Active Job and often PostgreSQL + Redis. Few generic PHP hosts cover that scope without PaaS or a dedicated VPS.
Gunicorn behind nginx, `collectstatic`, env vars, migrations and separate media — the Django prod path fits in a few steps, provided you do not skip collectstatic.
Node runs as a long-lived process, not an ephemeral PHP request. PM2, reverse proxy, environment variables and listen port change everything — from the first Express or Nest app.
Gandi remains rooted in domains and sober hosting. Alwaysdata offers a multi-language platform with SSH and instant scaling. For a developer who refuses cloud complexity, the right pick shows up in runtimes and support.
Symfony needs recent PHP, Composer, OPcache and often Redis or async Messenger. A host advertising PHP without these signals leaves you alone on cache warmup.
Laravel in production is not "a VPS with PHP." `.env`, queue workers, scheduler, Octane or FPM, and permissions are separate from the machine that runs them.
Shopify buys simplicity and platform maintenance. Self-hosted buys data control, custom checkout and margin — plus operations overhead.
IONOS and Contabo both advertise low-price VPS in Germany, but one sells a full ecosystem with renewal traps while the other packs massive resources with limited support. The trade-offs are not the same.
Magento (Adobe Commerce / Open Source) needs RAM, cache, indexing, and dedicated operations. Treating Magento like oversized WordPress leads to predictable outages.
With 50,000 SKUs, PrestaShop does not always slow down from CPU alone. Database, indexing, cache and third-party modules often set the ceiling long before the host.
Black Friday needs occasional elasticity, not an oversized server twelve months a year. Cache, queues, payment and monitoring beat an idle dedicated machine.
Infomaniak bets on Switzerland, documented ecology and 24/7 French support. o2switch offers unlimited shared hosting in France at a single price. For an SME, the right pick depends mainly on data location and site complexity.
Core, theme and plugins update continuously. Without staging, tested backup and execution order, production becomes the only test environment — with outages to match.
A WordPress multisite network simplifies running several sites — if you settle domains, SSL, plugins and backups before the first clone goes live.
Changing host rarely fixes a poorly optimised WordPress site. Slowness often comes from theme, plugins, database or cache — not just the server.
Scaleway and Clever Cloud both target technical teams in France, but one sells infrastructure to configure and the other a deploy-ready PaaS. Time saved depends mostly on what you agree to stop controlling.
Managed WordPress hosting outsources updates, cache and backups — but rarely your broken plugins or custom code. Here is what you actually buy.
Managed or self-managed is not budget alone. It is a clear split of who patches, monitors, restores, and answers at night when production falls.
Dedicated hardware is not hosting's mandatory summit. It is justified by physical isolation, steady load, or regulatory constraints — not prestige.
Two European pillars: Hetzner for price-performance and autonomy, OVHcloud for the French ecosystem and support. Scenario comparison, limits and decision grid for European apps.
Cloud is expensive when load is flat. It pays off when your spikes exceed what a fixed server can absorb without wasting resources the rest of the year.
Moving to a VPS is not about prestige. It is the point where shared hosting no longer guarantees what your site needs — isolation, versions, cron, restore.
For a brochure site or blog just getting started, shared hosting is often the right first step — if you know when it becomes a constraint rather than a saving.