Lay vs Vercel Comments
Vercel Comments is a feedback feature built into the Vercel deployment platform. When a team member opens a Vercel preview deployment, they can click anywhere on the page to leave a comment. The comment appears as a pin on the deployment, visible to other team members with Vercel accounts. It is tightly integrated with Vercel's preview workflow.
Lay is an independent feedback SDK. It installs via npm, wraps your application with a provider component, and works on any hosting provider. The two tools overlap in one use case — team feedback on staging — but diverge significantly in scope, architecture, and flexibility.
How Vercel Comments Works
Vercel Comments activates automatically on preview deployments for teams on Vercel Pro or Enterprise plans. Team members open a preview URL, click the comment button (or use a keyboard shortcut), and click on the page to place a comment. The comment is tied to the specific deployment preview.
The workflow is streamlined for its specific use case. There is nothing to install, no SDK to configure, and no onboarding for team members already on Vercel. Comments are visible on the preview deployment and in the Vercel dashboard.
This tight platform integration is both the strength and the limitation. Vercel Comments works seamlessly within the Vercel ecosystem. Outside of it — on other hosting platforms, in production, for end users — it does not work at all.
How Lay Works Differently
Lay is decoupled from any hosting platform. It is an npm package that you install in your React application:
- Install
@uselay/sdk - Wrap your app with
<LayProvider projectId="..." mode="review" /> - Press C to enter comment mode, click any element to anchor feedback
The feedback is anchored to the DOM element, not to a deployment or a pixel position. This means the same feedback system works on localhost, staging, preview deployments, and production — regardless of whether the application is hosted on Vercel, AWS, Netlify, Railway, or self-hosted infrastructure.
Lay has two modes: review mode for internal team feedback on staging, and support mode for end-user feedback in production. Review mode is comparable to Vercel Comments' use case. Support mode has no equivalent in Vercel Comments — it lets any user point at a broken element and submit feedback without needing an account on any platform.
Feature Comparison
The Platform Lock-In Question
Vercel Comments works if three conditions are true simultaneously: your application is hosted on Vercel, your team has Vercel accounts, and you only need feedback on preview deployments. If any of those conditions changes — you migrate to a different host, you need feedback from external stakeholders, or you want feedback in production — the feature stops working.
This is not a criticism of Vercel. Platform-native features are powerful within their ecosystem. But feedback is a workflow that often needs to span environments:
- Development: Developers test locally. Vercel Comments does not work on localhost. Lay works everywhere the application runs.
- Staging: Both tools work here. Vercel Comments on preview deployments, Lay on any staging environment.
- Production: End users encounter bugs in production. They cannot leave Vercel Comments (it requires a Vercel account). Lay's support mode captures the same structured context from production users.
- Migration: If you move from Vercel to another platform, all Vercel Comments history is tied to the platform. Lay's data lives in your Supabase backend, portable regardless of hosting.
Context Depth
Vercel Comments captures basic positional data and the comment text. Lay captures the full Context Stack: element identity (tag, text, role, CSS selector), computed styles (colors, fonts, spacing, z-index), accessibility data (contrast ratio, ARIA attributes), viewport state (dimensions, device, scroll position), a cropped screenshot with element overlay, and AI classification.
The AI layer is the largest functional gap. Lay automatically classifies every comment by category and urgency, generates developer triage with likely causes and investigation starting points, and clusters semantically similar reports to reduce duplicate noise. Vercel Comments is an annotation layer — it places the comment but does not analyze it.
When feedback syncs to Linear, Lay generates Developer Handoff Packs: structured issue bodies containing the original comment, element metadata, annotated screenshot, and AI-generated triage. The developer opens the Linear issue and has everything needed to start fixing — no reproduction required.
When to Use Vercel Comments
Vercel Comments is an excellent choice when:
- Your team is fully on Vercel — If your application is deployed on Vercel and all reviewers have Vercel accounts, the zero-setup experience is unbeatable. No SDK to install, no configuration to maintain.
- You only need preview deployment feedback — For teams whose feedback workflow is "review the preview, leave comments, merge or revise," Vercel Comments handles this natively.
- Lightweight is enough — If you do not need AI classification, element metadata, accessibility data, or issue tracker sync, Vercel Comments' simplicity is a feature, not a limitation.
When to Use Lay
Lay is the better fit when:
- You need hosting flexibility — Lay works on any hosting platform. If you might migrate, or if you deploy to multiple environments, platform-locked feedback is a risk.
- End users need to give feedback — Lay's support mode lets production users point at broken elements. The system captures the same six-layer context stack without requiring any account. This is Lay's primary use case — replacing chat widgets and support emails with structured, element-anchored reports.
- AI enrichment saves triage time — Automatic classification, urgency scoring, developer triage, and semantic clustering turn raw feedback into actionable engineering work without manual sorting.
- You want bidirectional Linear sync — Lay creates Linear issues with full context and syncs status changes back. Resolving in Linear resolves in Lay.
- You need feedback in production and staging — The same SDK, same anchoring, same context stack works in every environment. Review mode for your team, support mode for your users.
- Data portability matters — Lay's data lives in Supabase. You can self-host the backend, query it directly, or migrate without losing history.
The choice comes down to scope. Vercel Comments is a platform feature for team annotation on previews. Lay is a feedback system for the full lifecycle — team review on staging, user feedback in production, AI triage, and developer handoff.