⌘K
NextBlock™ CMS Just submitted our application for **NextBlock CMS**! 🚀 NextBlock is an open-source, full-stack CMS framework built natively for **Next.js 16 (App Router + RSC)** and **Supabase (PostgreSQL JSONB)**. We’ve focused on: * **Zero-Config 1-Click Deploy:** Automated Supabase database migrations on build. * **100/100 Lighthouse Defaults:** Tiptap visual editor renders PostgreSQL JSONB directly into React Server Components, eliminating client hydration overhead and HTML sanitization taxes. * **Cortex AI & Native MCP:** Model Context Protocol server support (`/api/mcp`) for deterministic, schema-constrained block synthesis. * **GitHub:** https://github.com/nextblock-cms/nextblock * **Live Sandbox:** https://cms.nextblock.dev Looking forward to the review process and collaborating with the Vercel DX team! 🧱
Axyl1410 Hi! I applied for the Summer 2026 Vercel OSS Program, but I’m not sure whether my application was successfully submitted. I also didn’t receive a confirmation email. Is there any way for applicants to verify whether their application was received, or is there normally no confirmation email after submitting the form? I’d like to avoid submitting a duplicate application if my original submission went through. Thanks!
Amy Egan If you reached the final page that says, "Thank you," then your application was received :) You'll get an email about a week after applications close letting your know whether or not your project was accepted
system Hi there! I'm just a bot here to share some info that might help you before a human arrives. If your account is eligible, you can use our new self-service recovery flow: 1. Go to vercel.com/login 2. Choose to sign in using the email + one-time password (OTP) option. 3. Select Use another sign-in method 4. Verify your identity using the GitHub, GitLab, or Bitbucket account previously linked to your Vercel account 5. Follow the remaining prompts to complete the recovery process If you've ever set up a passkey, possibly on another device, you can use that to get back into your account and update 2FA settings yourself. You can also use recovery codes if you've stored those in a safe place that you can still access. If you are unable to access your account using the steps above, you can open a support case using the Start 2FA recovery option on the Two-Factor Authentication login screen. **Please do not publicly post account details, like your email address, that could help an attacker gain access to your account in the future.** There's no need to open an additional case if you already have one open. Thanks for your patience while the team works to resolve all cases as quickly as possible while keeping everyone’s accounts safe and secure. A human should be here soon to help.
ricardoffmendes Thanks. We tried exactly this flow on 9 October: after signing in with email and the one-time code, the 2FA screen only shows "Use a Recovery Code Instead" and "Start 2FA recovery". There is no "Use another sign-in method", so the GitHub verification is not offered for this account, and the case opened through "Start 2FA recovery" (TNS_012Aa7d36q5eC3Uv) was declined on 10 October. She will retry the flow once more and we will add a screenshot of the 2FA screen here. We would appreciate a human looking at the case.
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/domains/troubleshooting
Jonathan Experience the same issue with `.ai.id` domain. Looking forward for any response from Vercel team.
Miqdad Badjuber Same issue here with antislop.ai.id (project antislop-website). Domain stuck on "Verification Required", dashboard asks for TXT at _vercel.ai.id. Vercel's agent confirmed it treats ai.id as the apex domain. Please sync the internal Public Suffix List with upstream, or share an ETA. Thanks.
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Nicosuaya 2179 I am seeing the same issue on a Pro team where the connected account is a confirmed Owner. Vercel Support directed me here. Read-only checks on October 12, 2026: - list_teams returns the correct team, and get_team succeeds. - list_projects without a team selector returns the existing team-owned project. - The returned project accountId and the team ID from list_teams are identical in a character-by-character comparison. - list_projects with that exact teamId returns an empty list. Using the verified slug also returns an empty list. - get_project for the existing project succeeds without an explicit team selector, but returns 404 with the correct teamId or slug. Before pausing writes, create_git_project with an explicit teamId and deploy:false returned 403, saying the account did not have permission to create the project. No project or deployment was created. Two OAuth reconnections did not resolve it. During the latest consent flow, the team row visibly showed Authorized before Allow Access was completed. The connection lists Projects Read/Write permissions. Could the Vercel MCP team clarify whether the Authorized badge can still coexist with a restricted project grant, what the team-row Configure control covers, and how an end user can inspect the effective project scope of an existing ChatGPT grant? Is there a supported fix for the different results with implicit versus explicit team scope? This is an MCP/API authorization issue, not a website-level 404. I am not trying to bypass the explicit scope or change production settings. Account details, repository names, team/project IDs, request IDs, source code, and credentials are omitted from this public reply. Please indicate a secure channel if identifiers are needed. Update: list_deployments, limited to one result for the same existing project, also succeeds without a team selector and returns 403 when the exact verified teamId is supplied. The asymmetry therefore affects both project and deployment reads.
yasoob Hi eric, thanks for letting us know. Could you please try again? The Prisma team has just pushed out a fix.
eric Hi yasoob, thanks for the follow-up, and sorry for the late reply. I just tested it again and the issue is resolved now. I do want to share some feedback, though. Because of this error, we had to remove the Prisma Postgres integration from our service and migrate to a different database provider. An issue like this takes the whole service down, not just one feature. It took a long time to get a response, and in the meantime there was nothing we could do on our end. No status update, no workaround, no escalation path. For integrations that sit on the critical path, like database auth/SSO, a faster response channel or at least visible incident status would make a big difference. Thanks again for looking into it.
