Fastly Compute

HostedEdge runtime

Instant. Programmable. Global. Choose three.

Homepage Docs Pricing Repository

Scanned 14 Oct 2026 · Schema v5 · features v21

From: $500/mo
Usage-based Compute requests plus vCPU milliseconds; free monthly allowances, volume discounts, optional packages and enterprise quotes. CDN bandwidth and attached storage are separate charges.
Free tier: Not documented
10 million Compute requests and 100 million Compute vCPU milliseconds per month.
Isolation: WebAssembly
shares the host process
Regions: 6
North America · Europe · Asia Pacific · South America · Africa · Middle East
Capabilities: 16 / 61
2 partial · 33 fail · 0 not assessed
Agent readiness: 10/11 · 9/11
read · drive, pre-login surface

Advertised for

HTTP edge applications and APIs · Request routing and reverse proxying · Authentication logic and security enforcement · Personalization and A/B testing · Real time request/response processing

Built for

Developers, then technical

· Compute documentation leads with CLI, SDK language guides, WebAssembly and Terraform: https://www.fastly.com/products/edge-compute
· Compute usage billing uses requests and vCPU milliseconds: https://www.fastly.com/pricing

01 Pricing Usage-based Compute requests plus vCPU milliseconds; free monthly allowances, volume discounts, optional packages and enterprise quotes. CDN bandwidth and attached storage are separate charges.

Tier	EntryCompute usage-based	Compute Starter package	TopCompute Advantage / Ultimate
Price	$0 base; metered beyond free allowance	$500/month	Contact sales
Includes	10M requests and 100M vCPU ms monthly; attached storage/network services separately priced.	500M requests, 5B vCPU milliseconds, 20 services, 5 config stores with 500 entries each.	Advantage: 2B requests, 20B vCPU ms, 30 services. Ultimate: 5B requests, 50B vCPU ms, 50 services.
vCPU hours	27.77777777777778 h	1388.888888888889 h	—
Request count	10000000	500000000	—
vCPU hours overage	$0.18/h	—	—
Request overage	$0.0000005 per request	—	—

Free tier: 10 million Compute requests and 100 million Compute vCPU milliseconds per month.

Compute request and vCPU millisecond (tables per million units).·Card required: unconfirmed·fastly.com

Overages: Requests per million: 10M–500M $0.50; 500M–5B $0.49; 5B–20B $0.48; 20B–50B $0.45; 50B–125B $0.40; 125B–500B $0.30; above 500B $0.20. vCPU ms per million: 100M–5B $0.05; 5B–50B $0.049; 50B–200B $0.048; 200B–500B $0.045; 500B–1T $0.04; 1T–5T $0.03; above 5T $0.02.

02 Website design Desktop public website · assessed 14 Oct 2026

Complete assessment.

Fastly’s public marketing pages combine oversized sans-serif headlines, black/cream contrast, blue actions and fine red wave graphics. Pricing uses an orderly three-card grid; developer docs switch to a compact black navigation, a map-led hero and practical code examples.

Corporate
Technical illustration

Landing page: captured
Pricing: captured
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

WebAssemblyshares the host process

Persistence

No durable per-instance disk. Sandbox globals may survive sequential requests under sandbox reuse; they are not durable storage. KV/config/secret stores supply external state.

Snapshots / forks

No user-managed snapshot/fork lifecycle documented for Compute sandboxes.

Resources & limits

Storage

KV Store, Config Store and Secret Store are attached edge data stores; not a persistent instance filesystem or relational database.

Limits & quotas

Default limits: 50ms CPU/execution; 2-minute runtime (60s trial); 128MB heap and 1M-byte stack; 32 backend requests (10 trial); 32 dictionary lookups; 200 dynamic backends/service. Published resource limits can vary by account.

GPU

Not applicable to this Wasm edge runtime; no user GPU instance.

Access

Deploy interface

Official Fastly CLI, GitHub Actions and Terraform integrations; compiled WebAssembly service packages.

SDK languages

JavaScriptTypeScriptRustGoC++Python

Network & secrets

Egress controls

Configured backend origins and dynamic backends are supported. No general outbound firewall/allowlist guarantee established.

Secrets

Secret Store supplies sensitive values to Compute applications; separate attached edge data store.

Bring your own cloud

Runs on Fastly’s global network; no customer-cloud Compute deployment documented.

Placement & use

Jurisdiction

Global edge execution; no customer-selectable jurisdiction restriction established by these public Compute sources.

Advertised workloads

HTTP edge applications and APIsRequest routing and reverse proxyingAuthentication logic and security enforcementPersonalization and A/B testingReal time request/response processing

04 Capabilities 16 pass · 2 partial · 33 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 2/5

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Not applicable

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Not supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Not supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Supported

GPU computeGPU-backed instances available.

Not applicable

Multi-regionCompute placeable in more than one geographic region.

Supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Not applicable

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not applicable

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not applicable

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not applicable

Networking & delivery 4/8

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Supported

Custom domainsBring-your-own domain via CNAME/DNS.

Supported

Public preview URLsShareable per-deploy / per-branch URLs.

Not supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not applicable

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Partially supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Not supported

Email send / receiveSend and/or receive email from the workload.

Not supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Supported

Developer access 3/7

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Not supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Not applicable

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not applicable

Git deployDeploy from a Git repo / push-to-deploy.

Partially supported

Private container registryHosted private image registry.

Not applicable

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Not supported

AI & agents 2/12

Built-in coding agentShips a first-party AI coding agent in the product.

Not supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Not supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Not supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Not supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Not supported

BYOK for LLMsBring-your-own LLM provider keys.

Not supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Not supported

Data 0/4

First-party databasePlatform-provided managed database.

Not supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Not supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not supported

Platform & operations 2/6

Scheduled tasksCron / scheduled job primitive.

Not supported

Durable workflowsDurable execution / long-running workflow primitive.

Not supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Not supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Supported

Organisation & security 3/9

Built-in authPlatform-provided authentication / IAM for workloads.

Not supported

SSO / SAMLEnterprise single sign-on.

Supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Not supported

BYOCRuns inside the customer's own cloud account.

Not supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Not supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Not supported

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

10/11

8 full · 2 partial · 91% of applicable checks

llms.txt
Supported
“Substantive apex and documentation llms.txt indexes link docs, products, pricing and development resources. Source: https://www.fastly.com/llms.txt; confidence: high.”
llms-full.txt
Not supported
“Apex and documentation llms-full.txt return 404; concise indexes exist but no full corpus file established. Source: https://www.fastly.com/llms-full.txt; confidence: medium.”
robots.txt AI policy
Partially supported
“Wildcard exclusions, no explicit AI user-agent allow/block rules; default allow. Source: https://www.fastly.com/robots.txt; confidence: medium.”
JSON-LD
Partially supported
“Organization and Corporation JSON-LD found, no Product/SoftwareApplication offers established. Source: https://www.fastly.com/; confidence: medium.”
Sitemap
Supported
“Nontrivial sitemap index links sitemap files. Source: https://www.fastly.com/sitemap/sitemap-index.xml; confidence: high.”
Meta tags
Supported
“Descriptive title, description and Open Graph metadata in HTML. Source: https://www.fastly.com/; confidence: high.”
Markdown negotiation
Supported
“API index.md fetched as substantive markdown; documented Accept: text/markdown and .md support. Source: https://www.fastly.com/documentation/reference/api/index.md; confidence: high.”
Content efficiency
Supported
“HTML visible-text extraction 12082 bytes / 224032 HTML bytes = 5.393%; scripts/styles excluded. Source: https://www.fastly.com/; confidence: high.”
Docs discoverable
Supported
“Documentation and developer hub links are present in public navigation. Source: https://www.fastly.com/; confidence: high.”
Machine-readable pricing
Supported
“Compute request/vCPU monthly brackets and packages are structured readable tables. Source: https://www.fastly.com/pricing; confidence: high.”
No anti-bot wall
Supported
“Fresh public product, pricing, API, docs and well-known fetches return content or genuine 404, not bot challenges. Source: https://www.fastly.com/products/edge-compute; confidence: high.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

9/11

8 full · 1 partial · 82% of applicable checks

Public API
Supported
“Documented REST API and scoped token authentication. Source: https://www.fastly.com/documentation/reference/api/; confidence: high.”
OpenAPI spec
Not supported
“No fetchable OpenAPI established; Postman collection is not OpenAPI, validation starter not management spec. Source: https://www.fastly.com/documentation/reference/api/; confidence: medium.”
MCP server
Supported
“Documented official MCP server with installation and Compute management examples. Source: https://raw.githubusercontent.com/fastly/mcp/main/README.md; confidence: high.”
SDK packages
Supported
“Official developer guides cover multiple SDK languages. Source: https://www.fastly.com/documentation/guides/compute/; confidence: high.”
Auth documented
Supported
“Scoped API tokens, Fastly-Key header and creation via API/web interface documented. Source: https://www.fastly.com/documentation/reference/api/; confidence: high.”
Self-serve credentials
Supported
“Programmatic API-token creation is documented; account bootstrap still requires signup and this is not a tested autonomous signup. Source: https://www.fastly.com/documentation/reference/api/auth-tokens/; confidence: high.”
Webhooks
Not supported
“No signed general Compute webhook integration established; logging drains are not webhooks. Source: https://www.fastly.com/documentation/reference/api/; confidence: medium.”
CLI tool
Supported
“Official Fastly CLI latest release retrieved. Source: https://api.github.com/repos/fastly/cli/releases/latest; confidence: high.”
Error model
Partially supported
“Observed API JSON error {msg: Provided credentials are missing or invalid}; comprehensive documented error schema not established. Source: https://api.fastly.com/openapi.json; confidence: medium.”
Rate limits documented
Supported
“Writes 1000/hour; reads 6000/minute; 429 and Fastly-RateLimit-Remaining/Reset headers documented. Source: https://www.fastly.com/documentation/reference/api/; confidence: high.”
Agent config files
Supported
“Multiple discoverable surfaces: official agent setup, MCP configuration and portable toolkit skills/plugin manifest. Source: https://www.fastly.com/documentation/reference/agent-setup/; confidence: high.”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 8

Claude Code Anthropic
Supported
“Setting up your agent manually: Claude Code”
Source fastly.com
Codex CLI OpenAI
Supported
“Setting up your agent manually: Codex”
Source fastly.com
Cursor Anysphere
Supported
“Setting up your agent manually: Cursor”
Source fastly.com
GitHub Copilot GitHub
Supported
“Setting up your agent manually: GitHub Copilot”
Source fastly.com
Gemini CLI Google
Supported
“Setting up your agent manually: Gemini CLI”
Source fastly.com
OpenCode opencode
Supported
“Setting up your agent manually: OpenCode”
Source fastly.com
Cline Cline
Supported
“Setting up your agent manually: Cline”
Source fastly.com
Qwen Code Alibaba (Qwen)
Supported
“Agent-specific installation: Qwen Code”
Source github.com

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 5

ISO/IEC 27001
certifiedhosted
“Fastly is certified to the ISO/IEC 27001:2022 standard for its Information Security Management System (ISMS). You can view our report here (Schellman certificate directory, certificateNumber=1850190-4).”
Source fastly.com
PCI DSS
certifiedhosted
“Fastly is Payment Card Industry Data Security Standard (PCI DSS) compliant as a Level 1 Service Provider. For customers using Fastly's Network services, Compute, or Observability products, our PCI-compliant caching product allows customers to configure their services in accordance with our PCI DSS Attestation of Compliance.”
Source fastly.com
SOC 2 Type II
certifiedhosted
“SOC 2 Type 2: Fastly is audited against the Trust Service Criteria for Security and Availability as established by the AICPA.”
Source fastly.com
HIPAA
self-attestedhostedDescribed as 'audited against relevant sections' rather than a certified BAA arrangement; classified self-attested. Compliance reports available to customers under NDA.
“Fastly is audited against relevant sections of the Security and Privacy Rules of the Healthcare Insurance Portability and Accessibility Act (HIPAA). Customers can configure their services using our HIPAA-compliant caching product to support their compliance with these requirements.”
Source fastly.com
GDPR
self-attestedhosted
“GDPR: Fastly is audited against key articles of the General Data Protection Regulation, mapped to data protection and privacy controls for Fastly as a data processor.”
Source fastly.com

Regions 6

North America
Europe
Asia Pacific
South America
Africa
Middle East

Global network coverage from refreshed network map; no live capacity number or authenticated per-city inventory asserted.

Legal

Privacy notice Terms of service

08 Company & presence Facts only, not scored

Company

Headquarters: San Francisco, CA, USA
Founded: March 2011
Team size: Not disclosed
Hiring: Public careers and open-position links available; individual requisitions not enumerated.

Activity

Last release: Fastly CLI v16.1.0 (2026-09-14T14:40:52Z) api.github.com
Last blog post: October 13, 2026: Defense Without Detours: Introducing Fastly Network Protect (latest date observed on index). fastly.com

Presence 5

Links found on the public surface scanned; not an exhaustive search.

09 Sources & method How this entry was produced

Public surface only

Everything here was read from fastly.com's unauthenticated pages, docs, pricing and repository on 14 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All Edge runtime products →