We looked at S3 first — it's the obvious default and the DX is solid. But egress fees are a hidden tax that quietly compounds as your user base grows. Every file your users download costs you extra, and it adds up fast.
R2 gives you the exact same S3-compatible API, so there's no learning curve and no SDK migration. We literally just updated our config. Zero egress costs since day one, backed by Cloudflare's global network we were already using. It wasn't even a close call.
Cloudflare has so many products bundled in now, where do you even start as someone just trying to speed up a small WordPress site and add basic DDoS protection without getting buried in enterprise features?
@kymetwpmb I'd probably use AI to guide me step by step. As it can indeed be confusing and overwhelming.
@kymetwpmb First thing I'd do is move off of WordPress.
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?
@emilholsvik I'm not technichal so please excuse the simple question, but what can you not do on Cloudflare that you can do on Vercel, and why won't you fully move?
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?
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.
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 free tier hold up under a sudden traffic spike, and at what point does it nudge you toward a paid plan?
How does the pricing actually scale for a small site that suddenly gets a traffic spike, or do you cap usage before that kicks in?