Vercel Reviews

I mainly use Vercel for React and Next.js projects. We've done all our web hosting for these projects on Vercel. It's a wonderful platform for hosting web applications built with Next.js and React-based frameworks.

I'm also trying to implement Angular projects on Vercel, but I've been facing some issues. For Angular, we're currently using Firebase to host web applications.

One of the great things about Vercel is that we don't need any particular script to deploy our applications. We connect our GitHub repository directly to Vercel. Then, if any push happens in GitHub, we have a script that determines which branch should be deployed to which domain. We can map this according to our requirements.

I like several features of Vercel. First, it's serverless. We've used different services before, such as AWS EC2 instances, Compute Engines, App Engine, and Cloud Run, as serverless. However, their web performance only reached eighty to eighty-five percent. With Vercel, we reached more than ninety percent performance in website and lazy loading.

The Vercel platform performs better and looks better. I also like how it handles loading GIF files and YouTube videos, which we used in one of our websites. We can do all our file binding and code building within the Vercel platform. We don't need to use different tools like S3 bucket or Cloudinary. We use the Vercel platform for binding, lazy loading, and other features. Everything happens inside the platform, which is very convenient.

The tool is very easy to use. It was harder to manage when we used Firebase, App Engine, and Cloud Run. Someone had to be available to handle build and deployment issues. We sometimes needed to change scripts or add credentials in Secret Manager or .env files, and we had to check logs to see what was wrong. The build time was a major advantage with Vercel. For NextGen and ReactGen projects, the build time is minimal. I compared it with App Engine and Cloud Run, and while they took about 15 minutes, Vercel only took 15-20 seconds. The build and deployment happened a fraction of the time, which was a significant benefit.

The platform is very easy to understand, and it's essentially plug-and-play. As a senior DevOps engineer, I've handled GCP and AWS, which require platform-specific knowledge. We've also used Firebase to host Angular projects and static pages, which need scripting for deployment, targeting sites, and ignoring caches like node modules.

With Vercel, none of that extra work is necessary. React, or Next.js developers develop based on the framework requirements, and it's plug-and-play with GitHub. You need to connect the domain. I learned to use it in-house in about two to three hours and could deploy it.

Another advantage is that we can get SSL certificates directly through Vercel. We don't need to purchase separate SSL certificates for HTTPS redirecting.

I used Vercel for a SaaS project that provided a one-stop solution for new startups, including opening corporate bank accounts, payroll management, and legal consulting. We built the backend using Next.js, and that's why we hosted it on Vercel. The frontend is also hosted on Vercel. It was a good experience since they offer a lot of client services, including a command line interface (CLI) that you can install using NPM. You can also connect it to GitHub if needed.

In our organization, many people use Vercel. Most repositories and dependencies are hosted on Vercel, including our 3JS projects, due to Vercel's good support for React three fiber and other features. Vercel provides a good amount of storage, even for those without a plan, making it ideal for open source projects. Many libraries and dependencies are hosted on Vercel to showcase to developers, as GitHub’s default hosting isn’t always appropriate.

I use Vercel to Deploy ReactJS and NextJS websites.

I like the user experience. Without platforms like Vercel, you have to manually handle route or domain connections and use other services. Vercel makes it easy to connect domains and also has the Azure feature, Vercel Edge Functions.

I have used Vercel for my personal products and the company I work for, where we make a lot of SaaS software tools for our clients.

If I am considering deploying my front end, the entire process or the entire deployment cycle is very easy for a full-stack developer or a front-end developer. Let us say that after the deployment, I want to push some updates, then the entire CI/CD pipeline, and everything is handled since the tool's automation is very good.

I use Vercel to deploy my full-stack websites, including React and Next.js projects, and use AWS for its backend. Vercel provides a free hosting service and a subdomain for the websites you host.

Vercel is a platform that is well-suited for deploying Next.js applications. Next.js is a robust front-end framework built on React.js, known for its excellent SEO capabilities. It supports static page generation and server-side rendering, which helps improve search engine rankings. This optimization is due to Next.js's ability to provide search engines with fully rendered pages. Vercel also provides automatic SSL certificates for your websites, ensuring visitors see a secure connection.

Vercel is a platform where you can deploy your website. I use it to deploy my Next.js and JavaScript or TypeScript websites.

I use Vercel for front-end websites.

The best thing about Vercel is that it supports Next.js. I use the Next.js framework for my front-end websites.

I use the solution to deploy my website.

The most valuable feature of the solution is that it helps me deploy my website and offers Advanced Deployment Protection along with Vercel Environment Variables.

I mainly use it to deploy my web projects.

I like most that whatever you make in GitHub is directly linked. It does CI/CD, continuous integration and continuous deployment. 

Whatever changes you make in GitHub and commit, it will be reflected in that website. You don't have to refresh it every time.

Anyone can use it. It is very easy. For some time, I did not properly understand the website. But once I looked into it, I got it. You don't have to learn anything.

Sometimes, you have to look into GitHub and see what the main files are, and you have to tell it to run the main files properly. Otherwise, it will run some other files, and your project will not be properly deployed. 

You have to keenly observe and tell it where the file is and which project you need to run.