# VextJS > High-performance Node.js full-stack runtime documentation. The current frontend model is route-owned SSR plus hydration, optional Streaming SSR, and an esbuild build pipeline; React Server Components, Server Functions, and PPR are documented non-goals for this release. This is the concise English index. Use the complete English index for every public English page, or the documentation manifest for the authoritative bilingual inventory. ## Start here - [Introduction](https://devcodex-labs.github.io/vextjs/guide/introduction): VextJS is a full-stack Node.js framework for applications that need APIs, server-rendered React pages, or both. src/routes/ remains the URL authority while services, validation, security, cache, OpenAPI, and typed clients share the same request contracts. Y... - [Quick start](https://devcodex-labs.github.io/vextjs/guide/quick-start): VextJS provides the vext create command to create a runnable project. The default template proves the one-route model immediately: / renders React through res.render(), /api/hello returns JSON, and both use the generated example service. Choose API-only whe... - [Project structure](https://devcodex-labs.github.io/vextjs/guide/project-structure): VextJS follows the design philosophy of convention over configuration and implements automatic scanning, loading and registration through a fixed directory structure, without the need to manually configure route mapping or service injection. ## Frontend runtime - [Frontend Overview](https://devcodex-labs.github.io/vextjs/frontend/overview): This Frontend guide documents the current built-in Vext frontend capability: route-driven React 19 pages, SSR, hydration, nested layouts, frontend i18n, Fast Refresh, render refresh, code splitting, static assets, CDN upload, performance budgets, and hydrat... - [Rendering Modes](https://devcodex-labs.github.io/vextjs/frontend/rendering-modes): Vext supports a mixed full-stack frontend model without mixing server files into the browser bundle. - [Boundaries and Roadmap](https://devcodex-labs.github.io/vextjs/frontend/boundaries-and-roadmap): This page separates current frontend targets from future capability tracks. - [Data Flow](https://devcodex-labs.github.io/vextjs/frontend/data-flow): Frontend data in Vext starts on the server. Route handlers call services, prepare JSON-safe values, and pass them into res.render(). - [Performance Budgets](https://devcodex-labs.github.io/vextjs/frontend/performance-budgets): Performance budgets keep the React hydration path measurable. ## Runtime and operations - [routing](https://devcodex-labs.github.io/vextjs/guide/routing): VextJS uses conventional file routing + three-stage routing definition to automatically map file paths to URL prefixes, and declare specific routes inside the file through defineRoutes(). - [Service layer](https://devcodex-labs.github.io/vextjs/guide/services): VextJS adopts a layered architecture and concentrates business logic on the service layer (Service Layer). Service files are placed in the src/services/ directory, automatically scanned, instantiated and injected into app.services by the framework, and acce... - [Build (vext build)](https://devcodex-labs.github.io/vextjs/guide/build): vext build compiles server source code into deployable JavaScript products and, when frontend.enabled is true, bundles the browser client into dist/client/. The current version of vext build is designed as a production-target build: it statically injects pr... - [Deployment and production environment](https://devcodex-labs.github.io/vextjs/guide/deployment): This guide explains how to deploy a VextJS application into production, covering practices such as building, Docker containerization, Nginx reverse proxy, PM2 process management, log collection, and health checks. - [OpenAPI Documentation](https://devcodex-labs.github.io/vextjs/guide/openapi): VextJS has built-in automatic generation of OpenAPI documentation. Based on route validate and docs configuration, the framework generates an OpenAPI 3.0 JSON document and serves the default /docs page with the Vext Docs Renderer. Third-party documentation ... ## Support and machine-readable documentation - [Support and Services](https://devcodex-labs.github.io/vextjs/resources/support-and-services): A scoped, maintainer-led path for production reviews, migration work, and team enablement. - [Documentation Data and AI](https://devcodex-labs.github.io/vextjs/resources/documentation-data-and-ai): Canonical, machine-readable documentation assets and a privacy-first measurement boundary for VextJS. ## Machine-readable assets - [Documentation manifest](https://devcodex-labs.github.io/vextjs/docs-manifest.json): authoritative bilingual page metadata, locales, public applicability, relationships, and source hashes. - [Capability boundary](https://devcodex-labs.github.io/vextjs/capabilities.json): supported frontend/runtime capabilities and explicit exclusions. - [AI reference questions](https://devcodex-labs.github.io/vextjs/ai-gold-questions.json): citation-required evaluation prompts. - [Event contract](https://devcodex-labs.github.io/vextjs/docs-events.schema.json): optional privacy-preserving documentation event schema; no collector is enabled by default. - [Measurement definition](https://devcodex-labs.github.io/vextjs/docs-dashboard-definition.json): metric definitions and collection boundary. - [Complete English documentation index](https://devcodex-labs.github.io/vextjs/llms-full.txt): every public English page URL and summary, generated from the manifest. ## Other language - [Simplified Chinese index](https://devcodex-labs.github.io/vextjs/zh/llms.txt): Use the locale-specific Chinese index when the requested answer should be grounded in Simplified Chinese documentation.