Vercel [EOL] 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.

Due to RBI guidelines, we're facing issues with billing in India. Credit card payments often get declined even when we try to pay from the backend. Another problem is paying 20 dollars for each new project, even under one account. This seems odd since we already pay for one project with multiple hosts.

The tool should improve its support. The time zone difference causes delays in communication, which can significantly impact production websites and servers.

I'd rate the platform itself higher, but they still need improvements. They need to work on their billing system and create more understandable plans that clearly show costs based on bandwidth usage.

A major challenge we faced was an unexpectedly high bill of 25 lakhs for one month when we usually pay only one or two lakhs (100,000-200,000 rupees). While they showed the bandwidth usage, we lacked support on optimising or implementing changes to reduce costs.

I have been using the product for a year. 

In the year we've been using Vercel, we haven't had any issues with stability or bugs. We've hosted multiple websites and a WhatsApp platform without problems. We configured the required settings for our major company projects and a public website, which handles data loads in terabytes daily, especially for GIF files.

The only issue we've faced is billing, which is due to RBI guidelines and not under Vercel's or our control. For stability, I'd rate it nine points five to ten out of ten, specifically for NextJS and ReactJS projects. I haven't deployed any Angular projects on Vercel yet, though they're in our pipeline.

We're developing code and improving frameworks based on the Vercel platform. Once that's done, I might deploy Angular projects too. For React, I'd say this is the best platform.

For scalability, I'd rate the tool an eight out of ten based on my experience and deployments. It's a serverless platform, so we haven't had any scalability issues. We can choose the configuration we need and improve bandwidth usage by selecting the appropriate plan. If we need additional bandwidth, we can reach out to the business head or their team to choose the right plan.

I'm giving it an eight because it depends on our main company's public-facing needs. We've never experienced any lagging issues, even when uploading multiple large files like GIFs, panels, and images. Some banners are around ten megabytes, but loading them doesn't take much time. I'd say we've achieved 90 plus percent in performance. We've never felt any performance issues, even with large file uploads and high bandwidth usage.

Our entire development team, especially the front-end developers, uses Vercel. We have around eight to ten front-end developers working with React and Angular. Access to it is necessary for deployment. The CI/CD implementation with Vercel is very easy. We must connect our GitHub to Vercel; CI/CD happens by default. We don't need to schedule webhooks; Vercel handles them on the backend. So, we have eight to ten front-end developers utilizing Vercel in our organization.

I've never contacted Vercel's technical support team, only contacting them about billing issues.

The solution's deployment is straightforward. 

As a DevOps person who has to consider the commercial aspects, I find it odd that we must pay $20 per user for each new project under a pro account. That's not what I expected. Additionally, there are charges based on bandwidth usage. We incur additional charges if we go beyond 1 TB or 2 TB. However, we can choose plans based on our specific requirements. So, while the per-project pricing and bandwidth-based charges can add up, we have some flexibility in selecting plans that fit our needs.

I rate the overall solution an eight out of ten. 

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.

If you're not using Edge Functions, Vercel only allows 20 seconds of streaming from the backend. They should allow more time for backend streaming without Edge Functions. This is one thing that Vercel can improve.

I would like more time allowed for backend streaming. If you have a chatbot with text streaming, like ChatGPT, and you're not using the Edge router or Edge Functions, Vercel cuts off streaming after 10 seconds. The backend server without Edge Functions shuts down if it processes for more than 10 seconds.

It has been one and a half years since I have been using Vercel for production and deployment.

I've been using Vercel for one and a half years and have never had an issue. Vercel's site went down once for three to four months, but other than that, I've never faced an issue.

Previously, we used AWS for deployment. Now, about 10 to 20 people in my company use Vercel, including for the main site.

It is definitely a scalable product. We can add more users if we want.

I've never needed to contact customer service and support. It's always working perfectly.

There are two things: deploying on Vercel and the Vercel CLI. Installing Vercel on your local machine is super easy using NPM. 

For production, you connect it to GitHub and get all the repositories there. Deployment is done with a click. It's very easy.

I deploy ReactJS and NextJS websites on their platform on Vercel cloud.

I have integrated Vercel with any AI projects. The streaming issue was from one of those projects. I had to switch to AWS because of it.

It's quite expensive for enterprise use, but it's worth the price.

If someone wanted to use Vercel for the first time to deploy a ReactJS or NextJS website, I would definitely recommend using it. Vercel provides a better user experience and easier deployment than other platforms. 

It is easy for a beginner to learn within a week. 

Overall, I would rate it a ten out of ten. 

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.

The tool could have some built-in support for a wide variety of frameworks. I have seen that the tool is majorly biased towards Next.js because it is one of Vercel's products. If Vercel can expand that to many other back-end frameworks as well and maybe somehow delve into the deployment and DevOps for Android and iOS apps, it would be good. I don't know the nuances behind deploying an Android or iOS app, but maybe if Vercel could figure that out, then it would be good. What I have experienced is that even if I coded an Android app, it is kind of very complex and difficult to get it live on the Google Play Store and deal with all the complexities that come with such a platform.

In one of my projects, I was implementing the ChatGPT API to function like a chatbot on a client's website. I saw that the APIs need serverless functions, and these are supposed to be deployed on Vercel. When it comes to serverless edge functions, Vercel sometimes kind of messes up. If there is one chatbot and 100 users are trying to chat with it at once, it gets messed up, even if it is a small number. The above-mentioned area in Vercel could be improved. I know the tool will improve because it covers a lot of space in the front-end development domain.

I have been using Vercel for two to three years. I am a customer of the tool.

In the previous year, there was a time when one of the tool's servers went down. Even on the tool's website, it was showing that if any of the product's servers were down, it was due to a wide outage, and many of the other servers under Vercel were also down at that time. I think the speed of the tool is good. If your front end is deployed on Vercel, the speed is good. The tool's free plan is quite good. The tool offers a lot of features in its free plan. I have deployed my stuff on Vercel for almost two years. Stability-wise, I rate the solution a nine out of ten.

It is a scalable solution. The tool can handle more than 1,00,000 requests, and I think that is more than enough for a lot of small-scale startups. Scalability-wise, I rate the solution an eight out of ten.

I have experience with Netlify and Render.

The product's initial setup phase is very easy. I can go to the tool and sign up or log in with my Google or GitHub, connect my Vercel account to my GitHub account, and then just select the repository we want to deploy. Then, I need to select Next.js, and everything is done. The process is just a kind of one-click deployment and can be managed in five to ten minutes.

If I cross the free version, I have heard from some people that the billing can be expensive. I think it really depends, and it is a very subjective question. I haven't personally experienced the billing plans, so I cannot comment on the pricing part.

For a first-time user or a non-tech person, it will be very easy to deploy the tools you have. If you are running a business and you usually work in your tech team, apart from working with front-end and back-end developers, you will also need two or three people from the DevOps team. What I have personally experienced is that Vercel eliminates the need to have DevOps. If you are not a very big startup and you are doing a small-scale business, then you might not need DevOps people while using Vercel, leading to cost reduction.

I recommend the tool to others.

At my company, I tell my colleagues and other developers to just keep an eye on Vercel because, for most of the full stack work that is being done right now in the SaaS space, 70 percent of people are using Next.js by Vercel. A lot of SaaS in the future is going to be built on Next.js, and it will be deployed on Vercel. It is good if you are familiar with using the tool. The entire ecosystem Vercel is setting up is quite beneficial for the developers.

As Vercel is an expensive product, I rate the tool an eight out of ten.

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.

Vercel provides hands-on experience they provide for hosting services. Initially, we started with hosting, and I found it impressive that Vercel identifies even minor issues in your project that might prevent your website from being hosted correctly. For example, if there is a small problem in your front end, Vercel will notify you that your site hasn’t been hosted yet and provide the specific file and line number where the issue is occurring.

It is definitely an easy tool to use. It provides clear instructions on how to handle everything, even if you're not very familiar with coding. It has a seamless integration with GitHub. We connected our private repository to Vercel, and it directly indicates any issues with the website whenever we commit code. Even if we've done all the changes and committed to the repo, Vercel lets us know about any flaws that would prevent the website from functioning fully. Once the final commit happens, Vercel gives a green tick, indicating no issues. It was a very easy and good experience, with great integration with other tools.

Initially, Vercel was great for hosting projects built with frameworks like Next.js or React.js, with NPM or Node.js as the backend. Now, they seem to be expanding into offering templates and ready-made front-end and back-end setups, making it possible to host a website without writing any code. Personally, I don't like this shift because it reduces scalability and the ability to create unique, customized experiences. Code is essential, and moving towards more user-friendly, code-free tools might limit deeper development possibilities.

I have been using Vercel for the past six months.

We didn't experience any stability issues with Vercel; right from the beginning, it was a very good experience. For stability, I’d give it 9.5 out of 10.

For scalability, I think Vercel should maintain a rigid system while still being easy for those who don't know code. For developers, it would be great if they could update their code directly from Vercel. Based on scalability, I'd rate it an eight out of ten.

We didn't encounter any problems requiring technical support, but I feel Vercel's support is good. The developers who built Next.js probably built it at Vercel, so it's a well-integrated system. Overall, it was a good experience.

The initial setup with Vercel is very straightforward. 

For most use cases requiring a small amount of storage, Vercel has a storage cap. Once you exceed that, they charge a nominal amount. I don’t think the storage is insufficient; you can use it for a long time.

On a scale from one to ten, I’d give Vercel nine out of ten.

I definitely recommend Vercel for others, especially for startups and those testing their products. You can connect it with GitHub to host your website easily. If you're starting a technology startup, whether B2C, B2B, SaaS, or open source, and you're low on funds, Vercel is a great option for free hosting. It has excellent built-in features, especially for those using Next.js, React, and other JavaScript libraries. Vercel is great for beginners and mediocre coders who want to host their small or medium projects to see how they look. It's free for many storage needs and is perfect for open-source projects and new libraries that need to be showcased.

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.

In future releases, I would like to see AI-based capabilities in Vercel. 

I have been using it for three months. 

Vercel is a stable platform for me right now.

There are eight people in my company THE CONSTRUCTORS, and two of them use Vercel right now. Six people are still learning, but they will use Vercel in the next three months.

I didn't reach out to support. 

I can understand the structure and documentation of Vercel. That's a good thing about Vercel; everyone can understand it properly. You don't need to talk to the team about deployments or anything else.

I used Netlify before Vercel, but now I use Vercel because it is better.

We chose it because Vercel is the fastest deployer, and if you deploy your site, it won't have any issues. If you create it for positive use, Vercel will never get you into any trouble. 

But if you use it for negative purposes, it will cause trouble with the website. Vercel is better than any other website, so that's why I use it.

It is easy to deploy websites on Vercel. Vercel is the best for deployment. I use Netlify, but Netlify is not better than Vercel. Vercel is the perfect website if you want to deploy your site or run a free site.

Vercel is basically free. It's free of cost for new developers, and they can use and deploy their sites without a domain. They can use a custom domain with the Vercel protocol.

It is easy to learn. If you want to deploy your site, it's easy to do. If you create a site on Next.js, it will deploy properly and easily.

There is no time needed to learn. If you are a front-end developer, you can also deploy your site on other websites. Many people deploy their sites on GitHub, but I use Vercel. Vercel is easier to use than GitHub.

I would rate it seven out of ten because there are things missing in Vercel. If it can add AI, then it's perfect.

Vercel is easy to use, and the documentation is good.

I use Vercel mainly for deploying Node.js and Flutter applications, though it can handle many different types of applications, such as Python and Django. Vercel gives us a serverless deployment flow.

What I like most about Vercel is that it's easy to set up CI/CD. I can get my site running and sharing with just a few clicks. It automatically builds and deploys new code when I commit to my repository. It provides temporary domains for each deployment, making sharing and previewing changes easy. I get three subdomains under the tool that I can use to share my site. I can easily view logs, too. It's great for starting projects, as I can use it for free as an individual. I find it simple to share repositories and deployments with anyone worldwide.

I've been using the solution for a while now, and while I haven't encountered major issues, there is room for improvement. The main problem I've noticed is with the error logs. They often lack information and only indicate that a file is missing without specifying the actual cause of the error. This makes troubleshooting difficult, as running the app locally might show the error in the console, but on Vercel, it just crashes without providing useful details.

I have been using the product for three to four years. 

I haven't got much traffic on the website. Hence, I haven't faced any stability issues. 

I use the documentation, FAWs, YouTube videos, and friends for support. It offers faster resolution.  

I chose Vercel over Heroku because I found Heroku too complex, especially when setting up pipelines and workflows. It used to work fine, but many features became paid. Vercel, on the other hand, is easy. Even someone without coding knowledge can import a repository and make it live. In comparison, other platforms often require some programming knowledge.

The solution's deployment is straightforward. You need to import the remote repository from GitHub or any other source, and then you can deploy the code with two or three clicks.

I haven't paid for the solution yet. You need to pay to invite team members. 

If you asked me whether to use Vercel, I would recommend it. Based on my experience over the past three to four years with both Heroku and Vercel, I can confidently say that Vercel is much simpler. You don't need much technical knowledge; Vercel guides you through the process, making it easy to use.

I rate the overall product an eight out of ten. 

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.

What I could feel is that it should have some work for when we commit some type of error. Very silly errors. If it has some feature that will reduce those errors, like deployment errors or some missing files. But we don't get what are the missing files in the Vercel website.

So if we have some certain feature that tells us what are the files missing, what are the images. Sometimes images are not properly placed into the website. So have some feature like that. It'll be great.

I started using it only last year. 

I was deploying my projects. And I wanted a free platform to deploy my React projects, or normal HTML, CSS, JavaScript projects, my websites.

I would rate the stability a six out of ten. 

I've faced a lot of issues with Vercel. One thing is that it is a little bit slow. Whenever I deploy my project, whenever I click on the link URL to my website given by Vercel, the images, and the text sometimes load really slowly.

It's as easy as committing to GitHub. It is connected to GitHub.  So you can connect your GitHub to Vercel, import your projects into it, and then deploy it.

So very straightforward. It's a cloud-based platform.

Integration: I've used Render sometimes. But I like Vercel because it is connected to GitHub. Render is also connected to GitHub, but there are some other features which I don't like in Render. It takes a lot of time to deploy and create an account. It has a lot of fuss. But in Vercel, it is very easy to log in and create an account.

I'm a free user.

But the price is a little higher than that of Indian currency.

I would recommend it. It's a great platform, but you need to work on the servers. They are really slow for free accounts. I haven't used their premium account.

Overall, I would rate it an eight out of ten. I used to deploy my websites on localhost, but I haven't used anything else as such.

I use the solution to deploy my portfolio website. 

I like Vercel the most for its ease of use, especially with Next.js. Its UI is user-friendly, and the solution is easy to learn. I was a beginner when I created my portfolio website with the tool. 

I have seen a bottleneck in Vercel regarding socket servers. According to their documentation, Vercel doesn't support WebSocket. While Vercel is great for creating a cloud application, if you need socket operations, the current platform won't accommodate that. I would like the Vercel team to add this feature.

I have been using the platform for three years. 

My portfolio website was based on Next.js. The Vercel team is part of Next.js, so it was my best option. If I had to deploy a React application, I would have had to add a lot of configurations, especially for the server part, which can get messy. That's part of the reason why I chose Vercel.

The tool's deployment is easy. 

I use the solution's free version. 

My portfolio website draws only around 200 visitors. I rate the overall product an eight out of ten. 

I wouldn't recommend Vercel for a serverless static page. If we are looking at a production level, maybe a cloud platform that is being used by a lot of users, then I would suggest Vercel because it comes with its own pages, like analytics and insights. So I think it would be better if we were using it for a large customer base. But I would not recommend it if it's for a small project.

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.

Vercel fails to provide a database to its users, making it in an area where improvements are required. With the database, it can be easy to manage the websites. We can add the database, and also we can deploy the websites.

I have been using Vercel for two years. I am a freelancer who uses the tool for my clients.

When reloading or due to any server error, I have not seen any issues when I deploy any website in Vercel. It runs very smoothly.

I have never contacted the technical support for the solution.

The tool's billing allows 200 deployments per day, but if you want to do more work with the solution, you can opt for the pro plan offered by the tool.

The tool is easy to use.

Vercel is a good platform for deployment of websites. The tool allows want to easily manage deployment and branches, specifically the ones in GitHub.

From the product's technical support team, you can get help on how to customize domains and how to manage the branches. We can add the members to the group.

I personally use the product, and I feel that the other solutions in the market do not provide the features that Vercel offers. Vercel is also easy to manage.

I recommend the tool to others.

I rate the tool a nine and a half out of ten.

I build full-stack applications. For backend technology, I use Python Jango. So, for the backend application, I use Vercel for deployment. 

Vercel's real-time global deployment positively impacted our project delivery.

Vercel is easy to deploy. We don't have to set up any servers or something like that. We just have to configure the server in Vercel and it takes care of it. 

There is room for improvement in terms of error logging. It has some bugs. 

It just gives a single sentence. It is not good. What error is causing in the terminal or console is not explained properly. 

I've been using Vercel for six months.

It is pretty stable. I haven't found any bugs. 

We have around 10 to 15 end users. 

Once I reached out to the support. It was an issue with the domain setup. 

The experience was okay, neither good nor bad. 

Neutral

Other solutions are not stable. Vercel is the only situation, giving good features and performance.

It is pretty cheap for the features it offers. 

If someone wants to use Vercel for the first time, I recommend it.

There are some prerequisites to using Vercel. For example, if someone knows how server configuration works, they can easily use it. 

Overall, I would rate it an eight out of ten.