Netlify CMS is well suited when you have very less frequent updates to your content, maybe once a day and very few people need to access your data. You can connect it to Netlify, GitHub, or any platform and have multiple people access it and do as many updates as you wish, but the process is not well-defined and you need to build your own system for that. It is well suited for projects you need to pull off with very low cost, it is essentially free as the software is open source and free to use, and all you need to do is set up your schema correctly and find a deployment pipeline where you can build your static site/API to redeploy whenever the content changes. I personally used a GitHub Login -> Netlify CMS -> next app consumer of content -> GitHub pipelines to run next SSG -> GitHub Pages to deploy the built static site. It might not be appropriate for large teams where users themselves need no-code tools to modify the schema of the content.
TYPO3 is great if you need to connect some systems in company to work together: like ecommerce + CRM + ERP + MRP and build an Extranet for partners/dealers where they can order your products, see particular BOM (bill of material), paid/unpaid invoices and use email marketing on top of it. You can do it but keep in mind that you will need a dedicated hosting, well organized admin(s) and some handwritten code. For simple blog TYPO3 is also a good choose, but WP would be better I think.
compared do Wordpress - far less community support
when you run a simple blog - it is simple as piece of cake. But if it is a large news site, with many user roles, extensions and permissions - it may be hard to find an admin that will organize and keep that stuff working.
server resources: so you want performance and speed with all that modules enabled? make sure that you have dedicated server in most cases. WP works much better here.
We really can't compare it to full-fledged CMS software, like WordPress, which has a lot of community and support with widgets, plugins, and whatnot. It's not built for that, but you can compare it to Contentful, Ghost, Strapi, etc., which provide similar functionality to a headless CMS with custom schema options, but even among them, it still lacks a lot of functionality, ease of use, and support. But Netlify CMS pros would be of the opinion that compared to other platforms where most schemas need to use their own tools and frameworks, it's very cost-effective. Something new called TinaCMS has come up to compete with Netlify CMS by covering most of its shortcomings, but it's something new being built by the same team that built Forestry CMS and comes with many modern features, yet currently only supports NextJS SSG.
