Pricing and usage
Understand the resources Easel meters and how application behavior affects usage.
Easel usage is driven by the work required to build, deliver, and execute an application. Included allowances, on-demand ranges, and regional rates live in Pricing and on the pricing page.
This guide explains the usage model. It does not duplicate price numbers that can change.
Main usage categories
Builds
Build usage includes dependency installation, framework compilation, output analysis, and publication. Rebuilding the same source can still consume build resources when configuration or dependencies differ.
Bandwidth and delivery
Delivery usage includes bytes returned through Easel's network. Static assets, cached responses, and Function responses can all contribute to transfer.
Function execution
Function usage is based on Function Requests and Function Duration. Function Requests are logical requests into your functions, not cloud-provider invoke counts. Post-response work continues to consume Function Duration until it completes or reaches the applicable limit.
In-function concurrency can allow one active instance to serve overlapping requests. Do not assume that request count maps one-to-one to instance count or invocation count.
Image optimization
Image Optimization is metered as Image Transformations on cache MISS and STALE only. See Image Optimization pricing.
Observability
Logs, metrics, traces, retention, and export can have plan-specific allowances or limits.
Security
Some security capabilities or higher limits may depend on the workspace plan.
What reduces usage
- Serve immutable assets with long-lived cache headers.
- Cache eligible dynamic responses at the CDN.
- Use Runtime Cache for repeated application data or computation.
- Avoid unnecessary rebuilds in monorepos.
- Keep Function work bounded and move durable jobs to a queue or background system.
- Control verbose application logging in production.
Preview and Production usage
Preview deployments use platform resources in the same way as Production deployments. A high-volume Preview or automated branch workflow can therefore contribute meaningful build, bandwidth, Function, and observability usage.
Usage attribution
Inspect usage in the dashboard by workspace and project. Breakouts by deployment, environment, and resource category appear where the product exposes them.
Avoiding unexpected usage
- Review build triggers and monorepo path filters.
- Configure cache policies intentionally.
- Inspect Function duration and request volume.
- Set retention and export policies appropriate for the application.
- Review plan limits before a launch or migration.
See Limits for technical ceilings and the pricing page for current commercial terms.