Skip to content



The Bulletproof brand agency website after its infrastructure and performance overhaul




Bulletproof

Bulletproof approached us with significant technical challenges in their AWS-hosted website infrastructure.



Project Overview

Their development workflow was being hampered by excessive build times of 30 minutes per deployment, severely limiting their ability to iterate quickly or deploy urgent fixes. Additionally, their internationalization implementation had become increasingly difficult to maintain at scale.

We identified that a migration from AWS to Vercel would address the core infrastructure issues while providing substantial performance improvements. Our technical implementation focused on a comprehensive deployment architecture overhaul, migrating the entire application from AWS to Vercel's edge network to use their optimized build pipeline and deployment infrastructure. Through careful analysis and refactoring, we achieved a dramatic build process optimization that reduced build times from 30 minutes to just 4 minutes, an 87% reduction. This improvement was accomplished by implementing incremental static regeneration and optimizing the build toolchain, alongside a complete restructuring of their localization system using Next.js's native i18n capabilities to create a more maintainable and efficient approach to managing multilingual content.

The technical benefits extended beyond just build times. The team now has access to Vercel's comprehensive analytics, preview deployments, and a significantly simplified hosting model that eliminates infrastructure management overhead. This allows their development team to focus on feature development and content creation rather than deployment logistics. This migration demonstrates how strategic infrastructure decisions can transform development workflows and create measurable performance improvements without requiring a complete application rewrite.



Common questions

Bulletproof project FAQs

What buyers ask us about the Bulletproof project, answered from the work itself

What was the actual problem?
Thirty-minute build times on every deployment, which meant the team could not iterate quickly or ship an urgent fix without a long wait. Their internationalization setup had also become hard to maintain as it grew.
How much faster did deployments get?
Builds went from 30 minutes to 4, an 87% reduction, through incremental static regeneration and a reworked build toolchain.
Why move from AWS to Vercel?
The core problems were infrastructure problems, and Vercel's edge network and build pipeline addressed them directly. It also removed the infrastructure management overhead entirely, so the team could spend its time on features rather than deployment logistics.
Did this require rewriting the application?
No. The migration was an infrastructure and deployment change plus a restructure of the localisation layer onto Next.js native i18n. The Next.js development work was targeted at the parts causing pain, not a ground-up rebuild.
What else came with the move?
Vercel analytics, preview deployments on every change, and a much simpler hosting model with no servers to manage.


Services



Get in touch

Tell us what you're building. We reply within one working day. Jono or someone on the team picks up every message personally.

By sending this you agree to our privacy policy. We only use your details to reply.