What is Easel?

Easel is a cloud platform for building, deploying, delivering, and operating modern web applications.

Connect a Git repository or deploy from the CLI. Easel builds the application, publishes static assets to its delivery network, runs server-side code in Functions, protects incoming traffic, and records request-level telemetry.

What you can deploy

Easel supports static sites, client-rendered applications, and full-stack JavaScript frameworks. Supported framework integrations include Next.js, TanStack Start, Nuxt, React Router, SvelteKit, and Vite.

A framework build can produce several kinds of output:

• Static HTML, JavaScript, CSS, fonts, and images
• Server-rendered routes and API handlers
• Middleware and routing metadata
• Cacheable pages and application data
• Image optimization requests

Easel maps each output to the appropriate platform service.

The platform in one request

A request to an Easel deployment passes through the delivery network before it reaches application code.

Visitor
  ↓
Easel delivery network
  ├─ security controls
  ├─ redirects and rewrites
  ├─ CDN cache
  └─ static asset lookup
       ↓ when dynamic execution is required
Easel Function
       ↓
Database, API, or Runtime Cache

A request may complete at the edge without invoking a Function when it is blocked, redirected, served from cache, or matched to a static asset.

Deployment workflow

Every successful build creates an immutable deployment with its own URL. Git branches and pull requests can receive stable Preview URLs, while production domains point to the deployment currently assigned to Production.

This separation lets teams validate a build before release and roll production traffic back without rebuilding.

What Easel manages

Easel manages:

• Build execution and framework detection
• Deployment artifacts and immutable deployment URLs
• Static asset delivery and HTTP caching
• Dynamic Functions and runtime resources
• Domain routing and managed TLS
• Firewall controls and deployment protection
• Logs, metrics, traces, and request diagnostics

Your application remains responsible for its own business logic, authentication and authorization, data model, external services, and secure handling of credentials.

Where to go next

• Follow Getting started to deploy an application.
• Read Platform architecture to understand the request and deployment model.
• Review Frameworks for integration-specific behavior.
• See Core concepts for the terminology used throughout the documentation.