Pantheon vs Vercel comparison

"The product allows users to create multiple development environments."

"Pantheon has the most valuable workflow model."

"It is easy to learn. If you want to deploy your site, it's easy to do."

"It provides continuous integration and continuous deployment capabilities."

"Vercel is easy to use, and it has a flexible user interface."

"Vercel is easy to use and not as complex as AWS."

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

"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 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."

"Vercel provides a better user experience and easier deployment than other platforms."

"Pantheon has the most valuable workflow model."

"The Multidev environment is very costly compared to other tools like AWS and GCP."

"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."

"If I could add a feature to Vercel to make my life easier, I would add a user journey feature for new users. This would guide them with tips on exploring the platform, showing them the routes for deployment and functions they can use. This way, users can understand all the features without upgrading to premium to see their benefits."

"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."

"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."

"Vercel cannot handle big projects like shopping applications."

"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."

"What I could feel is that it should have some work for when we commit some type of error."

"Vercel fails to provide a database to its users, making it in an area where improvements are required."

"The platform has reasonable pricing compared to other systems."

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

"Vercel is a bit costlier than other solutions like AWS."

"The solution's pricing depends on the size of the project."

"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 solution is expensive for React projects."

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

"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."

"If I cross the free version, I have heard from some people that the billing can be expensive."