KIKO Milano がブラックフライデーにスケーリングする方法

KIKO Milano on Vercel:

Eliminated 3 weeks of Black Friday infrastructure prep

75% decrease in app build times

Went from minimal releases to deploying multiple times per day

KIKO Milano’s ecommerce team used to treat peak traffic as an operations project. Weeks before Black Friday, they had to manually scale AWS infrastructure and adjust application configuration, knowing that if demand exceeded forecasts, their site could slow down or even break, costing them real revenue.

After migrating to Vercel, they removed manual prep from their playbook. Instead of provisioning infrastructure, their team now ships campaigns and tests daily.

The Black Friday problem: manual scaling and stressful failure modes

Before Vercel, KIKO ran their ecommerce app on AWS EC2 instances sized for normal traffic, then scaled by hand ahead of peak periods.

This was their previous process leading into Black Friday:

Manual scaling window:

Black Friday prep began 2–3 weeks ahead of the event, then had to be unwound after the traffic spike passed.

Infrastructure configuration:

The infra team manually adjusted AWS EC2 capacity to support expected traffic.

Application configuration:

Scaling also required application-side changes, making peak readiness more than just an infrastructure task.

War room prep:

Chat channels and conference rooms were set up for teams to triage performance and downtime problems.

Beyond the manual prep work, KIKO’s dev team had to anticipate failure modes that hurt the business. Slow navigation and site instability made it hard for users to purchase, and, in Ant’s words, they knew that at any point, “everything could break.”

Worry-free delivery and automatic scaling

Vercel changed the work from preparation to execution. With environments available on demand, faster builds, and automatic scaling during traffic spikes, Ant’s team stopped planning around infrastructure limits and focused on the ecommerce experience itself.

Environments without the bottleneck

KIKO's old setup ran on a fixed number of shared environments, which constrained how the team handled dev, test, pre-prod, and prod work in parallel. On Vercel, Ant described provisioning new environments as "snapping your fingers," including spinning them up on the fly when a project calls for it. Cloning environment variables is quick, and many changes that used to require code edits now "just require redeployment."

Shipping faster without the operational tax

The dev team’s old pipeline took around 20 minutes to run, which meant they had to keep releases to a minimum. Builds on Vercel finish in under four minutes on average, even with many locales and a large catalog of pre-rendered pages. The deployments view in the Vercel dashboard gives the team one place to check build status and surface failures without digging through logs.

No more performance variability during traffic spikes

Performance used to swing with traffic, which meant the team felt every spike. Ant said that on Vercel, "everything scales automatically."

That’s possible because their Next.js app runs on infrastructure that separates static delivery, cached pages, and dynamic compute, so each part can scale independently during traffic spikes, instead of forcing the team to size and tune servers ahead of time.

Beyond Black Friday: velocity, SEO, and innovation

The infrastructure migration didn’t just change how KIKO prepares for traffic spikes, it changed how much operational work the team carries every week.

Ant estimates that Vercel saves his team almost an entire day per week when all of the friction is added up, and that time savings has made the team more confident: the platform works, they can ship quickly, and when they need support, they know Vercel is there with them.

About KIKO Milano: KIKO Milano is a global beauty brand delivering cosmetics and ecommerce experiences to customers worldwide.

Read more