AI Gateway

What do you like best about the product?

Vercel is what lets a small marketing-run engineering effort ship and run real production apps without a dedicated DevOps person. The CLI workflow is dead simple once authenticated: I run staging and production as two separate Vercel projects pointed at the same codebase, deploy staging first, verify, then push the same build to prod with one command. For a Next.js app like our internal lead-routing dashboard that our sales team relies on daily, deploys are fast and predictable, and I can verify a change actually shipped by curling the live bundle right after. It's also become the backbone of a product we're turning into paid software: our plan to sell it to other companies is to stamp a private Vercel project (plus Supabase and n8n) per customer from one template, which only works because spinning up a new project is trivial.

What do you dislike about the product?

Vercel Cron has been our biggest source of friction. We had nightly scheduled jobs running as Vercel crons and ran into cold starts and occasional silent failures that were hard to notice until something downstream didn't happen. We ended up planning to move that scheduled work into Postgres (pg_cron on our database) instead, specifically to get away from cold starts and get failures that actually surface rather than fail quietly. Managing two parallel projects (staging and production) also means duplicating environment variables and secrets across both, which is easy to get out of sync if you're not careful.

What problems is the product solving and how is that benefiting you?

Without Vercel we'd need someone managing servers, SSL, and deploy pipelines just to keep a handful of internal apps online, which isn't realistic for a marketing department building its own tools. Instead I can go from a Next.js app on my machine to a live URL reps and other departments actually use in minutes, and iterate on it safely by testing in a staging deployment before it ever touches production. The real payoff has been being able to build things like an internal lead-routing dashboard our sales team checks constantly, in-house instead of buying an off-the-shelf SaaS tool for it, and now we're extending that same setup into software we plan to sell externally, since replicating the whole stack per customer is just a matter of standing up a new Vercel project.

What do you like best about the product?

I use Vercel to deploy static ops trackers and complex intranet sites. It makes deployments easy to maintain and change without chaos. I appreciate that I've never faced deployment credit issues with the free version and enjoy the pro paid version at work. Vercel's UI is straightforward, and deploying sites is a breeze. The GitHub integrations, preview deployments, and automated deployments are fantastic. Once I push changes to GitHub, Vercel deploys them almost instantly without manual checks, and I can view the deployment history for modifications. It's user-friendly, even with minimal coding experience, and the initial setup was quite easy.

What do you dislike about the product?

I sometimes face difficulty with the technical terms, like configuration and environment variables, but I usually sort it out easily by asking for help from Claude or ChatGPT.

What problems is the product solving and how is that benefiting you?

Vercel makes it easy to deploy and maintain websites, connecting smoothly with GitHub and databases without chaos. It offers automatic and fast deployments, saving me time. I've had no deployment issues like those I faced with other tools, even on the free version.

What do you like best about the product?

I like how Vercel makes deployment feel effortless. Everything is fast, clean, and developer-friendly. Features like instant previews and seamless Git integration make it much easier to test, share, and ship projects quickly

What do you dislike about the product?

The main thing I would improve is pricing transparency. As projects scale, it can be difficult to predict costs. Better usage insights and clearer limits would help developers manage their projects more easily

What problems is the product solving and how is that benefiting you?

Vercel solves the problem of making web deployment simple and efficient. Instead of spending time managing servers and infrastructure, I can focus on building and improving my applications. Features like automatic deployments, Git integration, and preview environments make testing and releasing changes much faster. It saves time, reduces complexity, and helps me deliver projects more confidently.

What do you like best about the product?

What I like most about Vercel is how simple it makes deploying and managing web projects. I can connect my GitHub repository, push changes, and Vercel automatically builds and deploys the latest version. The deployment process is fast, and the dashboard makes it easy to check builds, logs, domains, and deployment status. For my React and frontend projects, it has saved me a lot of time compared to managing hosting and deployment manually.

What do you dislike about the product?

The main thing I dislike about Vercel is that the pricing can become a concern as a project grows, especially when usage increases. Some advanced features and higher usage limits can feel expensive for students or small projects. I also feel that debugging deployment or build issues can sometimes take a bit of time for beginners because the logs can be technical. Overall, the platform is great, but clearer guidance and more student-friendly pricing would make it even better

What problems is the product solving and how is that benefiting you?

Before using Vercel, deploying my projects and managing hosting, domains, builds, and updates required more manual work. Vercel solves this by making deployment closely connected with GitHub, so I can push code and have a new version deployed automatically. This saves me a lot of time, especially when I am working on multiple React and frontend projects. It also gives me deployment previews, build logs, and easy rollback options, which makes testing and fixing issues much easier. As a student, the biggest benefit for me is being able to focus more on building the project instead of spending time managing infrastructure.

What do you like best about the product?

Vercel provides really fast hosting for any local-site website on our system, regardless of which technology we use.

What do you dislike about the product?

Vercel can sometimes be slow, especially when I’m uploading a large project or using more complex technology. During the upload it may show an error, even though there isn’t actually an issue, since the same web app runs fine locally.

What problems is the product solving and how is that benefiting you?

Vercel solves the problem of having to buy web space to host our website, and it provides cloud storage for our projects through GitHub.

What do you like best about the product?

Vercel's automatic deployment from GitHub is completely magical. It provides ultra-fast global CDN edge hosting, which gives my React templates a perfect 100/100 Google Lighthouse speed and SEO score without any manual server configuration.

What do you dislike about the product?

While the free hobby tier is amazing, the pricing gap skips heavily when transitioning to the pro plan for smaller freelance agencies. Also, managing complex serverless functions can sometimes be tricky for pure frontend developers.

What problems is the product solving and how is that benefiting you?

It completely solves the hassle of complex server hosting and SSL configuration. It allows me to instantly push my code live to production with zero configuration, making client project showcasing extremely efficient.

What do you like best about the product?

Git deployments that I don't need to configure. Instant preview URLs that I can share with anyone in the team.

What do you dislike about the product?

The pricing is a bit unpredictable. The Pro plan is $20/seat/month, but that's just a credit wallet. High chances of exceeding the 1 TB included in this plan leading to paying way higher than expected.

What problems is the product solving and how is that benefiting you?

Preview URLs let me spin up mockup pages, create shareable links, and get them reviewed from the team internally. I don't need engineering help for this.

What do you like best about the product?

Serves as an easy solve to the hosting problem and great for beginners. When I was making websites on my own back in the day, I would use the vercel supabase stack, which is intuitive and simple in the age of nontechnical literate coders and vibe coders

What do you dislike about the product?

Not much I don’t like about vercel. I suppose it doesn’t give as much precision as a service like webflow, but, as I said, great for beginners.

What problems is the product solving and how is that benefiting you?

It solves the problem of wanting a simple and familiar interface for beginners at a budget

What do you like best about the product?

I mostly use Vercel for putting my web projects online and checking the live version while I am still working on them. As a student, I work on different projects where I need to make changes, test them, and then share a working link with someone. Vercel makes that part fairly straightforward. I regularly use the Deployments section to see the different versions of a project. After making a change, I can check the new deployment and open the generated URL to see how the website is actually behaving online. This is useful because something that works on my computer does not always behave exactly the same way after deployment. Another feature I use is Rollback. If a recent deployment introduces a problem, having the option to return to an earlier deployment is reassuring. I have found this particularly useful when making several changes close together and realizing that one of them has caused an issue. I also use Logs when I need to figure out why something is not working. They are helpful for checking what happened during a deployment or when trying to understand an error that I cannot reproduce easily on my local machine. I do not understand every log immediately, but they give me somewhere useful to start troubleshooting. The Domains section is another part I use when I want a project to have a proper web address rather than only the default Vercel URL. Once a project is online, being able to manage its domain from the same project dashboard is convenient. One practical benefit I noticed over time is the deployment history. I can look back at previous versions and know which deployment is currently live. When I am experimenting with a project, this gives me a little more confidence to make changes because I know there is a previous version I can refer back to if something goes wrong.

What do you dislike about the product?

The main thing I find slightly difficult is understanding the logs when there is a technical error. They can contain information that is useful to an experienced developer but takes some time to understand as a student. The Hobby plan also has usage limits, so I have to be more conscious of those when working on projects that receive more traffic or need more resources.

What problems is the product solving and how is that benefiting you?

Earlier, when I finished a web project, getting it online and keeping track of different versions was something I had to think about separately. If I made a change that broke something, it was also not always obvious which version I should return to. Now, I can deploy the project, check the deployment status, open the live version, look at logs when something goes wrong, and use an earlier deployment if I need to go back. I can also connect a domain once the project is ready to share. As a result, hosting has become a more regular part of my development workflow rather than something I have to figure out from scratch for every project. It does not remove the technical problems that come with deploying a website, but it gives me a clear place to manage and troubleshoot them.

What do you like best about the product?

Zero-config deploys from Git, preview URLs per PR speed up review cycles a lot. Edge network keeps latency low for our dashboard globally. Build times are fast, logs are clear when something breaks. Analytics built-in saves us a separate tool. Free tier's generous early on.

What do you dislike about the product?

Costs climb fast once you scale past hobby usage, especially with serverless function invocations. Cold starts on edge functions can spike latency unpredictably. Build minutes get eaten quickly on larger monorepos. Support's slow unless you're on enterprise. Some config feels locked-in to their platform

What problems is the product solving and how is that benefiting you?

We were manually managing deploys and staging environments, which slowed releases and caused config drift. Now every PR gets an isolated preview automatically, so QA and stakeholders test real builds before merge. Deploy pipeline that used to take hours now happens in minutes.