Statamic hosting requirements: what your server needs

From Statamic’s requirements page, checked on 30 October 2026. To check a server, run php -v and php -m, and compare the output with the list.

From Statamic’s release schedule and support policy, which notes the dates can shift with Laravel’s schedule. The latest Statamic 6 package on Packagist narrows Laravel 12 down to 12.40 or later.

The point for hosting: you need a host that lets you change PHP version without moving server. The Statamic 7 row shows PHP 8.3 leaving the range, and a host pinned to one PHP version will force a migration on you just when you want to upgrade.

1. Which PHP versions can we select, and how soon do new ones arrive?
2. Do we get SSH access, Composer and the ability to run php please commands on deploy?
3. Can we set the web root and add rewrite rules? Full static caching needs them.
4. Can a deployment run from Git?
5. Can the site’s PHP process write to its content and storage folders?
6. What’s backed up, how often, and has anyone tested a restore?
7. Where is the server, if your data has to stay in a particular place?

Statamic’s Laravel Forge guide mentions Laravel VPS, DigitalOcean, AWS, Hetzner or your own fresh Ubuntu server as hosting options under Forge. The site can also be deployed as a static site, in which case the host’s job is much smaller, but anything that needs PHP at runtime has to be handled another way.

Before paying for a bigger server, look at static caching. Statamic documents two levels:

Pages shown to logged-in members need care, since protected pages are left out of caching and whatever renders first is cached for everyone else. Statamic recommends warming the cache after deployment with php please static:warm.

• The Stache. It is Statamic’s content index. Statamic’s v5 docs describe it checking files for changes on each request while its watcher is on, and recommend turning the watcher off in production.
• Zero-downtime deployments. Statamic’s guide warns against sharing a Stache cache between releases, because it can store absolute paths. Give it its own cache store.
• Eloquent driver. If you use it, the Forge guide suggests replacing stache:warm with cache:clear in the deploy script.
• Several app servers. With the half measure, the lock store needs a shared driver such as Redis or Memcached, because the default file driver only locks within one server.

Add your hosting quote to the Statamic cost calculator. If the upgrade is what brought you here, the framework matters too, and we have a Laravel version table. For help choosing and setting up, see our Statamic development page.