view
Skip to Main Content
whiterabbit-logo

Technology & Media

Spotify's web infrastructure was headless, built on Contentful and Next.js, serving millions of users. But the content team couldn't move fast. Pushing product listings from staging to live was manual, and a single misstep could take a page down. This process created risk and slowed releases, so we rebuilt it.

  • Spotify web experience collage
  • Spotify product UI on desktop and mobile
  • Spotify connect-with-device campaign creative

Challenges

  • 01

    Manual Syncs With No Safety Net

    With 30 to 50 product listings going live at a time, each sync meant carefully comparing environments and moving changes by hand. The margin for error was narrow.

  • 02

    No Tooling to Compare Environments

    There was no tool to compare staging against production. When something looked off after a release, the team had to check layouts and content manually to find the difference.

  • 03

    A Release Process That Couldn't Scale

    Because every sync was manual, every release carried risk. The process couldn't be handed off or scaled, and as the content operation grew, that risk compounded.

  • Spotify web pages shown in isometric layout

Solution

// Pixel perfection, always

We built an automated sync system on top of Spotify's existing Contentful and Next.js stack. No replatforming or architectural overhaul. The system monitors environments for changes, flags when a sync is needed, and when approved, executes the deployment through a single controlled action.

We also built a visual comparison tool that overlaps staging and production side by side, highlighting exactly where the differences are. What used to take hours now takes seconds. Rate limiting, role-based access controls, and audit logs were built in from day one. The system was designed to scale from two environments to twenty without a rewrite.

Results

  • 80% Reduction in Release Time

    Syncs that used to take two hours now take ten minutes. The content team can move without waiting on engineering.

    01

  • Manual Deployment Errors Removed

    Every deployment runs through the same controlled, repeatable process. Nothing is done manually, so nothing gets missed.

    02

  • Automated Visual QA

    The overlay tool catches differences between environments instantly. The QA team confirms accuracy in minutes, not hours.

    03

  • A System Built to Scale

    The automation scales with volume, handling more environments, more products, and more frequent publishes.

    04