Sources

But after three years of using Vercel for basically everything, the honeymoon phase is definitely over. The cracks are starting to show, and my wallet is feeling it too. ## The "Free" Tier That Isn't Really Free Let's start with the most obvious issue. Vercel's free tier seems generous at first glance. And it is - if you're building a personal project that nobody uses. But the second your site gains any traction, you'll hit those limits faster than you can say "serverless function timeout." Last month, I launched what I thought was a simple portfolio site for a friend. Nothing fancy, just a few pages with some images and a contact form. Two weeks in, we hit the serverless function execution limit. Suddenly, the contact form stopped working, and visitors were getting errors. Not exactly the professional look we were going for. … ## Vendor Lock-in Is Real (And It Hurts) I didn't think much about vendor lock-in when I started using Vercel. Their developer experience was so good that I figured I'd never want to leave. But now that I'm maintaining several projects with different requirements, the limitations of being tied to their ecosystem are becoming painfully obvious. Vercel's edge functions? They're great, but they're not AWS Lambda or Cloudflare Workers. They have their own quirks and limitations that you won't discover until you're deep in production. And once you've built your app around their specific implementation, migrating becomes a massive undertaking. I found this out the hard way when trying to move a moderately complex Next.js app to a different hosting provider. What should have been a straightforward migration turned into a two-week refactoring nightmare because we'd used so many Vercel-specific features without even realizing it. ## The Next.js Relationship Is... Complicated And speaking of Next.js - let's talk about the elephant in the room. Vercel maintains Next.js, and they make sure it works best on their platform. This makes total business sense for them, but it creates some weird incentives that don't always benefit developers. Features that would make Next.js more portable or easier to self-host don't seem to get prioritized. Meanwhile, integrations that push you deeper into Vercel's ecosystem get fast-tracked. … ## Those Random Outages Though This is the part that really gets me. For a premium service that markets itself to businesses, Vercel has had some reliability issues that make me nervous. Three months ago, we launched a big campaign for a client. Everything was tested, everything looked great. And then, right as the campaign went live, Vercel had a partial outage affecting our region. Our beautiful landing page was returning 500 errors for about 40 minutes. The client was... not happy. … ## The Cold Start Problem Is Real If you're building anything with serverless functions (which is pretty much inevitable with Vercel), you'll eventually run into the cold start problem. Functions that haven't been used recently take longer to spin up, creating noticeable delays for your users. This wasn't a big deal for most of my projects, but for a recent e-commerce site, those extra seconds on the checkout page were actually impacting conversion rates. Users thought the site was broken when really it was just waiting for a function to warm up. … ## The Bottom Line Vercel isn't bad - it's just not the one-size-fits-all solution it's often made out to be. Their developer experience is still industry-leading, and for certain types of projects, they remain my first choice. But as your projects grow in complexity or traffic, the hidden costs and limitations become harder to ignore. The platform that makes it easy to get started might not be the best platform to scale with.

- Strengths: excellent alignment with the Vercel/Next.js ecosystem, smooth deploy path, and generous context limits on supported models documented in the v0 Models API (2025). - Caveats: pricing/credit limits change and can impact iteration; some community reports describe rapid credit burn and reliability hiccups in 2025 (anecdotal). Example discussions: “Updated v0 pricing” (2025) on Vercel Community. … - Error handling and autofix: The AutoFix layer described in the composite model article (2025) can rescue some broken generations. Still, you should expect to keep TS strict mode on and gate merges through CI. - Portability and lock‑in: v0’s outputs are plain Next.js/React code. You can take the code elsewhere, but the best‑supported path is clearly Vercel deploys with their previews, auth, and observability. That’s pragmatic rather than hard lock‑in—but factor it into your ops model. … Community sentiment in 2025 has included complaints about credit burn and iteration loops—useful as cautionary anecdotes, not authoritative data. See threads like “The new pricing system is horrible” (2025) on Vercel Community and “v0.dev has become unusable…” (2025) on Vercel Community. If your team iterates heavily in chat, monitor usage early and set expectations with stakeholders. … - General AI policy: Vercel describes LLMs trained on human and web content; details are outlined in the v0 Policy page (2025). If you have stricter requirements, obtain written assurances. - Platform security: Vercel publishes compliance and security controls (e.g., SOC 2 Type 2, ISO 27001:2022, GDPR readiness) in the Security & Compliance documentation (2025). You can also scope Git permissions more tightly with Protected Git Scopes (2025) and manage access to deployments with Vercel Authentication (2025). … ## Where to be cautious - Iteration cost/credit burn may be non‑trivial; confirm your plan and monitor usage in the first weeks. - AutoFix reduces some breakage but does not replace code review and tests. - If your stack diverges from Tailwind/shadcn patterns, expect more prompt wrangling or refactoring.

When pushed beyond simple request-response cycles into complex reasoning tasks, Vercel AI exposes significant infrastructure constraints. The following limitations were documented during our benchmarking of agentic and RAG-heavy workloads. … For an autonomous agent that needs to scrape a website, parse the DOM, query a vector database, and then generate a Chain-of-Thought response, this 5-minute window is often insufficient. In our testing, long-running agents consistently terminated with 504 Gateway Timeout errors once the hard limit was reached. Edge Functions are even more restrictive, enforcing a strict limit on the time between the request and the first byte of the response. If your agent requires extensive "thinking time" before streaming the first token, the connection is severed by the platform's proxy layer. ### Cold Starts on Heavy Workloads While Edge Functions are fast, they lack full Node.js compatibility, forcing teams to use standard Serverless Functions for operations involving heavy dependencies or database connections. Loading large prompt templates, validation schemas (like Zod), or establishing SSL connections to an external Vector Database (e.g., Pinecone or Weaviate) introduces significant latency during initialization. … ### Architectural Dependency on Edge Middleware Vercel Edge Middleware utilizes a proprietary runtime environment (EdgeRuntime) rather than the standard Node.js runtime. While it adheres to web standards like fetch, it lacks support for native Node APIs such as fs, net, or C++ addons. Consequently, routing logic or custom middleware developed specifically for Vercel’s Edge is not easily portable. Migrating this logic to a standard containerized environment (Docker) or a different cloud provider (AWS Lambda) often requires a rewrite of the gateway layer. This creates an architectural dependency where the cost of exiting the platform increases linearly with the complexity of the middleware logic implemented. … ### What are the disadvantages of Vercel? The primary technical disadvantages highlighted in Vercel AI reviews are the strict execution timeouts (maximum 5 minutes), the 4.5MB request body limit, the inability to attach GPUs for custom model hosting, and the potential for complex scaling costs.

- Image Optimization Enhancements - Dynamic image transforms at a new, lower cost to supercharge page-load speed. - Advanced Bot Protection - From simple firewall rules to challenge-mode cryptographic checks, keep malicious bots from running up your cloud bill. - Global Caching with Tag-Based Invalidation - Expire cache across Vercel’s edge network in under 300 ms for instantaneous content updates. - Rolling Releases & Safe Deployments - Gradually roll out code changes with instant rollbacks to avoid production surprises. - AI-Assisted Architecture - Best practices for using AI to generate multi-phase implementation plans and integrate them into Git-backed workflows. ▶️ Whether you’re building with Next.js, Remix, or pure Node.js, these features will help you cut costs, boost performance, and streamline AI workflows. ... So like let's say 100 millisecond, right? Like so the the difference is {ts:165} actually quite stark. In 2025, developers are increasingly building systems that facilitate longrunning AI {ts:172} interactions. Purcell is clearly working hard to remove the bottlenecks that make these systems expensive to run. … {ts:412} automation that goes through and clicks the boxes for you like there's ways to game the system and also most of the {ts:419} solutions are not very developer friendly they're kind of hard to use the pricing's kind of weird heard some {ts:425} horror stories of them we wanted to give multiple solutions for bots. … {ts:477} trying to work around that. They're not playing by the normal rules. It's kind of like when they don't follow the robot {ts:482} txt for scraping. They're like, "No, no, no. We're not going to look at that." So, how do you deal with the more … With AI backed web applications, every request comes at a {ts:590} major cost. So bots can really run up your cloud infrastructure bill. Danny and Malta talked about improvements to {ts:596} Verscell's caching systems as well. Check it out. We are really excited about the caching improvements that are … And that's coming both to the platform but also from NHS. Caching improvements are always great to {ts:619} hear about. We all know caching is one of the three hardest problems in computer science. Cache data is {ts:625} persisted across deployments on Verscell and expiring that cash can be really complicated and take a long time. … I'm going to review the plan. And maybe 90% of it is good. But now you have a chance {ts:770} to actually go in and say, "Okay, and I'm going to change that last bit." Now you change from plan to execution. And {ts:777} what I see a lot of people mess up is on execution.

### Common Pain Points with Vercel - **Pricing Scalability**: Costs can escalate quickly as your traffic grows - **Vendor Lock-in**: Deep integration with Vercel-specific features - **Limited Server Control**: Serverless architecture doesn't fit all use cases - **Bandwidth Costs**: Expensive bandwidth pricing at scale - **Build Minute Limits**: Restrictions on build times and deployment frequency … ### Take the Next Step Ready to explore a Vercel alternative?

## Introduction ... Vercel allows developers to host sites effortlessly, but it’s not without its challenges. Many users express their frustrations with Vercel, often summarized in the phrase Brady sucks Vercel. This article explores the challenges developers face with Vercel, provides solutions, and offers best practices to optimize the user experience. … ## Common Challenges with Vercel ### 1. Performance Issues Many developers experience performance slowdowns when using Vercel. These can manifest as slow page load times or delayed server responses, ultimately affecting user experience. **High Traffic:**Sudden spikes in traffic can overwhelm the platform’s resources, leading to slower performance. If an application is not optimized to handle high volumes of traffic, users may face issues like increased latency. **Large Assets:**Heavy assets such as large images, videos, or uncompressed files can significantly slow down loading times. Proper asset management is crucial for maintaining performance. ### 2. Configuration Complexity For new users, Vercel’s configuration options can seem daunting. Misconfiguration can lead to various issues, complicating the deployment process. **Environment Variables:**Setting up environment variables can lead to errors if not done correctly. Users must ensure that all necessary variables are defined properly for their applications to function. **Routing Issues:**Misconfigured routes can lead to broken links or improper navigation, frustrating users and leading to a poor experience. ### 3. Debugging Difficulties Debugging applications on Vercel can be a challenging process. **Limited Logs:**Vercel provides limited logging options, which can make it difficult to trace errors back to their source. This lack of detailed logs can complicate troubleshooting efforts. **Error Messages:**Users often find that error messages are vague and unhelpful. Without clear guidance, pinpointing the root cause of an issue can be time-consuming. ### 4. Cost Management While Vercel offers a free tier, costs can escalate quickly as projects grow. **Billing Surprises:**Users may encounter unexpected charges due to overage, particularly if they are not closely monitoring their usage. Understanding the pricing model is essential to avoid surprises. **Plan Limitations:**Features are often restricted on lower-tier plans, leading users to feel they need to upgrade to unlock necessary functionalities. ## Solutions to Common Challenges ### 1. Improving Performance To tackle performance issues on Vercel, consider implementing the following strategies: **Optimize Assets:**Compress images and use formats like WebP to reduce file sizes without sacrificing quality. Tools like ImageMagick or online compressors can help with this. **Lazy Loading:**Implement lazy loading for images and videos to improve initial load times. This technique loads assets only when they enter the viewport, enhancing user experience. **Use CDN:**Leverage Vercel’s built-in Content Delivery Network (CDN) to distribute content closer to users. This reduces latency and improves loading times across the globe. … ## User Experiences: Brady Sucks Vercel The phrase Brady sucks Vercel has emerged from various user experiences that highlight common frustrations. Here are a few testimonials that reflect users’ challenges: ### 1. Deployment Failures Some users report frequent deployment failures due to misconfigurations or asset issues. These failures can lead to significant delays in project timelines. For instance, a developer might spend hours troubleshooting only to discover a simple routing error. ### 2. Lack of Support Many users feel that while Vercel provides resources, timely support can be lacking. When issues arise, the lack of immediate assistance can hinder development and cause frustration. ### 3. Unclear Documentation Some developers find Vercel’s documentation to be unclear or insufficient. This can result in misconfigurations and wasted time searching for solutions. Comprehensive documentation is crucial for users to maximize the platform’s capabilities. ### 4. Integration Issues Integrating third-party services can sometimes be problematic. Users have reported challenges when connecting services like databases or authentication providers, leading to additional troubleshooting and delays.

### Weaknesses - PRICING: Complex, usage-based pricing creates budget uncertainty for teams. - DEPENDENCY: Over-reliance on Next.js success creates single point of failure. - SUPPORT: Enterprise support SLAs and response times lag hyperscaler offerings. - BREADTH: Platform lacks the breadth of services offered by AWS/GCP/Azure. - SALES: Enterprise GTM motion is still maturing vs. product-led growth. … ### Negative Impacts - Wasted engineering hours on infrastructure - Delayed time-to-market for new features - Inconsistent staging and prod environments ### Positive Outcomes - Increased developer velocity and happiness - Faster website performance and Core Vitals - Accelerated feedback loops and iteration ### Key Metrics ... - An intuitive, self-serve platform UI … ##### Buyer Power Moderate. Individual developers have low power, but large enterprise customers can negotiate terms and pricing. The stickiness of the platform and Next.js integration reduces churn. ##### Threat of Substitution High. Developers can revert to building their own CI/CD on AWS/GCP, or use alternative platforms. The primary defense is superior developer experience and workflow efficiency.

Something shifted in the developer community over the past year. The conversation around Vercel changed from "this is amazing" to "did you see my bill?" What was once the default deployment platform for Next.js and modern frontend apps is now the subject of Reddit threads, Hacker News discussions, and blog posts about surprise invoices and pricing traps. This is not about Vercel being a bad product. It is an excellent deployment platform with a superb developer experience. The issue is the gap between the experience of using Vercel and the experience of paying for it -- a gap that widens significantly the moment your app gets real traffic. … - **Build minutes:** 6,000 minutes included. Overages at $0.01 per minute. A Next.js app with a large page count or heavy static generation can consume 5-10 minutes per build. Push 20 times a day across a team and you are burning through those minutes fast. Some teams report hitting the ceiling within the first two weeks of the month. - **Serverless function invocations:** 1 million included on Pro. Every SSR page render, every API route call, every ISR revalidation counts as an invocation. A moderately trafficked e-commerce site can exhaust this in days. - **Bandwidth:** 1TB included. Overages at $0.15 per GB. If you serve images, videos, or large JSON payloads, 1TB is not generous. One viral moment and your bandwidth bill spikes. … The result is predictable: developers share stories of $400 surprise bills, $1,200 monthly invoices for what they expected to be a $20/month service, and the realization that the "serverless" model means you are paying per-request for things that a persistent server handles for a flat rate. The most frustrating aspect is not the cost itself -- it is the unpredictability. With usage-based pricing, a traffic spike (which should be a good thing) becomes a financial risk. You cannot budget accurately because you cannot predict your bill.

The web development community is experiencing a wave of criticism toward Next.js, one of the most popular React frameworks. What started as a single developer's blog post about logging difficulties has sparked a broader conversation about the framework's increasing complexity and its tight coupling with Vercel's hosting platform. … **Common Next.js Pain Points:** **Middleware limitations**: Single middleware file requirement, complex chaining **Logging difficulties**: Inconsistent behavior across edge/server/client environments **Runtime confusion**: Code execution context unclear (edge vs server vs client) **Vercel coupling**: Features optimized for Vercel hosting, problematic elsewhere **Documentation gaps**: Missing details about execution contexts and gotchas ### The Vercel Vendor Lock-in Debate A significant portion of the community discussion focuses on allegations that Next.js is deliberately designed to push developers toward Vercel's paid hosting services. Many developers report that features work seamlessly on Vercel but become problematic when deployed elsewhere. This has led to accusations that the framework's complexity isn't accidental but rather a business strategy. My experience with Next.js are that its rough edges are a feature, not a bug. Everything is geared towards you giving up and just using Vercel's hosting Several developers shared stories of inheriting Next.js projects that were so tightly coupled to Vercel's infrastructure that migrating to other hosting providers proved nearly impossible, sometimes requiring complete rewrites. ### Breaking Changes and API Instability The community has expressed frustration with Next.js's rapid release cycle and frequent breaking changes. With version 15 recently released, developers note that the framework has introduced 15 major versions in 8 years, each potentially containing backwards-incompatible changes. This creates maintenance burdens for long-term projects and makes it difficult for teams to keep applications updated.

## Framework limitations: React-only output V0's UI generation power comes with strict framework limits. The tool only creates: - React components (mostly functional component patterns) - Next.js-compatible code - Tailwind CSS for styling - shadcn UI component integrations This narrow focus helps v0 excel but creates restrictions. Developers who use Angular, Vue, Svelte, or other frameworks must convert v0's output extensively. Tools like Trickle AI offer broader framework support, which makes them different. The system doesn't create TypeScript by default and depends on Tailwind's design approach. Projects using CSS-in-JS solutions like styled-components or Material UI need much adaptation work. ## Why v0 isn't a full-stack solution V0's biggest limitation lies in its focus on the presentation layer. The system creates impressive UI components but doesn't generate: - Backend logic or server-side functionality - Database schemas or data access layers - Authentication systems (though it builds auth UI components) - API communication code - State management implementation V0 speeds up the design-to-code process for visual elements, but developers must build all underlying functionality themselves. My request for "a user profile page with edit capabilities" resulted in a beautiful interface without any data handling logic. The system doesn't tackle application architecture challenges. V0's components work as standalone pieces rather than parts of an integrated system. Developers must figure out how these components share state, interact with data sources, and fit into larger applications. Some developers might expect v0 to work like a complete application generator. The reality shows it's more of a specialized UI component creator—excellent in its domain but needing developer expertise to build production-ready applications. ## Top 4 Things Developers Get Wrong About v0 My extensive work with Vercel v0 has revealed several persistent misunderstandings about what it can do. Developers often approach this tool with wrong assumptions that cause frustration. They miss opportunities too. Here's the truth about the most common myths. … ### Myth 3: It generates production-ready code every time v0 has impressive capabilities, but expecting perfect, production-ready code every time leads to letdowns. The code it generates usually needs debugging and improvements. Users often face these issues: - Build errors with component imports - Module paths that don't match and need fixes - Project exports missing pages (showing just one instead of all created pages) - Problems with tweaking auto-generated code v0 gives you a good starting point for rapid prototyping. Notwithstanding that, developers should plan time to debug and improve the output before deployment. … ## Real-World Performance and Limitations Vercel v0's glossy marketing often hides serious usability problems that surface during actual use. My tests across many projects revealed recurring limitations that affect workflow efficiency and output quality. ### Code quality and debugging issues V0-generated code often turns debugging into a marathon. Users say the tool becomes "buggy to the point of being unusable" while prompts fail to complete code generation and produce "very low quality" responses. My tests showed v0 sometimes writes chat output directly into code files and creates syntax errors that break compilation. Developers face unique challenges with troubleshooting because v0 lacks proper debugging tools. Server-side exceptions leave developers with "no way to preview the project anymore". The platform doesn't give access to terminal logs, which leaves developers "stuck" without any way to see what's causing errors. Simple projects aren't immune to unexpected errors. A developer reported getting import errors for React hooks that weren't properly exported, though they hadn't changed their project. ### Project continuity and export problems Sharing and exporting v0 projects creates constant problems. The platform has trouble with Git integration, which makes version control difficult in team settings. Manual code edits often vanish during later generations – especially frustrating when fine-tuning components. Export features cause particular trouble. Users report "blank screens appearing after exporting" and incomplete project exports that include "only one page instead of all created pages". So what works in the v0 environment often breaks in production. ### Learning curve for non-Next.js users Developers outside the Next.js ecosystem face a steep learning curve because v0 only outputs React components. Teams using "other frameworks for front-end" development find the tool unsuitable. The tool struggles most with its parent company's own technology. A user who renewed their "Team Edition subscription" just for v0 reported "regretting it" due to "frequent errors on first prompts". Simple prompts needed "several round trips to fix issues", which undermines v0's promised productivity boost. V0 delivers impressive results in ideal scenarios but falls short in actual use. Teams should carefully evaluate its debugging limitations, export problems, and framework support before adding it to their professional workflows. … **Q4. What are the main limitations of using Vercel v0?** Key limitations include its React-only output, reliance on specific libraries like Tailwind CSS, lack of backend logic generation, and occasional issues with code quality and debugging. It also has limited customization options and may not always produce production-ready code without developer refinement.

Impact: 8/10Reported 6xNegativevia Other (22 sources)hidden costs No real-time cost monitoring - bills arrive as surprises The platform lacks real-time consumption monitoring of resources. Users can't predict or manage expenses before unexpected bills arrive. One of the biggest issues teams have is the lack of visibility into cost drivers until the bill comes. … Impact: 10/10Reported 7xNegativevia Trustpilot (35 sources)workflow failure Deployments fail without obvious reasons Users report deployments sometimes failing without clear error messages or obvious reasons. Build step can be interrupted if it exceeds 45-minute limit. Debugging failed deployments is frustrating without adequate error information. Impact: 6/10Reported 5xNegativevia Capterra (18 sources)workflow failure Integrations2 signals Vendor lock-in with Next.js - hard to deploy elsewhere Next.js generates build artifacts optimized for Vercel's infrastructure. Features like next/image, ISR cache invalidation, and edge functions work best (or only) on Vercel. Starting with Next.js 15.1+, some features may break on non-Vercel deployments. Impact: 8/10Reported 8xNegativevia Reddit (45 sources)migration pain Limited database and backend support Vercel focuses on frontend deployment, limiting support for databases and backend services. Programmers find they can't create sophisticated full-stack applications. Must use external services for databases, adding complexity and costs. … Impact: 7/10Reported 6xNegativevia Trustpilot (25 sources)workflow failure Hobby plan prohibits commercial use - must upgrade immediately Vercel's free Hobby tier prohibits commercial use entirely. Even small revenue-generating projects must upgrade to Pro at $20/user/month. Users discover this after deployment, forcing unexpected cost commitment. No grace period for startups testing viability. Impact: 7/10Reported 7xNegativevia Capterra (35 sources)expectation mismatch V0.dev requires separate payment and consumes credits fast V0.dev requires payment for both Vercel hosting and V0.dev separately before you can bring over your own code. The AI consumes credits unnecessarily, adding unexpected costs. Users feel nickel-and-dimed by the separate billing. Impact: 5/10Reported 5xNegativevia Capterra (15 sources)workflow failure Performance2 signals Serverless function timeouts at high load Users report undefined errors at higher loads that Vercel couldn't resolve. Function timeout limits cause issues - functions timing out at 60 seconds on Pro plan despite documentation claiming 300 seconds. Complex apps experience runtime issues with no clear solutions. Impact: 8/10Reported 6xNegativevia G2 (28 sources)scaling breaks Cache invalidation problems scaling Next.js Scaling Next.js is problematic due to bad cache invalidation across replicas. ISR (Incremental Static Regeneration) cache invalidation works best on Vercel but causes issues on alternative deployments. Makes it easy to start but harder to grow. … Account suspended without warning Account disabled within minutes of deployment with vague 'fair use violation' email. Appeals go unanswered for weeks. Project was running fine on previous host. Lost access to production site with no recourse. During deployment Reported 7x Locked into Next.js and Vercel ecosystem Chose Next.js for Vercel's great DX. Now want to switch hosts but next/image, ISR, and edge functions don't work properly elsewhere. Migration requires significant refactoring. Wish they'd chosen a more portable stack. After 1+ year of use Reported 7x Discovered commercial use requires paid plan Built and deployed project on Hobby plan. Added Stripe integration and launched. Later discovered commercial use violates terms. Had to upgrade to Pro immediately or risk suspension. Free tier wasn't really free for their use case. At product launch Reported 7x AI app burned through quotas in days Deployed AI-powered app expecting reasonable costs. Large payloads and frequent API calls exhausted Pro bandwidth quota within days. Projected overages of $160+/month made the project economically unviable on Vercel. First week after launch Reported 6x Team costs escalated with per-seat pricing … Functions timeout at scale performance Your serverless functions work fine in development but timeout under load in production. Documentation says 300 seconds but functions die at 60 seconds. Support can't resolve the issue. App becomes unreliable for users. Team grows beyond initial size pricing Started with a small team, now growing. Each new developer costs $20/month. Budget for 10 developers is $2,400/year just for Vercel seats, not counting usage. Alternatives with fixed team pricing become more attractive.

v0 used to be a good solution. I used it heavily every day, even though each message costs money. Lately, though, it has become a nightmare. I have wasted weeks building on it, and now I have to go back to working as a full-time developer just to fix things and keep building. v0 has become unreliable—conversations get deleted, messages disappear, deployments are erased, and new chats just use up credits and then stop working. At this point, it feels like the worst AI you could use or rely on. The Vercel team doesn’t seem willing to improve it, and things keep getting worse. It was fun for a while, but now I don’t think anyone in this community can honestly say v0 is safe to use, even for basic tasks. … I would also say that other AI tools such as v0 are also experiencing issues as well. Lovable for instance has been absolutely terrible on being a reliable solution. It is the reason I actually switched over to v0. I think all these tools will have issues tbh, at some point or another. And I can also become frustrated too. but I try and think that what they are all building, is not easy to do. … I am a heavy user of v0 and have been using it almost every day in the past. However, v0 has been frequently failing to process requests starting about a week ago. It seems the team is not prioritizing fixing this issue, which is disappointing. I believe that the team’s efforts to roll out new features are meant to make the product better and attract more users, but ironically, after the recent updates, my business operations have been interrupted for an entire week. The problem still hasn’t been solved so far. Without stable service, I don’t dare to use it, yet I am still paying $20 every month. Having such a terrible experience for a quarter of the time makes me question whether the v0 team even has professional developers and testers. Otherwise, how could a product with such critical problems be released as a production version? … In fact, the refresh issue is still unresolved. Many times, when I try to refresh, it keeps loading endlessly and not even the error page appears. Why would you release such an unusable version as the official release? This problem has been going on for a week now and there is still no sign of a solution. The efficiency in addressing the issue is extremely low. It makes me feel like you just pushed out an unstable version and then completely ignored the users, without bothering to roll back or fix the problem, just enjoying your weekend as usual. Meanwhile, customers like us are paying for subscriptions and simply wasting our time!