| Feature | vagejs | Next.js |
|---|---|---|
| License | MIT | MIT |
| Templates | TypeScript functions returning HTML | React components (JSX/TSX), Server Components by default |
| JavaScript sent to visitors | None by default | React, to make client components interactive |
| Output | Static files | A Node.js server, a container, or a static export with fewer features |
| Markdown | Built in, with frontmatter | MDX with the @next/mdx package; frontmatter isn't supported by default |
| Sitemap and robots.txt | Built in | sitemap.ts and robots.ts files you write |
| llms.txt for your site | Built in | Not built in |
| Checks before publishing | vage check |
Not built in |
| Spam-injection protection | Link lock, hidden-link checks, vage verify |
Not built in |
| AI coding assistants | AGENTS.md, vage info --json, JSON check results |
Extensive: AGENTS.md in new projects, docs bundled with the package, an MCP endpoint in the dev server |
| Hosting | Any static host | A Node.js host for all features; static export runs anywhere |
Where Next.js is stronger
- Applications. Logins, dashboards, personalised pages, forms that talk to your server, data that changes on every request. vagejs doesn't do any of that.
- React. If your team already builds in React, Next.js lets you reuse components and skills.
- AI tooling for apps. Next.js has invested heavily in guidance for coding agents, including a live MCP endpoint.
Where vagejs is stronger
- Speed by default. No framework JavaScript reaches visitors, so content pages stay small and fast without tuning.
- Simple hosting. The output is a folder of files: no server to run, patch or pay for.
- Content basics included. Markdown, sitemaps, robots.txt, llms.txt and structured data work without packages or code.
- Guardrails. Pre-publish checks and protection against injected spam are part of every build.
Which to choose
If the site is really an application, choose Next.js. If it's content (a company site, documentation, a blog), vagejs gives you a faster, simpler site with less to maintain. Some teams use both: Next.js for the app, and a static site for marketing and docs.
Sources: Next.js docs, Server and Client Components, static exports, MDX, AI agents guide. Checked October 2026.