Start project
Start project

Jamstack Hosting and Cloud Deployment Platforms

Discover a couple of Jamstack hosting and cloud deployment platforms favored by the community.

Written by:
  • Thom Krupa

    Thom Krupa

Last update: November 17, 2020
hero image

Table of Contents

Learn about Cloud Hosting

In the past few years, hosting solutions and CDNs have become much more than just a place on the internet, offering additional features to help you with deploying a modern website or an app. This gave birth to a new bread of hosting platforms like Netlify, Vercel, AWS Amplify, Firebase, etc.

Let’s say you went for Jamstack web dev architecture for your website or app project, and all of the coding is done. It’s time to find the best place to host it, right? Well, wrong. You really should have done this before.

But don’t worry, because, with static files that you’re about to serve pretty much any host can do the work.

However, not all of them are built with Jamstackers👨‍💻 in mind.

What is a static website?

To put it as simply as possible, a static website is a website made up of HTML pages with pre-populated content. Click here for a bit of an in-depth explanation.

What’s that Jamstack thing again?

Since you are here, reading this article, there’s a strong possibility you’ve already heard about the concept of Jamstack. It is more than a trend for web developers to move from dynamic server-side apps to client-side stacks. It is a shift change from the backend to the more powerful frontend that eases the dev workflow.

The best practices most devs would agree on, that define a Jamstack project, are: atomic deploys, automated builds, building and hosting are decoupled, site/app is on a CDN, instant cache invalidation, and content updates are pushed through Git or an API CMS (not really a necessity but it sure helps with multiple teams/edits, etc.).

Typical Jamstack build

For example, for a typical Jamstack website, you’ll need to use:

  • Static Site Generator. An SSG is a tool that builds static HTML pages out of the input content, whether it’s taken from a CMS or a built-in template. There’s a considerable number of SSGs suitable for almost any programming language.
  • Headless CMS. They serve as your content keepers. The fantastic thing about headless CMSs is that they decouple content management from your front end. Thanks to that, you can deliver your content beyond websites and apps and repurpose it from many different frontends.
  • [Optional] A JavaScript framework of your choice. Some SSGs like Gatsby or Next.js are built on top of React.js. Others like Nuxt and Gridsome use Vue. Others like 11ty or Hugo don’t use any specific JS framework.
  • Hosting and deployment solution.

Essential parts

The essential parts of every hosting provider are:

  • Continuous integration (CI) is a practice to merge all changes and branches to the main branch as often as possible. By doing so, you’re avoiding integration issues that can happen on the big release day. Push change, build preview, test, and finally deploy to production.
  • Continuous delivery (CD) is the ability to deliver an app anytime. In practice, it means you use git and have a build pipeline connected with deployment to server or CDN.
  • Content Delivery Network (CDN) is a global, distributed network of proxy servers and data centers.

A modern deployment platform is a tool that combines all of the above practices and features. It enables developers to ship apps safely and quickly with no need for a dev-ops team and infrastructure maintenance. Connect git repository and start building.

What is Cloud Deployment?

Cloud deployment is defined in terms of service models and deployment models. Read more about it here.

Fight for the developers

Deployment platforms evolve these days very quickly. The main reason is the number of tools and the growing popularity of serverless and Jamstack.

Every big corp cloud provider has its solution. Amazon has Amplify. Google has Firebase. Microsoft recently launched Static Web Apps, and Cloudflare launched Pages. It is a very competitive space in which companies fight for new users offering different products and approaches.

Essential parts, CI/CD and CDN, are no longer a feature. Those are must-haves that developers expect to have for free. Most of the tools we describe in this post support serverless functions. Some have analytics, other authentication, databases, and/or form handling built-in. All of them fight for developers’ attention improving the experience and introducing more and more new features.

What is CI/CD?

CI/CD refers to the combined practices of continuous integration and continuous delivery or continuous deployment in software development. To understand it better, take a look at this page here.

The best hosting and deployment solutions

Jamstack hosting options utilize the concept of serverless architecture (a system of running websites and applications without infrastructure management). They rely on third-party cloud-hosted services, like AWS, Google Cloud Platform, etc. The hosts carry out all server management, as the users pay a provision.

Having said that, let’s take a look at the ready-to-use hosting and deployment solutions for Jamstack projects that we’ve had the pleasure of working with. Reviews are there to walk you through what each solution offers. The pros and cons, if you will. But if you need a deep dive into available options and how they stand against each other, we’ve made a simple host compare tool to help you with that.

Jamstack hosting reviews

In the past few years, hosting solutions and CDNs have become much more than just a place on the internet, offering additional features to help you with deploying a modern website or an app. This gave birth to a new bread of hosting platforms like Netlify, Vercel, AWS Amplify, Firebase, etc.

Let’s say you went for Jamstack web dev architecture for your website or app project, and all of the coding is done. It’s time to find the best place to host it, right? Well, wrong. You really should have done this before.

But don’t worry, because, with static files that you’re about to serve pretty much any host can do the work.

However, not all of them are built with Jamstackers👨‍💻 in mind.

What is a static website?

To put it as simply as possible, a static website is a website made up of HTML pages with pre-populated content. Click here for a bit of an in-depth explanation.

What’s that Jamstack thing again?

Since you are here, reading this article, there’s a strong possibility you’ve already heard about the concept of Jamstack. It is more than a trend for web developers to move from dynamic server-side apps to client-side stacks. It is a shift change from the backend to the more powerful frontend that eases the dev workflow.

The best practices most devs would agree on, that define a Jamstack project, are: atomic deploys, automated builds, building and hosting are decoupled, site/app is on a CDN, instant cache invalidation, and content updates are pushed through Git or an API CMS (not really a necessity but it sure helps with multiple teams/edits, etc.).

Typical Jamstack build

For example, for a typical Jamstack website, you’ll need to use:

  • Static Site Generator. An SSG is a tool that builds static HTML pages out of the input content, whether it’s taken from a CMS or a built-in template. There’s a considerable number of SSGs suitable for almost any programming language.
  • Headless CMS. They serve as your content keepers. The fantastic thing about headless CMSs is that they decouple content management from your front end. Thanks to that, you can deliver your content beyond websites and apps and repurpose it from many different frontends.
  • [Optional] A JavaScript framework of your choice. Some SSGs like Gatsby or Next.js are built on top of React.js. Others like Nuxt and Gridsome use Vue. Others like 11ty or Hugo don’t use any specific JS framework.
  • Hosting and deployment solution.

Essential parts

The essential parts of every hosting provider are:

  • Continuous integration (CI) is a practice to merge all changes and branches to the main branch as often as possible. By doing so, you’re avoiding integration issues that can happen on the big release day. Push change, build preview, test, and finally deploy to production.
  • Continuous delivery (CD) is the ability to deliver an app anytime. In practice, it means you use git and have a build pipeline connected with deployment to server or CDN.
  • Content Delivery Network (CDN) is a global, distributed network of proxy servers and data centers.

A modern deployment platform is a tool that combines all of the above practices and features. It enables developers to ship apps safely and quickly with no need for a dev-ops team and infrastructure maintenance. Connect git repository and start building.

What is Cloud Deployment?

Cloud deployment is defined in terms of service models and deployment models. Read more about it here.

Fight for the developers

Deployment platforms evolve these days very quickly. The main reason is the number of tools and the growing popularity of serverless and Jamstack.

Every big corp cloud provider has its solution. Amazon has Amplify. Google has Firebase. Microsoft recently launched Static Web Apps, and Cloudflare launched Pages. It is a very competitive space in which companies fight for new users offering different products and approaches.

Essential parts, CI/CD and CDN, are no longer a feature. Those are must-haves that developers expect to have for free. Most of the tools we describe in this post support serverless functions. Some have analytics, other authentication, databases, and/or form handling built-in. All of them fight for developers’ attention improving the experience and introducing more and more new features.

What is CI/CD?

CI/CD refers to the combined practices of continuous integration and continuous delivery or continuous deployment in software development. To understand it better, take a look at this page here.

The best hosting and deployment solutions

Jamstack hosting options utilize the concept of serverless architecture (a system of running websites and applications without infrastructure management). They rely on third-party cloud-hosted services, like AWS, Google Cloud Platform, etc. The hosts carry out all server management, as the users pay a provision.

Having said that, let’s take a look at the ready-to-use hosting and deployment solutions for Jamstack projects that we’ve had the pleasure of working with. Reviews are there to walk you through what each solution offers. The pros and cons, if you will. But if you need a deep dive into available options and how they stand against each other, we’ve made a simple host compare tool to help you with that.

Jamstack hosting reviews

Further reading

Compare Cloud Platforms

vs
Compare!

Superheroes stack

Discover More