- About the web interface controls
- Always-on DDoS mitigation
- Browser recommendations when using the Fastly web interface
- Content and its delivery
- Fastly POP locations
- Getting started with Fastly
- How caching and CDNs work
- How Fastly's CDN Service works
- HTTP status codes cached by default
- Self-provisioned Fastly services
- Sign up and create your first service
- Working with services
Domains & Origins
Domains & Origins
- Changing origins based on user location
- Connecting to origins
- Enabling global POPs
- Failover configuration
- IPv6 support
- Maintaining separate HTTP and HTTPS requests to origin servers
- Routing assets to different origins
- Setting up redundant origin servers
- Specifying an override host
- Using Fastly with apex domains
- About Dynamic Servers
- Cache control tutorial
- Caching configuration best practices
- Controlling caching
- Creating and using pools with Dynamic Servers
- Creating and using server entries with Dynamic Servers
- Enabling API caching
- Enabling automatic gzipping
- Failure modes with large files
- HTTP/2 server push
- Implementing API cache control
- Making query strings agnostic
- Request collapsing
- Segmented Caching
- Serving stale content
- Setting Surrogate-Key headers based on a URL
- Setting Surrogate-Key headers for Amazon S3 origins
- Streaming Miss
- Accept-Language header VCL features
- Authenticating before returning a request
- Basic authentication
- Creating location-based tagging
- Custom responses that don't hit origin servers
- Delivering different content to different devices
- Enabling URL token validation
- Guide to VCL
- Isolating header values without regular expressions
- Manipulating the cache key
- IP geolocation variables: Migrating to the new dataset
- Overriding which IP address the geolocation features use
- Response Cookie handling
- Support for the Edge-Control header
- Understanding the different PASS action behaviors
- Using edge side includes (ESI)
- VCL regular expression cheat sheet
Access Control Lists
Monitoring and testing
- Domain validation for TLS certificates
- Enabling HSTS through Fastly
- Forcing a TLS redirect
- Managing domains on TLS certificates
- Serving HTTPS traffic using certificates you manage
- Serving HTTPS traffic using Fastly-managed certificates
- Setting up free TLS
- TLS key and certificate replacement
- TLS termination
Web Application Firewall
- Log streaming: Amazon S3
- Log streaming: Microsoft Azure Blob Storage
- Log streaming: Cloud Files
- Log streaming: Datadog
- Log streaming: DigitalOcean Spaces
- Log streaming: Elasticsearch
- Log streaming: FTP
- Log streaming: Google BigQuery
- Log streaming: Google Cloud Storage
- Log streaming: Honeycomb
- Log streaming: Kafka
- Log streaming: Log Shuttle
- Log streaming: LogDNA
- Log streaming: Logentries
- Log streaming: Loggly
- Log streaming: Heroku's Logplex
- Log streaming: OpenStack
- Log streaming: Papertrail
- Log streaming: Scalyr
- Log streaming: SFTP
- Log streaming: Splunk
- Log streaming: Sumo Logic
- Log streaming: Syslog
User access and control
Accounts and pricing plans
Last updated October 03, 2018
Types of accounts and plans
Fastly offers a variety of accounts and pricing plans, which we detail below. To estimate your monthly charges using our pricing estimator, see our pricing page.
Free developer trials
We offer a development trial that allows you to test our services free of charge. Simply sign up for a trial and begin testing. We allow you to test up to $50 of traffic for free to ensure everything fits your requirements.
Once your testing is complete and you're ready to start pushing production traffic our way, you can switch your account to a paid account by adding your credit card information. Some add-on options (our TLS certificate options, for example) require you to switch your account to a paid account before that functionality becomes available to you.
Paid accounts without contracts
After your trial period ends, you can use Fastly's services on a month-to-month basis without having to sign a contract. Be sure you've provided us with your current billing address as well as your credit card information.
To switch from a developer trial to a paid account without a contract, follow the steps below:
- Log in to the Fastly web interface.
From the user menu, select Billing.
Your account's billing information appears.
Click the Upgrade account link. Information about your plan's current account type appears.
- Click the Paid account plan option.
- Agree to Fastly's Terms of Service by selecting the I agree to the terms of service checkbox.
- Click the Upgrade Account button. The development trial option disappears.
Once you switch to a paid account, the developer account plan option disappears and we'll begin billing you automatically at the end of every month using your credit card information. You can cancel your paid account at any time.
Paid accounts with contractual commitments
If you plan to push at least 2TB of data per month and require one of our TLS service options, or if you plan to push a minimum of 4TB of data per month, it might be worthwhile to consider a contract with Fastly. Contact us at email@example.com for more information. We also offer solutions targeted to the needs of specific industries.
Free open source developer accounts
Canceling your account
To cancel your account, have your account owner follow the steps below:
- Deactivate and then delete all services on your account.
- If you're using a TLS certificate, do the following:
- From the user menu, click Account. Your account information appears.
In the Company settings area, click the Cancel Account button.
A confirmation window appears.
- In the Your password field of the confirmation window, type the password associated with your account and click Confirm and Cancel.
After your account is canceled, you'll be billed for any outstanding charges accrued through the day you canceled. For questions about your final billing statement, contact our billing team for assistance. If you decide at a later date to reactivate your account, contact Customer Support and request reactivation.Back to Top