Edgio Sites is a Jamstack platform built from the ground up to run high-performance websites and web apps. It is the only Jamstack platform with an integrated world-class CDN (Edgio Performance) and a state-of-the-art web security suite. Edgio Sites enables you to build your web apps faster and leverage a global CDN in your application code to achieve optimal performance for your production traffic.
Build upon these performance improvements through Server-Side Rendering (SSR). Edgio Sites takes an SSR-first approach that enables you to render your web apps using our Cloud Functions at any scale. This allows your teams to focus on shipping features that your customers will love instead of maintaining and scaling your backend server infrastructure. Edgio Sites improves real-world performance through precise control over caching that allows you to cache highly dynamic content. Responses served from the CDN cache will achieve a comparable Time to First Byte (TTFB) as static cached content.
We also support static page generation:
  • At build time through Static Site Generation (SSG).

Getting Started

Edgio Sites provides Next, Nuxt, and Nuxt3 integrations through which you can deploy your websites and applications to Edgio. Getting started with Edgio Sites involves initializing your Edgio property through our CLI. Our CLI will then automatically detect your framework and configure your app accordingly.

Compute Regions

Edgio allows you to cache and deliver your content through any of our points of presence (POPs) around the world. However, your Edgio cloud code will run in one of the following global regions:
  • Americas: Eastern US and Western US
  • Europe: Ireland, UK, Western Europe, Northern Europe, Central Europe
  • Asia: Japan
  • Oceania: Australia
Enterprise customers may choose the region where their workloads will run. Alternatively, if you are using our free tier, then your workloads will run in the Eastern US region.
Edgio ensures high availability for your computing workloads by:
  • Running your code within two separate data centers.
  • Setting up automatic DNS failover between those data centers.
  • Load balancing computing requests between redundant processes.
  • Applying an Origin Shield to our cloud workers. If your requests are cacheable, then this allows more requests to be served from cache.