@steev It seems that two concepts are being mixed: ‘static sites’ and ‘flatfile CMS’.
These extra ‘services’ mostly come with a generous free starter license, but do have a licensing model when outgrowing the starter-level.
Grav on the other hand is a ‘flatfile CMS’. It uses a PHP server (like Wordpress does) to process logic, eg. processing a contactform. Unlike Wordpress, Grav does not use a database for storing pages/posts, users, configuration and data, but uses flat text files. Hence the name ‘flatfile CMS’.
Which means that…
- All configuration is in flat files which can easily be read and written with any editor.
- All pages/posts are in flat files which can easily be read and written with any editor.
- The entire site can be versioned using git and GitHub. ‘Mistakes’ can therefor easily be rolled back.
- Backup is easy since everything is a simple flat file.
- There is no performance overhead of a heavy database.
- Installation is as easy as unzipping a zipfile.
And like Wordpress:
- There is an Admin panel to edit configurations, users and pages/posts.
- There is a PHP server to process logic for handling requests and responses.
- Contact forms can be handled like with Wordpress.
- External API’s can easily be called and results be processed.
Other advantages of Grav over Wordpress:
- It is (relatively) young and fresh which means:
- It is build on the latest frameworks and technologies. This makes Grav small and flexible.
- It does not carry the overhead of 10 years backwards compatibility like Wordpress does. This makes innovation a lot easier.
- Results of page processing are cached and reused, which increases performance.
Considering the limited requirements you have mentioned:
- I see no red flags for a conversion to Grav.
- I see the following bumps for running your site as a static site at Netlify:
- The contact-form needs extra attention and a 3rd party for emails.
Hope this helps…