Direct answer

For most indie sites, a managed CDN (Cloudflare or Bunny.net) removes more pain than it creates. The cost at low traffic is low, the setup is measured in minutes, and you get DDoS protection and global caching without running your own edge. A self-hosted CDN — usually nginx in front of origin storage — only makes sense once you have predictable traffic volume, a reason to control caching headers tightly, or a specific compliance need.

That is the short version. The rest of this article walks through when each path earns its keep, what the trade-offs really look like, and how to decide before you spend a weekend configuring servers.

Why this question shows up for indie founders

CDNs used to be a phase you hit at scale. That has changed. Modern static-first stacks — Next.js, Astro, Hugo, plain nginx serving pre-rendered HTML — ship files that are obvious CDN candidates. At the same time, free tiers from the big providers make the decision feel almost costless, which is exactly when a founder can waste a week on the wrong choice.

The real question is not “managed or self-hosted?” It is: what pain am I solving, and what pain am I taking on?

What a managed CDN actually gives you

A managed CDN is a third party that runs the edge network for you. Cloudflare and Bunny.net are the two names that come up most in indie circles, and for good reason.

Cloudflare sits in front of your site as DNS, CDN, and a basic web application firewall. Setup is famously quick: point your nameservers at Cloudflare, let it import existing records, and flip the proxy switch. The free tier is generous enough that many indie projects never need to upgrade. Beyond caching, you get DDoS mitigation and a layer of bot filtering without configuring anything.

Bunny.net is a pull-or-push CDN that many indie founders choose for cost transparency. Pricing is per-GB with no surprise bandwidth tiers, and there is a WordPress plugin that wires it up without manual DNS edits. Several indie operators report pairing it with Cloudflare in front — Cloudflare handles the public-facing edge and security, Bunny handles cached static delivery — though that layered setup is optional, not required.

The shared pitch across both: you change a few settings, your static files appear closer to your visitors, and your origin server stops doing as much work.

What “self-hosted CDN” usually means

When founders talk about a self-hosted CDN, they typically mean one of these:

  • A single nginx server (or a small fleet) tuned with proxy_cache, custom cache keys, and tuned TTLs, sitting in front of an origin — sometimes their own VPS, sometimes an object store.
  • Bunny.net as origin + nginx as edge, where nginx handles request routing and Bunny stores the bytes. Several practitioners describe this hybrid as the practical middle ground.
  • A multi-region nginx cluster with GeoDNS, often discussed in passing but rarely the right answer for a small site.

The appeal is control. You set the cache headers, the purge rules, the security headers, and the eviction policy. You are not depending on someone else’s pricing page changing.

The cost is everything else.

Cost at low traffic: honest math

Managed CDN pricing at indie scale is mostly irrelevant to the bottom line. Cloudflare’s free tier covers most static sites indefinitely. Bunny.net charges per gigabyte, and a small marketing site or docs site will often land in the lowest tier. Several comparisons of the two focus on transparency — Bunny’s per-GB model is easier to forecast than Cloudflare’s tiered structure for projects that start to grow.

Self-hosting has costs that are easy to underestimate:

  • A VPS with enough RAM and SSD to act as a cache (typically higher-spec than a plain app server).
  • A second region or a multi-provider setup if global latency matters (which defeats most of the cost advantage).
  • Your time: configuration, monitoring, log review, and the inevitable 2 a.m. cache invalidation bug.

If your site’s bandwidth bill is small, the managed option is almost certainly cheaper once you count hours.

Setup complexity, honestly

Cloudflare setup is the lightest. DNS scan, flip the proxy toggle, optionally tighten page rules. Beginners consistently describe it as approachable.

Bunny.net setup is more hands-on. You enter DNS records manually, configure the pull zone separately, and — unless you use a one-click plugin like the WordPress one — wire it up to your origin by hand. The interface is functional rather than polished, which matters if you are not comfortable editing zone files.

A self-hosted nginx CDN requires you to understand caching semantics: proxy_cache_valid, Cache-Control headers, purge endpoints, vary rules, and how your CMS or app framework interacts with them. It is not a weekend project unless you already live in nginx configs.

Control and caching headers

This is the one place self-hosting genuinely wins. With nginx, you decide:

  • Which paths cache and for how long.
  • How query strings affect the cache key.
  • How Vary is handled for responsive images or locale switching.
  • When purges happen and through what API.

Managed CDNs expose most of these via rules, but the granularity is theirs, not yours. If your product depends on subtle caching behavior — large media libraries, region-locked content, signed URLs, or custom workflows — that control has real value.

For a standard SaaS landing page, blog, or docs site, you will rarely notice the difference.

Security and DDoS

A managed CDN absorbs large attacks across a network built for that purpose. Cloudflare in particular is known for aggressive DDoS mitigation as part of its baseline.

A self-hosted nginx setup gives you whatever you configure: fail2ban, rate limiting, a basic WAF rule or two. Against a small scraping problem, that is fine. Against a real volumetric attack, a single VPS is a soft target. If uptime matters to revenue, this is where the managed option earns its cost many times over.

When an indie site actually needs a CDN at all

You probably need a CDN if any of these are true:

  • Your visitors are spread across more than one continent.
  • You serve images, CSS, JS, or video that account for most of your page weight.
  • Your origin server hits CPU or memory limits under traffic spikes.
  • You launch on Product Hunt, Reddit, or Hacker News and want to survive the front page.
  • You sell anything online and downtime costs you orders.

You probably do not need one if your site is local, low-traffic, and downtime-tolerant. In that case, a well-tuned origin server and a simple backup strategy go further than a CDN.

When managed is the right call

Choose a managed CDN when:

  • You want the result in an afternoon, not a quarter.
  • Your static assets dominate bandwidth.
  • You value DDoS protection out of the box.
  • Your team is small and “operations” is a hat someone wears on Saturdays.

Cloudflare is the default for most projects that want one decision and no bills. Bunny.net is worth a look if you want predictable per-GB pricing, a WordPress-friendly path, or a CDN that lets you store and inspect files directly — Cloudflare operates as a pull CDN that does not store originals in the traditional sense, which can matter for media-heavy workflows.

When self-hosted starts to make sense

Choose a self-hosted setup when:

  • You have specific caching rules that managed tiers cannot express.
  • You operate in a regulated environment where data residency is non-negotiable.
  • You already run nginx at scale and adding cache layers is incremental, not new.
  • Your traffic is high enough that the per-GB bill becomes a meaningful line item, and your team can maintain the infrastructure.

If you are considering self-hosting because the managed option feels expensive, revisit the math. The cheapest managed tier is almost always cheaper than the cheapest correctly configured self-hosted CDN once you add monitoring and on-call time.

A practical decision path

  1. Start with Cloudflare free. Flip the proxy on, review the auto-configured DNS, and look at the caching analytics for a week.
  2. If bandwidth becomes a real cost, evaluate Bunny.net for static delivery, especially if you want per-GB transparency or use WordPress.
  3. If you hit a caching wall that neither service can solve, sketch a self-hosted nginx layer in front of your origin — but only after you have a concrete reason, not a hypothetical one.
  4. If you operate in multiple regions with strict compliance, talk to a CDN with regional storage or a hybrid edge provider before committing to self-hosting.

FAQ

Is Cloudflare really free for indie projects? Yes for most use cases. The free tier covers DNS, the basic CDN, and DDoS mitigation. Some features (advanced WAF, image optimization at scale) sit behind paid plans.

Can I use Bunny.net and Cloudflare together? Yes. A common pattern is Cloudflare in front for DNS and security, with Bunny handling cached static delivery behind it. Set headers so caching works at both layers, and you reduce bandwidth on the inner service.

Is a self-hosted CDN faster than a managed one? Not for a single VPS. Managed providers run dozens to hundreds of points of presence. A single nginx box, no matter how well tuned, cannot match that geographic spread. Self-hosting wins on control, not raw latency.

Do I need a CDN for a small SaaS landing page? Probably not urgently. A CDN helps when traffic is global, when assets dominate weight, or when a launch spike might take you down. For a local audience and modest traffic, optimize the origin first.

Sources