235 GB in a single day. 890 GB and 6.1 million requests across two weeks. 94% served straight from cache. Total cost: about $25.

That was the traffic Armory's new website carried during the biggest week in the company's history — and it barely cost us a coffee run.

The biggest week in the company's history

On 5 May, Armory announced a ₹100 Cr ($12 Mn) deal with India's Ministry of Defence. We knew the announcement was coming, and we knew exactly what it meant: a flood of attention — and traffic — to a site built in Webflow.

The site itself is a scroll-based experience built on a high-quality image sequence. The kind of build that looks incredible and eats bandwidth for breakfast. Beautiful, heavy, and exactly the sort of thing that turns a traffic spike into a billing problem.

Why the default setup would have broken

On Webflow alone, that spike would have forced Armory onto a 1TB bandwidth plan at $399 a month. An image sequence is dozens of full-resolution frames, all loading as the visitor scrolls. Multiply that by 6.1 million requests and you blow past standard hosting limits fast.

This is the trap most teams fall into: they build the beautiful thing, ship it, and only discover the bandwidth bill when the traffic — the good kind, the kind you actually wanted — finally arrives.

The approach: Webflow runs the site, Bunny carries the weight

So we planned for it before launch. Every heavy asset — the entire image sequence — went onto bunny.net CDN instead of Webflow, and we served it into the scroll animation from there.

The split was clean:

• Webflow ran the site — pages, structure, CMS, the parts it does best.
• bunny.net carried the weight — the heavy media, delivered from a global CDN built for exactly this.

That separation is the whole trick. Webflow does what Webflow does best, and the bandwidth-hungry assets live somewhere built to serve them cheaply, at scale, anywhere in the world.

The numbers

• 235 GB delivered in a single day, at peak.
• 890 GB and 6.1 million requests across the two-week window.
• 94% served straight from cache — so the origin was barely touched.
• About $25 in total cost.

What this approach saved on Webflow

The math is simple. To carry this traffic on Webflow alone, Armory would have been pushed onto the 1TB bandwidth plan at $399 a month. Serving the same heavy assets through bunny.net cost about $25 for the entire launch window — roughly a 94% reduction in cost for the spike itself.

And the gap doesn't close after launch. That Webflow bandwidth tier is a recurring $399 a month — close to $4,800 a year — whether or not you use all of it. bunny.net's pay-as-you-go model means you only pay for the traffic you actually serve, so the bill tracks reality instead of a plan ceiling. For a media-heavy site, that's the difference between a fixed premium subscription and a few dollars on the weeks that matter.

Same traffic. The same experience for every visitor. A fraction of the cost — because the heavy lifting happened somewhere built to do it cheaply.

The takeaway

Anyone can build a website. The harder, more valuable work is planning for what happens after it goes live — the launch, the spike, the moment the thing you built actually gets used.

Armory's launch didn't just survive its biggest week. It handled it comfortably, predictably, and for the price of lunch.

Visit the site: www.armory.in

Everything Flow — Webflow Professional Partner.