Hey Vercel community 
Iām Mobeen, solo founder behind Nextly. Just joined the Vercel Open Source Program (Spring 2026 cohort) and wanted to introduce the project here.
What is Nextly?
An open-source, MIT-licensed application framework that lives inside Next.js. You can define your content schema two ways: in TypeScript code, or visually in an in-app Schema Builder. Both produce the same collections, fields, and APIs, mixable per collection. No separate server, no SaaS lock-in, no per-seat pricing.
Why it exists
I spent a decade building content-driven apps, from WordPress core contributor days to fully Next.js. Every CMS in the ecosystem forced a tradeoff: Payload nailed code-first but had no visual workflow, Strapi had the visual side but ran outside Next.js with a weak code-first story. Nextly is what happens when you stop choosing.
Stack
- Next.js 16, React 19, TypeScript end-to-end
- Drizzle ORM with Postgres, MySQL, SQLite adapters
- Vercel Blob, S3, R2, UploadThing storage
- JWT auth, RBAC, Lexical editor, 26+ field types, hooks, email, plugins
Links
- GitHub: https://github.com/nextlyhq/nextly
- Site: https://nextlyhq.com
- Docs: https://nextlyhq.com/docs
- Quick start:
npx create-nextly-app@alpha my-app
Would love feedback from anyone building content-driven Next.js apps, especially if you have felt this friction. Happy to dive into architecture, the dual-approach pipeline, or the roadmap.
Big thanks to the Vercel team for the OSS Program support 