Framework guides

Deploy frontend and full-stack frameworks to Easel.

Each guide documents the required setup, what the framework build produces, how that output maps to Easel infrastructure, supported capabilities, and known limitations.

Full-stack frameworks

Full-stack frameworks produce both static assets and server-side application code. Easel deploys each part of the build to the appropriate platform resource.

Next.js

App Router and Pages Router applications with support for server rendering, streaming, Server Actions, ISR, middleware, and image optimization.

Production-ready · Automatic setup

Read the Next.js guide

TanStack Start

Full-stack React applications with server functions, streaming, API routes, and prerendering through Nitro.

Production-ready · Nitro plugin required

Read the TanStack Start guide

Nuxt

Vue applications with server rendering, prerendering, Nitro server routes, middleware, and route rules.

Production-ready · Automatic setup

Read the Nuxt guide

React Router

React Router v7 framework-mode applications with loaders, actions, server rendering, resource routes, and streaming.

Production-ready · Deployment preset required

Read the React Router guide

SvelteKit

Svelte applications with server rendering, endpoints, form actions, hooks, streaming, and prerendering.

Production-ready · Adapter required

Read the SvelteKit guide

Static and client-rendered applications

Static applications produce HTML, JavaScript, CSS, and other browser-ready assets without a persistent application server.

Vite

Static sites and client-rendered single-page applications built with React, Vue, Preact, Solid, Svelte, and other Vite integrations.

Production-ready · Automatic setup

Read the Vite guide

Compare frameworks

The table describes the primary deployment path for each framework. Individual guides provide the complete capability matrix, version baseline, runtime behavior, and known limitations.

What framework support means

Framework support on Easel covers more than running a build command.

A documented framework integration defines how the framework’s generated output maps to Easel’s CDN, functions, routing, cache, image, and observability systems.

Build integration

Easel detects the framework, selects the appropriate build path, runs the production build, and validates that deployable output was generated.

When an adapter or preset is required, the framework guide identifies the exact package and configuration.

Runtime integration

Dynamic framework features are mapped to the appropriate Easel runtime.

Depending on the framework, this can include:

• Server-rendered routes
• API handlers
• Server Actions
• Loaders and actions
• Form actions
• Middleware
• Streaming responses
• Background work registered by the framework

Platform integration

Framework-native behavior connects to Easel platform services where supported.

This can include:

• CDN caching
• Runtime caching
• Path-based and tag-based revalidation
• Image optimization
• Environment variables
• Preview deployments
• Logs, metrics, and traces
• WAF and attack protection

Compatibility testing

Each framework guide identifies:

• The most recently tested framework version
• Required packages and configuration
• Supported capabilities
• Features that require additional setup
• Partial or experimental behavior
• Known unsupported features

How framework builds map to Easel

Different frameworks produce different combinations of static files, server handlers, routing metadata, and cached output.

Easel analyzes that output and deploys each component to the appropriate part of the platform.

Framework build
      │
      ├── Static assets ─────────▶ Easel CDN
      ├── Server routes ─────────▶ Easel Functions
      ├── Middleware ────────────▶ Request pipeline
      ├── Cached output ─────────▶ Runtime Cache
      ├── Image requests ────────▶ Image optimization
      └── Telemetry ─────────────▶ Observability

The exact deployment topology depends on the framework.

A Vite application may deploy entirely to the CDN. A Next.js application may also produce server functions, middleware, cached route output, and image-optimization requests.

Each framework guide includes a What Easel deploys section that documents this mapping explicitly.

Support levels

Framework-level support uses the following statuses.

Individual framework capabilities use a separate status vocabulary.

A feature is not marked partial merely because it requires configuration.

Using an unlisted framework

Easel can deploy many projects that are not listed on this page.

Static sites and applications that produce browser-ready HTML, JavaScript, CSS, and assets can often use the standard static deployment path.

Frameworks that emit a compatible server deployment format may also build successfully.

However, an unlisted framework does not currently have:

• A documented compatibility contract
• A maintained capability matrix
• A tested version baseline
• Framework-specific runtime guarantees
• Published known limitations

For a project that produces only static output, start with the Vite guide.

For a framework that produces server output, review the generated deployment artifacts and contact Easel before relying on the integration for production workloads.

Request a framework guide

Moving from another platform

Existing applications can often move to Easel without changing their framework architecture.

Easel supports common framework adapters, presets, build conventions, and compatible deployment configuration from other platforms.

The migration guide covers:

• Importing an existing repository
• Build and install settings
• Environment variables
• Domains and DNS
• Redirects and rewrites
• Functions and runtime behavior
• Caching and revalidation
• Preview deployments
• Observability
• Rollback and production cutover

Read the migration guide · Migrate from Vercel · Migrate from Netlify

Compatibility policy

Easel tests each documented integration against representative applications covering the framework capabilities listed in its guide.

The version shown on an individual guide is the most recently verified baseline. Nearby stable releases may also work, but newly released or experimental framework features can require an Easel runtime or integration update.

Before upgrading a production application:

1. Create a preview deployment with the new framework version.
2. Verify builds, dynamic routes, caching, middleware, and environment variables.
3. Review the framework guide for new limitations or configuration changes.
4. Promote the deployment only after application-specific testing.

Material compatibility changes are documented in Easel release notes and reflected in the corresponding framework guide.