Proposal in scoping · Akamai App & API Protector

A proposal to Welltory
from Akamai.

Replace Cloudflare without paying for it twice. Protect the API surface that carries your users' biometric data. Open the healthcare chapter with an infrastructure partner underwriting the transition — not invoicing you through it.

Reserve the 17-minute session Five inputs Akamai needs
Prepared for Welltory leadership team
From Akamai Technologies
Status Scoping — awaiting five inputs
01 · The Price Position

How aggressive can Akamai get against the Cloudflare number?

The honest answer, stated plainly by the Akamai deal team, and the reason this proposal starts with data requests instead of a price sheet.

Akamai does not lose on price.

Not a slogan — a commercial posture. Once the scoping inputs below are known, Akamai structures the number to win the account, and gets creative on the terms around it.

01

Price is not the constraint

Aggression is not capped by willingness. It is capped by scope clarity. Bandwidth, hits, FQDNs, zones, and contract timing determine exactly how far the structure can bend.

02

Data unlocks the number

Five inputs convert this from a conversation into a formal Akamai App & API Protector proposal with committed commercial terms.

03

Terms bend further than price

Takeout dollars, delayed billing, contract overlap, and buying out the remaining Cloudflare term are all live options — sized against what is left on your current agreement.

04

Healthcare adds leverage

Welltory landing during Akamai's healthcare-security push is strategically valuable. That value is real, and it becomes negotiable once scope is on the table.

02 · Proposal Inputs

Five numbers turn this into a formal proposal.

These are the exact inputs Akamai requires to issue a proposal for App & API Protector. Fill them in here — the summary can be copied or sent straight to the deal team. Nothing is transmitted until you press send.

Scoping worksheet

Akamai App & API Protector — required inputs

Across all applications that would sit behind Akamai.

Total request volume, including API calls from apps and wearables.

Every hostname Akamai would onboard and terminate TLS for.

Zones currently managed, including any delegated to Cloudflare.

This single answer decides how much of the overlap, delayed billing, or buyout structure Akamai can put on the table.

Optional. Sharpens the takeout structure but is not required to begin.

Entries are held in this browser only until you choose to send or copy them. Nothing is stored on a server by this page.

Why bandwidth and hits

They set the delivery tier and the ceiling of the takeout structure.

Why FQDNs and zones

They size the migration, the certificate work, and the WAAP policy scope.

Why contract timing

It selects which of the four commercial instruments below can be used.

03 · Commercial Options

Takeout dollars, delayed billing, contract overlap — and a buyout.

What is available depends on the remaining Cloudflare term. Within that boundary, Akamai can get creative on every one of these instruments.

Instrument 01 Easy

Delayed billing

Start the Akamai service now, start the invoice later. This is the simplest lever to pull and requires no restructuring of your current agreement.

Straightforward to structure
Instrument 02 Available

Contract overlap

Run Akamai in parallel while Cloudflare winds down, without paying two vendors in full. "We're still under contract" stops being a reason to wait.

Available today
Instrument 03 Available

Takeout dollars

Competitive-takeout economics applied directly against the incumbent baseline, structured so Year 1 does not punish you for switching.

Sized from the scoping inputs
Instrument 04 On the table

Cloudflare contract buyout

If the economics make sense to Akamai, Akamai can buy out the remaining Cloudflare term outright — removing the last financial reason to stay where you are.

Depends on remaining term
The dependency

Every instrument above is scoped against one variable: how much time and money is left on the Cloudflare agreement. That is why question 05 in the worksheet matters more than the other four combined.

04 · Switch Assurance

Protect the momentum. Absorb the switch.

Welltory is in the middle of something rare — a product and a category opening at the same time. This section is about making sure a security decision does not become the thing that slows any of it down.

The commitment

Akamai underwrites the transition. A named migration team designs a phased plan that minimizes Welltory engineering effort, validates performance and security before cutover, and keeps clear rollback options open until every agreed acceptance criterion is met. No engineering pull-off. No platform outage. No variable dropped into a launch window that Welltory earned.

Assurance 01 Akamai-run

Named migration team

A dedicated Akamai migration lead and services team run the transition end-to-end, sized to the scoping inputs. Welltory engineering stays focused on product, not on standing up a new edge.

Included in the switch, not billed on top
Assurance 02 Parallel run

Cutover only after validation

Akamai runs alongside Cloudflare during a phased onboarding — performance, security, and traffic behaviour validated against production before any traffic moves. The cutover is a switch, not a leap.

No dark-launch surprises at scale
Assurance 03 Acceptance-gated

Rollback stays open

Every phase has a defined acceptance gate. Until the gate is signed off, the Cloudflare path stays warm and the rollback stays clean — no forced one-way door, no midnight incident to unwind.

Momentum is protected by design
Assurance 04 Zero-day-one-lift

API surface hardened on day one

App & API Protector, DDoS defense, and API discovery are stood up by the Akamai team ahead of cutover — the biometric API surface goes into production with protection already in place, not scheduled for later.

Security in front of the launch, not behind it
Why this exists

Welltory has a category-defining moment in front of it. This proposal is engineered so the infrastructure decision underneath it does not consume engineering time, jeopardize uptime, or introduce variables into the launch plan Welltory has already built.

05 · What Is Being Proposed

App & API Protector, sized for a health platform.

Welltory's product is its API surface — biometric and wellness data moving between wearables, apps, coaches, and partners. That makes API protection a business-risk decision rather than a feature comparison.

Phase 01

Displace

Akamai delivery and DNS replace the Cloudflare footprint, with the migration run by a named Akamai team and a parallel period before cutover.

CDN + DNS App & API Protector Managed migration Parallel run + rollback
Phase 02

Protect the AI surface

API discovery and protection across the growing AI companion surface — new endpoints and integrations hardened as they ship, not after an incident.

API discovery Shadow API detection Bot & abuse defense Rate & auth controls
Phase 03

Open healthcare

Segmentation, audit-ready controls, and security documentation that clinical partners, employer plans, and enterprise buyers ask for before they sign.

Microsegmentation Audit evidence Restoration readiness Enterprise diligence pack
Independent evaluation · SecureIQLab 2025 Cloud WAAP CyberRisk report
Cloudflare WAF
28.7% of tested OWASP API attack types blocked
Akamai App & API Protector
100% of tested OWASP API attack types blocked
SecureIQLab API security efficacy score Akamai App and API Protector99.18% Cloudflare WAF87.24%
SecureIQLab overall security efficacy score Akamai App and API Protector88.16% Cloudflare WAF62.92%

Attack-type figures as published by Akamai's summary of the evaluation; efficacy scores from the primary SecureIQLab Cloud WAAP v4.0 comparative report (25 July 2025), which tested more than 1,360 attacks across eleven WAAP platforms. Results reflect the tested configurations in that evaluation, not a Welltory-specific test.

The healthcare question

Can the healthcare push unlock better terms?

Yes — and it is one of the strongest levers in this deal. A visible AI-health platform landing during Akamai's healthcare-security push carries strategic value well beyond monthly spend. What that converts into commercially is answered as soon as the scoping inputs are in hand.

Prerequisite

The five scoping answers

Then

Akamai does not lose on price

06 · The Partnership

What a flagship reference buys.

If Welltory is willing to commit upfront to joint proof — a case study, a webinar, an announcement — Akamai builds that directly into the proposal and gets more creative on the financial side. Select what is realistic and carry it into the session.

Selected commitments

None selected yet — tap any card above.

Effect on the proposal

Commercial terms scoped on infrastructure economics alone.

How this is treated

Co-marketing commitments are honoured after a successful migration and with Welltory's explicit approval of every published word. Nothing here obligates Welltory to a story it has not read and signed off on.

07 · The Ask

One 17-minute session.
Welltory team and Akamai team, together.

Not a discovery call and not a pitch. Seventeen minutes to confirm the five scoping inputs, agree the commercial structure worth pursuing, and decide whether a formal Akamai proposal is warranted.

0:00 — 3:00

Scope confirmation

Bandwidth, hits, FQDNs, zones, contract timing — verified in the room.

3:00 — 8:00

Commercial structure

Which of the four instruments fits: takeout, delayed billing, overlap, buyout.

8:00 — 12:00

Protection & migration scope

App & API Protector coverage, division of labour, parallel-run plan.

12:00 — 15:00

Healthcare & partnership

What the healthcare motion and joint proof add to the terms.

15:00 — 17:00

Decision

Proceed to formal proposal, or stop here. One clear answer either way.

In the room · Akamai
  • Matt Pare
  • Amy DiStefano
  • Nick Davie
  • Krupa Panchal
  • Felix Addo
Convened by
  • Ben O'Leary · Nirmata Holdings
  • Steven O'Leary · PhysioPS
In the room · Welltory
  • Leadership sponsor
  • Engineering / infrastructure owner
  • Security or compliance owner
  • Commercial decision-maker
Preparation required
  • The five scoping answers — nothing else
Pick a date & time

Choose a date and time to reserve the 17 minutes.

All times shown in your local timezone. Alternatives welcome.

The scoping answers and any partnership selections above are carried into the meeting request automatically.