Grav: which alternative fits your site?
Grav stores content in files and does not need a database.
Which PHP version does your site report?
We read only what your site already sends in public: the headers and the top of the homepage. No scan, no login.
More about this
It still runs on PHPPHP is a programming language that builds your web pages on the computer that hosts your site, just before they reach the visitor. WordPress runs on it..
If you also want to remove PHP from the public website, compare a static siteA static website is made of ready-made page files that the server hands over as they are, with no PHP code or database working behind the scenes. with how you currently create and publish pages.
First: do you need to move at all?
Leaving Grav is not a goal in itself. A site that works well and is kept up to date is a good site. Use these signs to see where you stand.
When staying is the better choice
- Your current way of creating pages works well.
- You want to keep using your existing content files.
- Someone maintains PHP, Grav and your extensions.
When moving on makes sense
- You want to publish ready-made pages without PHP.
- Your team needs a different editor.
- You want to replace the themes and extensions you use.
Worried about a PHP security issue? Read first what is going on, in plain language.
The options side by side
| Criterion | Stay and maintain it well | Move and upgrade | Switch to another CMS | Headless CMS with a fast front end | Static site, without PHP |
|---|---|---|---|---|---|
| Maintenance | Ongoing: keep PHP, the CMS, theme and plugins up to date | Ongoing, but on a version that still gets updates | Depends on the platform; on a hosted platform the provider does a lot | Low on the website itself; the CMS runs separately | Low: no PHP or plugins on the server |
| Security | Check versions, extensions and configuration | Check the supported version and configuration | Depends on the platform and how well it is kept up to date | Lower risk: the front end runs without PHP | Low risk: no PHP and no database on the server to keep updated |
| Cost, one-off | Low | Medium | Medium to high | High | Medium to high |
| Cost, ongoing | Medium: regular maintenance | Medium: regular maintenance | Medium: maintenance or a subscription | Low to medium, sometimes a subscription for the CMS | Low |
| Speed | Depends on hosting, caching and plugins | Often faster, thanks to newer PHP and hosting | Depends on the platform | Fast: pages are ready in advance | Fast: pages are ready-made |
| Edit content yourself | Just as you are used to | Just as you are used to | Yes, in a new environment you need to learn | Yes, in an editor | Limited: changes go through us or a simple editor |
| Migration effort | None | Small to medium: test, move, check | Large: move content, URLs and features | Large: build a new front end and connect the content | Medium to large: rebuild, keep URLs and set redirects |
Costs are shown as categories: low, medium or high, one-off and ongoing. The actual amount depends on the size of your site.
Each option in plain language
- Stay and maintain it well
You keep your current site and make sure PHP, Grav and every extension stay up to date. Often the wisest choice if your site works well and you really use its features. A security issue in PHP is solved with an update, not with a new website.
- Move and upgrade
You stay with Grav, but move to a PHP versionA PHP version is a numbered edition of PHP, like 8.3. Each edition is looked after for a limited time, then gets security fixes only, then nothing. that still gets updates, and to better hostingWeb hosting is the service that keeps your website's files on a computer that is always online, so visitors can open your site at any time. if needed. This fits when your site is stuck on an old version.
- Switch to another CMS
You choose another system, or a hosted platform where the provider does the maintenance. Check in advance how you would get your content out again later, and what it costs per month.
- Headless CMS with a fast front end
You manage your content in a CMSA content management system (CMS) is software that lets you edit the pages, texts and images of your website by logging in, without writing any code., but visitors see a fast front end that is separate from it. With many systems you can even keep your current one as the place where you edit.
- Static site, without PHP
Your site consists of ready-made pages, with no PHP and no database on the server. Little maintenance and fast, but less suitable if you change things daily or need many features on the server.
For a static setup, check how forms and search will work if you use them. Also test publishing an edited page. Having content in files does not by itself turn a site into a static website.
Choice helper: which route fits you?
Answer five short questions. You get a first direction straight away. Nothing is sent or stored.
Our first advice
Stay and maintain it well
Stay and keep your site in good shape. It does what it needs to do. Make sure PHP, the CMS and the extensions stay up to date, or have someone do that for you.
Move and upgrade
Stay with your CMS, but move to a version that still gets updates. You need its features, but an old version is holding you back.
Switch to another CMS
Look at another CMS or platform. Your site does not work the way you want, and you need a lot of features. First list what must keep working.
Headless CMSA headless CMS is a system for editing content that has no website attached; a separate front end takes the content and builds the pages visitors see. with a fast front end
A headless CMS with a fast front end. You change things often, but need few heavy features on the server.
Static site, without PHP
A static site without PHP. You change little and need few features on the server. Then less maintenance is a real gain.
Not sure which version you run? Do the free Exposure Check first.
This is a first direction, not a final verdict. We are happy to look at your situation with you. Ask for advice on your site.
We build each of these alternatives
We have no favourite route. We help you choose, and then we carry out what fits, even if that means you stay where you are.
Stay and update
Your site on a PHP version that still gets updates, tested before and after.
from £415
Move, upgrade or switch
To new hosting and a supported PHP version, or to another system, with your content and URLs.
from £835
Headless or static
A new front end without PHP, with or without a CMS for editing.
from £2,055
From prices, excluding VAT. The final price follows a 15-minute triage.
Frequently asked questions
Is Grav unsafe?
The CMS name alone does not tell you whether your site is secure. Have your installed versions, extensions and configuration checked. Read the PHP status page for sourced information about PHP issues.
What is the best alternative to Grav?
There is no best for everyone. If your site works well and you use its features, staying and updating is often best. If you change little, a static site saves a lot of maintenance.
Use the choice helper on this page for a first direction.
Will I lose my place in Google if I switch?
Not if the move is done well. We take your pages and URLs along and set redirects for addresses that change, so visitors and search engines end up in the right place.
What does switching cost?
That depends on the route and the size of your site. Each service below shows a from price. You hear the final price after a short triage, before we start.
Is Grav already a website without PHP?
No. The official Grav documentation lists PHP as a requirement, even without a database. A static setup builds pages in advance.
Check separately which services handle any forms and search functions.
Which official source was used?
Official documentation: https://learn.getgrav.org/17/basics/requirements (accessed 22-10-2026). Always check the requirements for your installed version.