Cloudflare Drop

Been using Cloudflare for a while now and the DNS speed bump alone was noticeable right away. Also love that the free tier covers way more than I expected for a small project.

Dropping a folder and having it live in seconds with no account needed is exactly the kind of friction that should be gone for quick projects or demos. My real question is the same one raised in the comments: if the site has a build step (package.json), does it actually run the build, or just serve the files as-is? That's what decides whether this is truly "instant" or only for simple static sites. The 60-minute lifespan also feels short, though I get it's there to prevent abuse.

how does the pricing actually scale for a small site that's starting to get more traffic?

The drag-a-folder-and-it's-live flow is exactly the friction I want gone for tiny side projects. What happens when there's a build step though, does it serve the files as-is or will it run a build if it sees a package.json? Most of my throwaway projects need one npm build before they're actually deployable, and that's usually where "instant" stops being instant.

This looks incredibly frictionless! With no account required and an instant live link, how is the team mitigating the risk of abuse, like rapid-fire phishing campaigns or malicious hosting? Are there automated security scans happening on the .zip files before the 60-minute URL goes live?

Yeah Rohan! I consider myself as one of the Cloudflare's biggest fan and deploying just by dropping a folder is amazing. 60 minutes sound like too short but I'm sure it's more than enough. Thanks for hunting it

How does the pricing actually scale for smaller sites compared to big enterprise customers, and are there any hidden caps on traffic or requests on the free tier that might catch you off guard?

How does pricing actually scale for a mid-size SaaS doing around 50M requests a month, and are there any gotchas when integrating with custom WAF rules alongside your existing CDN setup?