⌘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 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.
Thiego Thanks. I reviewed the 404 debugging guide. The common 404 causes listed there do not appear to match this case: - the active Preview deployment exists and is READY - the immutable deployment URL is correct - /login loads successfully - initial _next assets load successfully - build output is healthy - there is no vercel.json - repository configuration does not rewrite or cache /login POST requests - Deployment Protection/OIDC access is working The 404 only occurs after submitting the Next.js Server Action. The POST /login response is returned with: x-vercel-cache: HIT and contains an x-nextjs-deployment-id from an older deployment. The stale Server Action/RSC payload then references build-specific assets from that older deployment, and those asset requests return 404 on the current immutable deployment. So the 404 appears to be a downstream symptom of the stale cached Server Action response, rather than a missing route or deployment-output issue. Could a human from the Edge/Next.js platform team please review the x-vercel-cache: HIT / stale x-nextjs-deployment-id behavior?
