Discover your complete package

Fastly Full Site Delivery

Full-Site Delivery uses Fastly’s global content delivery capabilities to cache and accelerate the delivery of your HTTP-based file content such as video, images, CSS, Javascript files, as well as HTML and API responses. 

Request

An HTTP request. Requests include those made by the end user to Fastly, between Fastly POPs, and from Fastly POPs to origin.

Service

A logical configuration that captures a selection of inbound traffic (using domains or service pinning), connects it to origin servers, applies rules, and runs edge code.

Backend

A non-Fastly internet host from which Fastly will fetch content to serve in response to end-user requests. Also known as an Origin.

Purge

An action that explicitly invalidates or expires an object in the Fastly edge cache. A soft purge will mark the object as stale, while a hard purge will invalidate the object.

Health Checks

A regular HTTP request made by Fastly to an origin server to check that the origin is in a fit state to accept traffic.

Load Balancer

The practice of selecting a backend server from a pool of available, appropriate and often functionally identical servers based on a strategy designed to maximize performance and availability.

Log Streaming

We support real-time log streaming of data that passes through Fastly. We support a number of protocols that allow you to stream logs to a variety of locations, including third-party services, for storage and analysis.

Fastly TLS

A Fastly product that provides TLS provisioning with Fastly-managed or customer-managed certificates. Suitable for 1-1000 domains.

Domains

An internet hostname, such as my.host.example.com or www.example.com that is associated with a service. 

Fastly Image Optimizer

A Fastly product that allows images passing through the Fastly edge cloud to be transformed as required by the client.

Monthly Image Requests

When loading your website and sending a request for the image, the user’s web client will use the website’s CSS to determine which version of the image is appropriate for the device. It will send a request to your servers for the image with those parameters, and the image optimization solution will apply the transformation to the image response.

Billing for Fastly IO is based on the number of monthly image requests that are processed and delivered. 

Gold Support

Fastly will respond to the report of an Incident by troubleshooting the causes of the Incident and resolve them if caused by factors within Fastly's control, or provide information to those who can resolve the factors if the factors are within others' control, as follows in documentation.

Enterprise Support

Fastly will respond to the report of an Incident by troubleshooting the causes of the Incident and resolve them if caused by factors within Fastly's control, or provide information to those who can resolve the factors if the factors are within others' control, as follows in documentation.

Fastly Academy

Build your foundation of essential Fastly concepts and terms you will need before diving into more advanced courses in Fastly Academy.

Next-Gen WAF

The Fastly Next-Gen WAF (powered by Signal Sciences) is a web application firewall that monitors for suspicious and anomalous web traffic and protects, in real-time, against attacks directed at the applications and origin servers that you specify.

Base Platform

The Signal Sciences platform is an application security monitoring system that proactively monitors for malicious and anomalous web traffic directed at your web servers. The system is comprised of three key components:

A web server integration module

A monitoring agent

Our cloud-hosted collection and analysis system

Workspaces

A Workspace (also known as a Site) is a user-defined set of rules and settings for applications and origin servers.

Edge Rate Limit Counters

When you create a rate limiting policy, you define the criteria to track requests counts and their rates over time. Accumulated counts are converted to an estimated rate computed over the time window you specify: either 1s, 10s or 60s. Rates are always measured in requests per second (RPS).

Edge Rate Limiting Penalty Boxes

Penalty boxes allow you to penalize clients for exceeding rate limits you set. Accumulated counts are converted to an estimated rate computed over one of three time windows: 1s, 10s or 60s. Rates are always measured in requests per second (RPS).

Advanced Rate Limiting Rules

Advanced rate limiting rules: block or tag requests from individual clients when a threshold (e.g., 100 requests in 1 minute) is passed. 

Client identifier

The parts of requests used to identify an individual client.

Requests per Second (RPS)

The maximum number of requests per second to count within the detection window before enacting the rate limiting policy. The lowest rate limit supported by this feature to demonstrate effective behavior is 100 RPS.

Gold Security Support

Fastly will respond to the report of an Incident by troubleshooting the causes of the Incident and resolve them if caused by factors within Fastly's control, or provide information to those who can resolve the factors if the factors are within others' control, as follows in documentation.

Enterprise Security Support

Fastly will respond to the report of an Incident by troubleshooting the causes of the Incident and resolve them if caused by factors within Fastly's control, or provide information to those who can resolve the factors if the factors are within others' control, as follows.

Response Security Service

Fastly offers Fastly Next-Gen WAF (powered by Signal Sciences) customers a Response Security Service (RSS) that provides your organization with enhanced access to our Customer Security Operations Center (CSOC) team and periodic consultation with a Designated Security Specialist for strategic security solutions reviews and planning. 

Compute@Edge 

One of the two platforms offered by Fastly to run edge code. Compute@Edge services run Webassembly binaries that are compiled outside of Fastly using tools that we provide in the Fastly CLI. 

Compute Requests

Compute requests represent a count of the number of times you invoke a function instance. Each incoming request creates one function instance.

CPU time

CPU time represents the sum of the total time spent by the CPU running your code.

Compute Duration

Compute duration represents the total memory allocation over time required to process a compute request. We measure memory allocation in GB-seconds and calculate it based on the time it takes for a function instance to execute, multiplied by the memory allocated to that function.

Services

A logical configuration that captures a selection of inbound traffic (using domains or service pinning), connects it to origin servers, applies rules, and runs edge code. Service versions are used to create immutable configurations and apply multiple changes to a service in a single deployment. The mechanism used to run edge code and other logic on requests processed by the service depends on the service type, which can be Compute@Edge or VCL.

Config Store

Config stores are a type of versionless container that allow you to store often repeated data as key-value pairs that can be read from the edge and shared by multiple Compute@Edge services in your account.

Entries per Config Store

You can store environment variables, redirect lists, and more in Config Store, where they can be shared across services and referenced in your edge logic.

KV Store

KV store is a key-value store that provides high performance reads and writes across Fastly’s network to enable more powerful edge applications.

KV Store Class A Operations

Operations that mutate the state of an object

KV Store Class B Operations

Operations that read the state of an object.