Skip to content
LEGACY CDN MIGRATION GUIDE

Moving on from a legacy StackPath CDN setup

StackPath is not a current CDN option in this comparison. Start by identifying who serves your traffic today, then assess whether Cloudflare Enterprise with Vigilbase meets your delivery and security needs.

On 24 August 2023, Akamai announced it had acquired select enterprise customer contracts after StackPath decided to cease CDN operations. This guide concerns that legacy CDN service; it makes no claim about the status of every other StackPath product.

Vendor sources checked

OUR VERDICT

The short answer

Start with the decision. The detailed evidence follows below.

Review an inherited StackPath configuration

Your current CDN

Confirm the service that actually handles your traffic and your contractual position. The 2023 announcement does not tell you the current state of an individual account.

Assess Cloudflare for the next deployment

Cloudflare Enterprise

Vigilbase can scope Enterprise licensing, migration, and ongoing operation once your application and support requirements are clear.

Side-by-side evidence

Detailed comparison

What this page compares

Cloudflare Enterprise
A scoped Cloudflare Enterprise deployment and operating service
StackPath CDN (legacy)
A legacy CDN configuration, not a current product offer

First decision

Cloudflare Enterprise
Confirm required controls, traffic, and operating coverage
StackPath CDN (legacy)
Identify the current provider, contract, DNS, and configuration owner

Cache behavior

Cloudflare Enterprise
Validate cache rules, headers, purging, and application paths
StackPath CDN (legacy)
Export or document existing behavior where still available

Cutover

Cloudflare Enterprise
Test TLS, origin access, security policies, and rollback
StackPath CDN (legacy)
Check residual DNS records and dependencies before retiring configuration

In-depth overview

Cloudflare Enterprise with Vigilbase

Cloudflare Enterprise with Vigilbase

Cloudflare provides delivery and security controls; Vigilbase plans the supported configuration and operates it within agreed authority.

KEY STRENGTHS

✓DNS, TLS, cache, and WAF review in one migration plan
✓Supported changes followed by verification
✓Operating coverage selected for the application

LIMITATIONS

✗Feature names do not establish configuration equivalence
✗Performance must be tested against your users and application paths

IDEAL FOR

Teams evaluating a supported migration and ongoing operator

PRICING

Cloudflare Enterprise licensing and Managed Cloudflare operations, scoped together.

Legacy StackPath CDN setup

Use the historical StackPath configuration as migration input. Akamai announced the acquisition of select enterprise CDN customer contracts in August 2023 after StackPath decided to cease CDN operations.

KEY STRENGTHS

·Existing configuration can explain intended cache and routing behavior

LIMITATIONS

✗Old feature tables and prices are not a current purchase basis
✗Your current service and contractual arrangements need separate verification

IDEAL FOR

Understanding inherited settings before deciding what to retain or replace

PRICING

Check the actual current provider and contract

Pricing breakdown

Cloudflare Enterprise

Cloudflare Enterprise with managed operations

Agreed contract

✓Cloudflare Enterprise licensing is sized to your requirements
✓Cloudflare Enterprise uses an agreed contract scope and bandwidth
✓Choose based on traffic, controls, support, and operational requirements
✓Vigilbase can size, deploy, and manage your Cloudflare environment

StackPath CDN (legacy)

Legacy contract review

·No current StackPath CDN price is quoted here
·Verify termination, transfer, and billing arrangements with your current provider

Which one is right for you?

Find yourself in these scenarios to see which solution fits best.

If you're a Application owner at a Organizations with inherited CDN configurations trying to Plan a controlled move to Cloudflare

→ Cloudflare Enterprise

Inventory DNS, TLS, origins, cache behavior, and security rules; test representative journeys and agree rollback before cutover.

A controlled CDN migration

Switching from StackPath CDN (legacy)? Here's how we make it painless.
1

Identify the current provider, account owner, and contract

2

Inventory DNS, certificates, origins, cache rules, and application dependencies

3

Map delivery and security behavior to the proposed Cloudflare configuration

4

Test representative journeys and agree rollback with the application owner

5

Cut over within an agreed change window and verify the result

Frequently asked questions

When should we keep the current CDN?

Keep a current service that meets your requirements unless there is a demonstrated delivery, security, or operating need to change.Document any gap first, then compare a proposed migration against the current service using the same traffic, controls, and operating responsibilities. Include testing, cutover, and rollback work in the decision.Choose who operates CloudflareWhat to check before buying Cloudflare

Is StackPath CDN still a current alternative to Cloudflare?

Akamai announced on 24 August 2023 that it had acquired select enterprise customer contracts following StackPath’s decision to cease CDN operations. This page therefore treats StackPath CDN as a legacy migration context, not a current buying option.What to check before buying CloudflareCloudflare Enterprise with Vigilbase

Does that announcement establish the status of my account?

No. Check your current provider, billing arrangements, DNS, and configuration ownership. The announcement concerns select enterprise contracts and does not establish the circumstances of every customer or the status of every other StackPath product.Choose who operates CloudflareHow we run Cloudflare after go-live

Is Cloudflare guaranteed to be faster or cheaper?

No. Test representative application paths and user regions, and compare equivalent contract scope and operating responsibilities. This guide does not claim a universal latency improvement or a fixed saving.Cloudflare Enterprise licensing explainedWhat to check before buying Cloudflare

What can Vigilbase take on?

Vigilbase scopes Cloudflare Enterprise licensing, guided migration, and managed operations. Supported changes require agreed authority and are followed by verification, with analysts handling exceptions.Agree the applications, controls, coverage hours, escalation path, and verification process before handover. Keep responsibility for any services outside that scope explicit.Compare Core, Priority and CriticalHow we run Cloudflare after go-live

Review your CDN migration with Vigilbase

Review your current controls, permitted changes, migration dependencies, and support requirements with Vigilbase.

Email for a recommendation