Website · Documentation · Pricing

Cost calculator

Your traffic

Choose a workload. We’ll estimate traffic and requests for you.

Estimated monthly costs

USD per month, before tax. Load balancing and unpriced extras are excluded.

What’s included?

Estimates cover cacheable content. Origin and optional services are added only when you enter their rates. Plans differ in features and coverage; check their terms before buying.

Advanced settings
Split traffic between regions

Percentages must total 100%. The same split applies to bytes and requests. CloudFront charges by serving edge location; this is an approximation. Shared free allowances are allocated proportionally.

Origin and optional services

Paid tiers start with this workload; estimates do not include other account traffic. Enter your own effective rates after origin allowances. Reads use request misses; egress uses byte fill. Functions assume one invocation per viewer request. Zero leaves an extra out of the estimate; it does not mean your origin is free.

Compare a quote you received

This is your quote, not a published provider price. Use an effective rate for the selected traffic mix; tiers, included usage and commitments need to be reflected in your inputs. Sharing a scenario includes your quote details.

Presets are starting assumptions, not measured traffic. Video assumes one rendition and segment GETs; playlists, retries and extra audio tracks add requests. Fill is a byte ratio, not a request cache-hit rate. GB = 1 billion bytes; Google bills GiB = 1,073,741,824 bytes; CloudFront estimates use binary GB as a billing assumption.

Overview

Fastly provides programmable content delivery with cache control, purging and edge application logic. Full Site Delivery and Compute are distinct service models.

Security, image optimization, TLS and observability products have separate capabilities and pricing. Match the product configuration to the workload before comparing costs.

Network

  • Fastly concentrates network capacity at selected markets and publishes 622 Tbps of connected global capacity. This is a network-wide figure, rather than capacity reserved for one customer.
  • The named city inventory distinguishes current markets from planned additions. A city can contain multiple PoPs; markers show approximate centers rather than individual facilities.
  • Origin shielding changes cache-miss routing and origin traffic. Evaluate the access networks serving your users rather than comparing providers by city count alone.
Listed network cities

Published current network cities, shown at approximate centers. Planned Budapest, Jakarta, Lagos and Nairobi are not plotted. Markers represent cities rather than facility counts or capacity.

AtlantaBostonChicagoDallasDenverDetroitHonoluluHoustonLos AngelesMiamiMinneapolisNew YorkPhoenixSan JoseSeattleSt LouisCalgaryMontrealTorontoVancouverQuerétaroBogotaBrasilliaCuritibaFortalezaSão PauloRio de JaneiroBuenos AiresLimaSantiagoAmsterdamCopenhagenBerlinDusseldorfFrankfurtMunichBrusselsDublinHelsinkiLisbonLondonManchesterMadridMarseilleParisMilanPalermoRomeOsloSofiaStockholmViennaAccraCape TownJohannesburgBangkokChennaiHyderabadKolkataMumbaiNew DelhiPatnaDubaiHong KongKuala LumpurManilaOsakaTokyoRiyadhSeoulSingaporeAdelaideBrisbaneMelbournePerthSydneyAucklandChristchurchWellington
Cities

Atlanta, Boston, Chicago, Dallas, Denver, Detroit, Honolulu, Houston, Los Angeles, Miami, Minneapolis, New York, Phoenix, San Jose, Seattle, St Louis, Calgary, Montreal, Toronto, Vancouver, Querétaro, Bogota, Brasillia, Curitiba, Fortaleza, São Paulo, Rio de Janeiro, Buenos Aires, Lima, Santiago, Amsterdam, Copenhagen, Berlin, Dusseldorf, Frankfurt, Munich, Brussels, Dublin, Helsinki, Lisbon, London, Manchester, Madrid, Marseille, Paris, Milan, Palermo, Rome, Oslo, Sofia, Stockholm, Vienna, Accra, Cape Town, Johannesburg, Bangkok, Chennai, Hyderabad, Kolkata, Mumbai, New Delhi, Patna, Dubai, Hong Kong, Kuala Lumpur, Manila, Osaka, Tokyo, Riyadh, Seoul, Singapore, Adelaide, Brisbane, Melbourne, Perth, Sydney, Auckland, Christchurch, Wellington

Listed without a marker: Ashburn (US), Columbus (US), Jacksonville (US), Kansas City (US), Portland (US), Noida (IN), Fujairah (AE).

Features

FeatureSupported
Web application firewall✓ Supported
Bot protection✓ Supported
DDoS protection✓ Supported
Rate limiting✓ Supported
HTTP/3 (QUIC)✓ Supported
TLS 1.3✓ Supported
Tiered caching✓ Supported
Origin shield✓ Supported
Instant cache purge✓ Supported
Serve stale while refreshing✓ Supported
Serve stale on origin errors✓ Supported
Image optimization✓ Supported
On-demand video✓ Supported
Live video✓ Supported
Digital rights management◐ Partial
HLS / DASH packaging◐ Partial
WebSockets✓ Supported
Signed URLs✓ Supported
Edge compute✓ Supported
Edge functions✓ Supported
Key-value storage◐ Partial
Configuration API✓ Supported
Real-time logs✓ Supported
Log export✓ Supported
Terraform provider✓ Supported

✓ Supported · Partial: limited or separate-product support · ✗ Not supported · Not listed: unconfirmed. Some features need a separate product or plan.

  • Programmable delivery: VCL services customize request handling and support a limited set of ESI directives. Compute uses a separate runtime; KV Store is available there, rather than in VCL services.
  • Cache control: Instant Purge, stale-while-revalidate, stale-if-error and origin shielding. Shielding adds a cache tier and can add billable network traffic.
  • Security: Bot Management, DDoS protection, Edge Rate Limiting and Next-Gen WAF are separate products or contract options. The WAF combines predefined attack protections with configurable rules and thresholds.
  • Images and media: Image Optimizer transforms images. On-the-Fly Packager adds HLS/DASH packaging and DRM-provider integrations; live ingest and encoding remain unconfirmed.
  • Protocols and access: HTTP/3, TLS 1.3, WebSockets and programmable signed-URL access.
  • Visibility: real-time metrics and streamed request logs use different APIs and destinations; log export is not a complete billing record.

Pricing

  • Usage billing: regional bandwidth and requests have separate meters, with 100 GB and 1 million requests free in the Full Site Delivery table.
  • In Europe and North America, the first paid bandwidth tier is $0.12/GB; other destinations differ. The first paid request tier is $0.01 per 10,000 requests. Higher usage uses additional tiers or a quote.
  • Packages: Deliver packages target web pages and APIs, exclude streaming services, and limit traffic from the African, Indian and South Korean billing regions to 10%.
  • Compute, image processing, TLS, security, logging and shielding can add costs. Use an effective workload-specific quote in the calculator; region shares and tier boundaries matter.

Developer tools

  • The official Fastly Terraform provider, APIs, CLI and SDKs support configuration and deployment automation.
  • Stream request logs to supported logging endpoints, including data-stream platforms and storage services.
  • Use the real-time analytics API for aggregated traffic metrics; request logs and metrics are different data.
  • Version service configurations and test cache behavior, origin headers and shielding before activation.

When it fits

  • Teams that want detailed cache control, quick purging and programmable request behavior.
  • Applications using VCL delivery or a separately evaluated Compute deployment.
  • Media workloads that can select delivery, packaging, origin shielding and content protection components individually.

Before you choose

  • Get a workload-specific quote if you need one predictable price covering regions, requests and optional products.
  • Plan who will operate the VCL or Compute configuration.
  • Budget media packaging and DRM separately from cached delivery, and check the upstream ingest and encoding workflow.
Sources