Upgrade × Cloudflare
Talk to Cloudflare →
Executive Brief · Vendor Consolidation

One network for Upgrade's edge, bot defense, API security & Zero Trust.

Today upgrade.com runs two CDNs (Akamai + AWS CloudFront), Akamai Bot Manager, and AWS-hosted origins with no dedicated edge WAF in the path. Cloudflare collapses edge, bot, API, DDoS, DNS and Zero Trust onto a single network — fewer vendors, one control plane, and audit-ready logging for an IPO-track lender.

Why now

Upgrade raised a $165M Series G in Oct 2025 at a reported ~$7.3B valuation and is publicly targeting an IPO in ~12–18 months. The company has delivered $40B+ in credit to 7M+ customers and now spans personal loans, Upgrade Card/OneCard, Rewards Checking, auto and home-improvement lending, plus Flex Pay (the travel BNPL business it acquired as Uplift for $100M in 2023).

That trajectory raises the bar on three things Cloudflare directly addresses: security posture & fraud controls across a fast-growing API and login surface, uptime and performance for many consumer-facing brands, and vendor/cost discipline + unified audit logging that IPO diligence rewards.

Sources: Reuters, CNBC, Bloomberg (Oct 16, 2025); Crowdfund Insider (Aug 2025); Upgrade press releases (2023–2025).

From vendor sprawl to one network

Edge, bot, DNS and email vendors identified on upgrade.com today (AWS stays the application origin). VPN/SSE marked *per account-team. The right is where the edge & security layer can live.
6 edge/security vendors → 1 network
AkamaiCDN · www
Akamai Bot Managerbot defense
AWS CloudFrontCDN · static
AWS Route 53DNS
SendGridemail
VPN / SSEremote access*
Cloudflare one network · one bill · one control plane
Goal: collapse 2 CDNs + bot into one edge

Eight consolidation plays

Each maps to something observed on upgrade.com today — or a security gap a regulated, IPO-track lender should close.
01

One CDN — consolidate Akamai + CloudFront

↳ replaces Akamai (www) + AWS CloudFront (static)

Upgrade pays for two content-delivery networks. Cloudflare serves the whole footprint from one global anycast edge in front of the existing AWS origin — one CDN bill, one cache, one set of logs.

  • Identified: www → upg-www.edgekey.net (Akamai)
  • Identified: static → d2v04be0n9rr5j.cloudfront.net
  • Argo Smart Routing + Tiered Cache to the AWS origin
02

Bot Management

↳ replaces Akamai Bot Manager

For a lender, bots mean application fraud, credential stuffing and synthetic-identity attacks on loan, card and BNPL flows. Cloudflare's ML bot scoring runs inline on the same edge as the WAF — one policy, one log.

  • Identified: Akamai Bot Manager via _abck & bm_sz cookies
  • ML scoring on ~20% of all web traffic for training data
  • No separate bot SKU or second console to run
03

WAF + unmetered DDoS

Net-new edge security in the request path

Recon shows requests hitting an AWS ALB → Istio/Envoy → Next.js origin with no dedicated WAF observed at the edge. Cloudflare adds managed WAF rulesets and always-on L3–L7 DDoS in front of every property.

  • Observed: server: awselb/2.0 then server: istio-envoy
  • OWASP + managed rules tuned for financial services
  • Unmetered DDoS — no surge billing during an attack
04

API Shield

Protect the Next.js + Istio API surface

Upgrade's web and mobile apps are API-driven — lending decisions, accounts, Flex Pay checkout, dealer & partner integrations. API Shield discovers every endpoint and enforces schema, auth and volumetric limits inline.

  • Observed: Next.js + Istio/Envoy service mesh origin
  • Automatic API discovery + schema validation
  • mTLS & JWT validation; block BOLA & abuse
05

Authoritative DNS

↳ migrate from AWS Route 53

Move authoritative DNS onto the fastest network on the internet, with DNSSEC and one-click control of the same WAF/CDN/bot policies — no separate console from where security is managed.

  • Identified: ns-*.awsdns-* (Route 53) on upgrade.com
  • Fastest authoritative DNS resolution globally
  • DNSSEC + analytics; AWS stays the origin
06

Account-takeover & fraud defense

Protect login & onboarding flows

Consumer credit + BNPL = a prime ATO and synthetic-identity target. Cloudflare scores logins for leaked credentials and automated abuse before they hit Upgrade's origin — folded into the same WAF/bot policy.

  • Leaked-credential checks at sign-in
  • Bot + behavioral signals on onboarding & checkout
  • Turnstile (privacy-first CAPTCHA) where friction is needed
07

Cloudflare One — Zero Trust & AI/SaaS governance

↳ replace VPN; govern AI + SaaS access

Upgrade is an engineering- and AI-forward shop across SF, Phoenix, a Montreal tech center, Atlanta & Irvine. Cloudflare One delivers ZTNA (Access), SWG, DNS filtering, CASB and DLP — one agent, one policy, one audit log.

  • Evidence of AI/SaaS adoption: OpenAI, Anthropic, Cursor, Slack, Atlassian, Jamf domain-verification TXT
  • Access (ZTNA) replaces legacy VPN for internal apps
  • Gateway + CASB + DLP to govern AI-tool data egress
08

R2 — egress-free storage

↳ offload AWS S3 / CloudFront origins

As an AWS shop serving static assets and media through CloudFront, object-storage egress is a recurring tax. R2 charges $0 egress — an ideal origin for the consolidated CDN and any AI/retrieval workloads.

  • S3-compatible API; zero egress fees
  • Natural origin for the single Cloudflare CDN
  • Pairs with Workers AI + Vectorize for retrieval

Consolidation roadmap

Sequenced to the IPO runway — land security quick wins first, consolidate the edge, then displace VPN/SSE and unify logging for diligence.
First 90 days

Land — security in the path

  • Deploy WAF + DDoS in front of www / app
  • Bot Management pilot → displace Akamai Bot Manager
  • Onboard authoritative DNS off Route 53
  • API Shield discovery on top lending & Flex Pay APIs
3–9 months

Consolidate the edge

  • Cut www + static over to one Cloudflare CDN
  • Retire Akamai and AWS CloudFront
  • API Shield schema + mTLS on partner/dealer APIs
  • ATO / leaked-credential defense at login
  • Stand up R2 for media + asset origins
9–18 months · IPO-ready

Zero Trust & unify

  • Cloudflare One — Access replaces VPN; Gateway/CASB/DLP
  • Govern AI + SaaS tool access & data egress
  • One control plane + unified logging for audit
  • Single vendor relationship & commercial agreement

Consolidation snapshot

Current-state vendors are evidence-based from public recon; the one account-team item is marked. Nothing here is assumed.
FunctionTodayHow it was identifiedOn Cloudflare
CDN — marketing site Akamai identified www → upg-www.edgekey.net Cloudflare CDN
CDN — static assets AWS CloudFront identified static → *.cloudfront.net Cloudflare CDN (one edge)
Bot management Akamai Bot Manager identified _abck & bm_sz cookies Cloudflare Bot Management
WAF / DDoS None observed at edge awselb/2.0 → istio-envoy origin Cloudflare WAF + DDoS
API protection App-tier only Next.js + Istio/Envoy headers API Shield
Authoritative DNS AWS Route 53 ns-*.awsdns-* nameservers Cloudflare DNS
Origin / compute AWS (ALB · EC2 · EKS/Istio) awselb; Amazon Technologies ASN Stays on AWS — fronted by Cloudflare
Object storage / media AWS (S3 / CloudFront) cloudfront.net asset origin R2 (egress-free)
Transactional email SendGrid mail → *.sendgrid.net Keep — add Email Security (inbound)
Remote access / SSE VPN / SSE *per account-team Not publicly observable Cloudflare One (ZTNA)

How we know — observed on upgrade.com

No assumptions: every current-state vendor below was identified from public DNS, HTTP response headers, set-cookie signatures, and the live upgrade.com Content-Security-Policy.
Akamai www → edgekey.net Akamai Bot Manager _abck / bm_sz AWS CloudFront static → cloudfront.net AWS Route 53 · ALB · EC2 origin Istio / Next.js server headers Contentful app.contentful.com (CSP) SendGrid mail.upgrade.com Stripe stripe-verification TXT AI tools OpenAI / Anthropic / Cursor TXT
LIVE Checking the Cloudflare edge serving this brief…