Airbrake's Advice on Which PaaS App is Right For Your React Project
Tags: react, javascript
Published: 2022-10-06 15:36:44


Serverless platforms are quickly evolving, and new ones are emerging as the industry is helping unleash React developers' creative powers by removing the burden of Ops from their plates. With so many options, it can be challenging to know which Platform as a service you should go with to deploy your React project. 

In this article, we'll explore the top 6 Serverless PaaS options available on the market (along with one bonus one!). We'll also offer recommendations for which one you should go with, depending on what you want from your PaaS. 

## PaaS Should Have These Three Elements

Before we offer recommendations, let's talk about the three elements we felt needed for a serverless PaaS for an emerging React project. 

First, it should be easy to get started: you should be able to work and deploy directly from a Git repo.

Second, it should be free to start—but scalable enough to support real-world production usage and commercialization.

Third, it should be easy to operate: you should be able to A/B test your site and have analytics capabilities.

With that in mind, we created the following chart with our [PaaS scoring system](https://7307809.fs1.hubspotusercontent-na1.net/hubfs/7307809/Airbrakes%20Serverless%20PaaS%20comparison.pdf). 

For more information, you can also check out our blog post, "[Best Serverless Platforms to Deploy Your React App](https://bit.ly/3CxU75F)"

## You should go with this PaaS if...

There's no one size fits all solution, but we've got some recommendations based on which scenario we think these platforms will stand out for your app. 

**Go with Netlify if...**
You want a simple, all-encompassing experience with a strong community and built-in analytics but don't need to be part of that community.

**Go with Vercel if...**
You want a simple, and all-encompassing experience with built-in app analytics and want to be part of a community.

**Go with AWS Amplify if...**
You are already using the AWS ecosystem and/or are looking to scale out your app significantly with features and scale.

**Go with Cloudflare Pages if...**
You want a capable experience focused on availability and performance but can forego some simplifying options such as plugins or app templates.

**Go with Render if...**
All you need is a bare-bones service that offers technical options and flexibility. 

**Go with Fly if...**
You love simplicity, and you're not at the point of scaling. 

**(Bonus) Go with GitHub Pages if...** 
You have no plans to commercialize your project and only need a simple static hosting site. 

## What to do next

We hope this blog gave you a better idea of which PaaS might be suitable for your React project. 

With that, here are some next steps: 

Create an account with the PaaS of your choice.

Deploy your app using these get started documentation: 

- [Get Started with Neflify](https://docs.netlify.com/get-started/)
- [Get Started with Vercel](https://vercel.com/docs/concepts/get-started) 
- [Get Started with AWS Amplify ](https://www.googleadservices.com/pagead/aclk?sa=L&ai=CW5uYnM0pY6PaDIqWogbUuK-4CoeD9cFsrIigi9IP35z5ieovCAAQASC5VGDJ5piN7KSAEKABj8CR-wLIAQHIA9ggqgReT9Arg1XS5Ohyqu7o04Fl3OT7crgBkYAz68MyT8NOY4n2dWwbIviBzMkeUgDuhMce45xFcgXKQVOKk9pkvKpgRVwhVzKWu1rOkDs0ERfdIOG9SA0XXBtJYx7Pt8khz8AEpdiog_UDgAWQTogFkZz-9z3ABQSgBmaAB9m_7oQBiAcBkAcBqAemvhuoB7masQKoB_PRG6gH7tIbqAf_nLECqAfK3BuoB4-psQKoB9imsQKgCLzopQSwCAHACAHSCAwQAiCEATICg0A6AQCaCS9odHRwczovL2F3cy5hbWF6b24uY29tL2FtcGxpZnkvZ2V0dGluZy1zdGFydGVkL7EJmLNY5vNbTxG5CeHDDRyxuffc-AkBigqhAmh0dHBzOi8vcGl4ZWwuZXZlcmVzdHRlY2gubmV0LzQ0MjIvY3E_ZXZfc2lkPTMmZXZfbG49YW1hem9uJTIwYW1wbGlmeSZldl9seD1rd2QtMTY0MzM4MjcyMjE0MyZldl9jcng9NTg4OTcxMTM4MzU5JmV2X210PXAmZXZfbj1nJmV2X2x0eD1zbCUzQUdldCtTdGFydGVkK1dpdGgrQW1wbGlmeSZldl9wbD0mZXZfcG9zPSZldl9kdmM9YyZldl9kdm09JmV2X3BoeT05MDA4MTg4JmV2X2xvYz0mZXZfY3g9MTY2MjYxOTE4ODkmZXZfYXg9MTM0NDkzMTIxNTczJmV2X2VmaWQ9e2djbGlkfTpHOnMmdXJsPXtscHVybH2YCwHaCwsIHxDBi_2RhgEYAeALAaoMAggBuAwB6AwGghQSCAISDmFtYXpvbiBhbXBsaWZ5iBQFyBSn25_5nZ6sozHQFQH4FgGAFwGSFwgSBggBEAMYZw&ae=2&ved=2ahUKEwim_OzsyaP6AhViElkFHdo8AjcQqyQoAHoECAIQBQ&nis=8&dct=1&cid=CAASFORoyDiIbBc-6d6SGtm7LM01Oupo&dblrd=1&sival=AF15MECOhlsN9b19iUeY1aAEazH-BTv4Gv9zA1-fcGfBFrFlLHqjqAGIgGh_aCUoMjibzfwjdOZY5zBDkQFwKJ--LjA3hVPvU41xfdamyVv4yReqQMJdN8lUcxB5AqGdIiJDpVnPRMR0qsaeGUkn2yZ_t8QzGRi1Fi830pXHuZnuECjD2Qi4BOU8PqE_BiAYZfWZu7Cw66H3&sig=AOD64_1QPnkET8ZsFSgz4Hw_jM-QhcbiPQ&adurl=https://aws.amazon.com/amplify/getting-started/%3Ftrk%3D41731cf6-f5eb-4611-81ef-f2914ec706b5%26sc_channel%3Dps%26s_kwcid%3DAL!4422!3!588971138359!p!!g!!amazon%2520amplify%26ef_id%3D%7Bgclid%7D:G:s%26s_kwcid%3DAL!4422!3!588971138359!p!!g!!amazon%2520amplify)
- [Get Started With Coudflare pages](https://developers.cloudflare.com/pages/get-started/)
- [Get Started with Render](https://render.com/docs)
- [Get Started with Fly](https://fly.io/) 
- [Get Started with GitHub Pages](https://docs.github.com/en/pages)

Implement an error-monitoring system like [Airbrake Error and Performance Monitoring](https://www.airbrake.io) to catch errors while you're deploying your project