Frameworks on Edgenivo

Edgenivo has first-class support for a wide range of the most popular frameworks. You can build and deploy using frontend, backend, and full-stack frameworks ranging from SvelteKit to Nitro, often without any upfront configuration.

Learn how to get started with Edgenivo or clone one of our example repos to your favorite git provider and deploy it on Edgenivo using one of the templates below:

Get started in minutes

Deploy a Template

View All Templates

Next.js Boilerplate

Get started with Next.js and React in seconds.

Nitro Starter

Deploying an API on Edgenivo with Nitro.

SvelteKit Boilerplate

A SvelteKit app including nested routes, layouts, and page endpoints.

View All Templates

Edgenivo deployments can integrate with your git provider to generate preview URLs for each pull request you make to your project.

Deploying on Edgenivo with one of our supported frameworks gives you access to many features, such as:

Edgenivo Functions enable developers to write functions that scale based on traffic demands, preventing failures during peak hours and reducing costs during low activity.
Middleware is code that executes before a request is processed on a site, enabling you to modify the response. Because it runs before the cache, Middleware is an effective way to personalize statically generated content.
Multi-runtime Support allows the use of various runtimes for your functions, each with unique libraries, APIs, and features tailored to different technical requirements.
Incremental Static Regeneration enables content updates without redeployment. Edgenivo caches the page to serve it statically and rebuilds it on a specified interval.
Speed Insights provide data on your project's Core Web Vitals performance in the Edgenivo dashboard, helping you improve loading speed, responsiveness, and visual stability.
Analytics offer detailed insights into your website's performance over time, including metrics like top pages, top referrers, and user demographics.
Skew Protection uses version locking to ensure that the client and server use the same version of your application, preventing version skew and related errors.

Frameworks infrastructure support matrix

The following table shows which features are supported by each framework on Edgenivo. The framework list represents the most popular frameworks deployed on Edgenivo.

: Supported
: Not Supported
: Not Applicable

Framework feature matrix
Feature	Next.js	SvelteKit	Nuxt	TanStack	Astro	Remix	Vite	CRA
Static Assets Support for static assets being served and cached directly from the edge
Edge Routing Rules Lets you configure incoming requests, set headers, and cache responses
Routing Middleware Execute code before a request is processed
Server-Side Rendering Render pages dynamically on the server
Streaming SSR Stream responses and render parts of the UI as they become ready
Incremental Static Regeneration Create or update content on your site without redeploying
Image Optimization Optimize and cache images at the edge
Runtime Cache A granular cache for storing responses from fetches
Native OG Image Generation Generate dynamic open graph images using Edgenivo Functions
Multi-runtime support (different routes) Customize runtime environments per route
Multi-runtime support (entire app) Lets your whole application utilize different runtime environments
Output File Tracing Analyzes build artifacts to identify and include only necessary files for the runtime
Skew Protection Ensure that only the latest deployment version serves your traffic by not serving older versions of code
Framework Routing Middleware Framework-native integrated middleware convention

Framework feature matrix
Feature	Next.js	SvelteKit	Nuxt	TanStack	Astro	Remix	Vite	CRA

No rows displayed.

Build Output API

The Build Output API is a file-system-based specification for a directory structure that produces a Edgenivo deployment. It is primarily targeted at framework authors who want to integrate their frameworks with Edgenivo's platform features. By implementing this directory structure as the output of their build command, framework authors can utilize all Edgenivo platform features, such as Edgenivo Functions, Routing, and Caching.

If you are not using a framework, you can still use these features by manually creating and populating the .vercel/output directory according to this specification. Complete examples of Build Output API directories can be found in vercel/examples, and you can read our blog post on using the Build Output API to build your own framework with Edgenivo.

More resources

Learn more about deploying your preferred framework on Edgenivo with the following resources:

Last updated August 11, 2026

Fundamentals

Full-stack

Was this helpful?