Hey Vercel community 👋
Wanted to share Nextly, the open-source app framework I've been building for Next.js, along with the sites already running on it.
What Nextly is, in one line: an MIT-licensed Next.js framework where you can define your content schema in TypeScript code OR build it visually in an in-app Schema Builder. Both paths produce the same collections, fields, and APIs. Mixable per collection.
The dual approach in action:
Code-first:
import { defineCollection, text, richText } from "nextly";
export default defineCollection({ slug: "posts", fields: [ text({ name: "title", required: true }), richText({ name: "body" }), ],});
Or visually, in the in-app Schema Builder:
Either way, you get a typed admin dashboard:
Production sites already shipped on Nextly:
🌐 CodexSpot — Curated developer AI tools directory 🌐 Rext AI — AI Content Studio 🌐 Revnix — AI Development Agency 🌐 Personal Portfolio — My personal portfolio site
All deployed on Vercel, all running the same Nextly framework.
Stack: Next.js 16, React 19, TypeScript end-to-end, Drizzle ORM (Postgres / MySQL / SQLite), storage adapters for Vercel Blob, S3, R2, UploadThing. Auth + RBAC, Lexical editor, 26+ field types, lifecycle hooks, plugin system. Deploys as a regular Next.js app, so vercel deploy is the whole story.
Try it:
npx create-nextly-app@alpha my-appLinks
- GitHub: https://github.com/nextlyhq/nextly
- Site: https://nextlyhq.com
- Docs: https://nextlyhq.com/docs
Proud to be in the Vercel Open Source Program (Spring 2026 cohort). Huge thanks to the Vercel team.
Would love feedback, especially on the Schema Builder UX and the dual approach concept. Happy to answer anything.