Fastly: role and evidence
An edge control layer with pre-cache and post-cache inspection options. Deployment mode matters to which requests are inspected.
Evidence, not endorsement
A research and planning tool, not a vendor certification. Sources describe specific products, not every service offered by a company. Unknown means not established by the sources reviewed, not unsupported. grug402 sandbox tests do not test these vendors. Operational owners are suggested team contacts, not legal liability assignments.
Editorial review: 2026-10-08. Evidence older than 90 days needs rechecking; source check dates are not release dates.
Product and roles
Operator: Fastly. Product scope: Bot Management.
Edge networks: What may reach the origin? Handoff: Bot policy, headers and cache rules → protected origin. Suggested owner: Network, CDN and security teams.
Prerequisites to confirm
Check Bot Management entitlement; post-cache inspection also requires the specified Next-Gen WAF deployment.
Review cache-miss coverage and service-wide impact before changing policy.
Discovery
Unknown: not established by the reviewed sources. Ask the provider; this is not a failed test.
Delegated authorization
Not applicable: not assessed for this participant's listed role.
Retail checkout
Not applicable: not assessed for this participant's listed role.
Paid API / tool
Unknown: not established by the reviewed sources. Ask the provider; this is not a failed test.
Settlement
Unknown: not established by the reviewed sources. Ask the provider; this is not a failed test.
Deployment
Documented: Bot Management can be enabled through the control panel or API with required entitlements.
Operational controls
Documented: Pre-cache inspection covers cached and uncached resources; post-cache inspection analyzes requests going to the origin.
Relevant sandbox tests — not vendor results
These are controlled grug402 scenarios. A passing sandbox request does not certify a company, integration, checkout or refund process.
- P1: Establish safe edge behavior — Challenges and personalized paid responses need deliberate cache controls. Suggested owner: CDN and application engineering.
- P2: Avoid stale payment instructions — A cached challenge can advertise an expired quote or outdated payment terms. Suggested owner: CDN and payments engineering.
- P1: Prevent paid content leaking from cache — A shared cache can serve one payer's content to another visitor. Suggested owner: CDN and security.
- P2: Allow valid payment credentials through — Security policy may reject a legitimate payment retry. Suggested owner: Network and security.
- P2: Coordinate edge and settlement timeouts — A timeout can leave the buyer unsure whether the service was paid. Suggested owner: Network and payments operations.