⌘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.
Seongsu0306 1361 Additional diagnostic information: I tested the current Production deployment directly with authenticated `vercel curl`, which generated a Deployment Protection bypass token successfully. Current Production deployment: reveries-campaign-b4wkpa1e9-seongsu0306-1361s-projects.vercel.app `vercel ls` reports: Status: Ready Environment: Production `vercel inspect` reports: Deployment ID: dpl_BmybYWXNn3XrNYR9caS1zc6nHQaN Target: production Status: Ready Aliases: - campaign.reveries.kr - reveries-campaign.vercel.app - reveries-campaign-seongsu0306-1361s-projects.vercel.app However, authenticated: vercel curl https://reveries-campaign-b4wkpa1e9-seongsu0306-1361s-projects.vercel.app/ -I still returns: HTTP/1.1 404 Not Found X-Vercel-Error: NOT_FOUND The build logs also confirm that the application built successfully: - Next.js 16.3.4 compiled successfully - TypeScript completed successfully - `/` route exists - all application routes were generated - Build Completed in /vercel/output - Deploying outputs... - Deployment completed - final status: Ready So the generated Deployment URL itself returns a platform-level NOT_FOUND even though the deployment is Ready and the build output contains `/`. This now appears to be a deployment serving / edge routing registration issue rather than a DNS or application routing problem. Could a Vercel engineer inspect the deployment-to-edge routing registration for: Project: reveries-campaign Deployment: dpl_BmybYWXNn3XrNYR9caS1zc6nHQaN Domain: campaign.reveries.kr
Amy Egan Thanks for reporting this. I'm checking with the team about it
Romlenzotti Hi @amyegan Thanks for your message. On the example I finally fixed the problem. ```json { "$schema": "https://openapi.vercel.sh/vercel.json", "bunVersion": "1.4.x", "framework": "bun" // this line is required, but missing in the example } ``` But in the vercel backoffice Bun framework is missing. This is why I haven't tried that, and in my mind bunVersion should trigger bun automatically. After that I faced to another issue. One the dependencies (universal-github-app-jwt) of octokit to consume github API use internal imports to resolve crypto lib depending on the : ```json { "imports": { "#crypto": { "node": "./lib/crypto-node.js", "default": "./lib/crypto-native.js" } }, ``` import { subtle, convertPrivateKey } from "#crypto"; // >> unable to resolve #crypto But in your Bun integration, theses imports aren't resolved. Use a bun patch doesn't solve this problem. At this step, I decided to back forward to a Node.js stack which is more stable ;) (I assume the Bun support in vercel still in beta). Let me know if you need more details on the different issues. See you
Amy Egan Glad you got it working! I'll add these notes to the internal ticket for the team
