We're thrilled to join forces with Fanout. The integration of Fanout technology into our network will help enable real-time app development at the edge with improved time-to-market, reduced…

Our new partnership lets you deploy Glitch apps to Compute@Edge, making it even easier to build high-quality, customized digital experiences on our edge cloud platform.

We’re introducing Cloud Deploy, a wizard that helps you start building on Compute by deploying and customizing templates, and sets you up with an automated deployment workflow and best…

Many websites today are really applications, and we should be building them as such. To do that, we need application architectures and networks that are capable of supporting fast, secure…

As we look back to celebrate the 30th anniversary of the website, it’s also worth thinking about the next 30 years. There are a couple of areas where we — as engineers, developers, and…

Fastly customers have been using our Fiddle tool for years to try out ideas for edge logic in VCL. With the advent of Compute last year, we made our edge compute network accessible to any…

In this tutorial, we’ll walk you through the basic steps of outputting messages to STDIO and tailing that output with the Fastly CLI as well as configuring a log streaming endpoint, emitting…

For a limited time, you can get $100k/month in edge compute credits for nine months, as an incentive to start building with Compute now.

When we acquired Signal Sciences, we put a stake in the ground as a company that cares about the complete delivery path and making it not just resilient and performant, but inherently secure…

With JavaScript now available for WebAssembly and Compute, you can get started faster than ever with a language you already know, while ensuring the speed and security you need in a…

As you start to build more at the edge, it becomes ever more important to deploy edge logic in the same way you deploy changes to your own applications and infrastructure. Today, we’ll take…

We experienced a global outage due to an undiscovered software bug that surfaced on June 8 when it was triggered by a valid customer configuration change. Here's a rundown of what happened…