Netlify vs. Upsun

Any frontend hosting solution is just great. It's also available for users in China to access. I don't know if this will be a permanent fixture as it's more dependent on China, but our project requires access from China, and Vercel is not accessible there. Netlify is hugely CI-friendly, so I would also recommend it to anyone with a solid CI/CD workflow.

Incentivized

In our organisation we are the only team that uses Platform.sh to host any site. This was a cost effective way for us as we were using Acquia Cloud earlier for these websites. We mostly use Platform.sh for those sites which are always in development as it is simpler and faster to handle these operations in Platform.sh. Then we do a lift and shift to Acquia as we move more towards the go live and post production maintenance side.

Incentivized

• Hosting multiple websites and having multiple projects
• Updating the site by directly connecting to Github repository as new code is pushed
• Temporary deployment to show preview on GitHub pull requests

Incentivized

• As this is a PaaS it mitigates the complexities of a Cloud infrastructure like Acquia
• We are easily able to integrate our sites with different technologies like Python and Rest
• Helps us in providing Continuous Development cloud deployment hosting solution

Incentivized

• it is not aimed at it but first party laravel support would be nice.
• their free tier was so handy, i wish they start some similar efforts
• incorporate more WebOps mindset

Incentivized

• Platform.sh is not for beginners in my opinion. It has a good amount of learning curve in my opinion.
• As this is a PaaS, teams habituated with cloud infrastructure may miss the server side support from their cloud teams. I believe you will have to work on server bugs more on your own.
• During normal maintenance periods, integrations may fail if you are working on your sites in that time, in my experience.

Incentivized

Netlify is extremely user friendly while having several notable features including, but not limited to: - Managing deploys - Form integration - Domain management - Use of plugins From a user standpoint, they have made it incredibly easy to manage and review our websites deployment processes while incorporating the above optional features

Incentivized

To me, Netlify is the gold standard for static web hosting, but each alternative has specific situations where it might fit better. If building a Next.js site, then Vercel is the easiest solution for hosting. For Jekyll, GitHub Pages might make more sense. Other than that, I would turn to Netlify as my first choice for any static site hosting.

Incentivized

In our team we use Platform.sh mostly while sites are in developmental phase. Then we do a lift and shift to either Acquia or AWS depending on the type of sites we have. Platform.sh is really cost effective and more fluid in terms of Continuous Development hence the usage. After said development is done, we generally lift and shift to Acquia for more content heavy sites and to AWS for more transaction oriented sites.

Incentivized

• Netlify Platform has reduced our cost of additional server capabilities for PoC projects
• Netlify Platform has simplified CI CD pipelines for small standalone applications, thereby improving developer productivity
• Junior developers mainly working on Netlify Platform are often unable to get a low level understanding of server configuration, which is a drawback

Incentivized

• Continuous development for sites in build has been fluid
• Platform.sh is really cost effective when comparing to AWS or Acquia Cloud
• On the other side, lack of server side support demands a big learning curve from its users in my opinion.

Incentivized