Cloudflare charges to deliver and protect a site's traffic, and apart for the platform where the customer runs its own program. They are not the same book. Akamai and others sell parts of the same trade. It is not a share of internet traffic by decree and the network is not a count of cities. This report does not describe the attack or how it is stopped, and it does not describe how that traffic moves.
The customer can choose not to renew. A year of heavy traffic is not normal earnings. Building more network is spending, not a bill. The customer's program does not move with delivery of the site.
Cash is the bill collected, minus that build. If something is paid out, it has to fit. It is not a network the customer cannot leave.
Sustainable Competitive Advantage
"The advantage is the customer already sending that site through the network. They can leave. The moat narrows if they do not renew, or if traffic falls and the other book does not make it up."
Loading the Vaultflake…
Radar axes
—
Health
—
Moat
—
Growth
—
Value
—
Return
—
Health is the network's debt, not of a share already measured. Quality separates the margin of delivering the site from the customer's platform. Growth follows bills, not a year of heavy traffic. P/E is read against that year, not against that peak. Shareholder return, if any, is checked against cash. Do not read it as the network that cannot be replaced.
The P/E of a year of heavy traffic is not the earnings if the customer leaves. EV/EBITDA is read without treating the network build as a bill. Do not use a single-book multiple as if site delivery and the platform were the same. A dash if the NET cache is cold.
Limits of this report
Not advice on Cloudflare. Vaultflake does not state a traffic share and does not describe the attack. Read the filings. A past payout is not a right. The table is a snapshot, not a target price.
Questions from this report
What moat does Cloudflare have?
The advantage is the customer already sending that site through the network. They can leave. The moat narrows if they do not renew, or if traffic falls and the other book does not make it up.
How do you read the Cloudflare radar?
Health is the network's debt, not of a share already measured. Quality separates the margin of delivering the site from the customer's platform. Growth follows bills, not a year of heavy traffic. P/E is read against that year, not against that peak. Shareholder return, if any, is checked against cash. Do not read it as the network that cannot be replaced.
Which multiples matter for Cloudflare?
The P/E of a year of heavy traffic is not the earnings if the customer leaves. EV/EBITDA is read without treating the network build as a bill. Do not use a single-book multiple as if site delivery and the platform were the same. A dash if the NET cache is cold.
What does this Cloudflare analysis leave out?
Not advice on Cloudflare. Vaultflake does not state a traffic share and does not describe the attack. Read the filings. A past payout is not a right. The table is a snapshot, not a target price.
Related reports in Technology · Web Delivery and Developer Platform
