University of Surrey optimizes developer operations by shifting to Platform.sh

With a history dating back to 1891, the University of Surrey has never been afraid to evolve. In fact, in 1956, the University was one of the first institutions to be named a college of advanced technology. 

To date, Surrey has welcomed more than 140,000 students through its doors, including its current class of ~15,000 students. The Surrey Research Park continues the institute’s legacy of collaboration, adaptation, and innovation.

So it’s no surprise that Surrey’s digital team has high standards for its underlying technology. But in 2014, their decentralized suite of websites became too challenging to manage; with clunky operations and lengthy publishing times, something had to change. 

Unfortunately, it wasn’t an instant fix. The digital team endured two years of trial and error, searching for a system to simplify DevOps, giving developers more time to focus on code and innovation.

The shift away from on-premises hosting

Historically, the University's IT team had managed and hosted the digital team's websites on-premises. But when the IT team added Drupal on top of their legacy content management system, they also added layers of complexity. Although a full switch to Drupal was imminent, the IT team didn't have the resources to maintain Drupal, along with the rest of the digital team's tech stack, in-house.

While a few of the digital team’s 10 websites were low maintenance, many of them required daily changes. An overnight publishing process impacted team agility and their ability to give attention to high-value work. It was clear that on-premises hosting just didn’t make sense anymore. The Surrey team needed a new solution—fast.

Initially, they chose Acquia to carry them through their transition to managed services. But as the development team grew, so did the tool’s constraints. With the original team size of 3 devs, communications and collaboration around a single dev environment was possible—but with 8 developers, it was unsustainable.

Surrey Lead Digital Developer Daniel Gittings recalls that developers were frequently forced to wait until the only dev environment was available. This created significant delays, which the team was eager to overcome—but that meant another system migration. To make a strategic and lasting decision, they outlined their must-haves for the new platform. 

• Seamlessly integrates with Drupal and GitHub
• Offers preview environments for user acceptance testing (UAT) to foster real-time collaboration and rapid approvals
• Scales to accommodate larger teams and additional sites
• Provides responsive, caring customer support 

After vetting a few options, Platform.sh emerged as the best choice for all these needs.

Surrey developers share why Platform.sh is the right long-term partner

Since the switch to Platform.sh eight years ago, it’s been more convenient and simpler than ever for Surrey to scale, adding sites to their portfolio as the need arises. Here’s what Surrey lead digital dev team members Daniel Gittings (DG) and Chandra Rajakumar (CR) value most about Platform.sh services and support.

Seamless integration, configuration, and capabilities

Simplified review cycles

Customer support and rapid response times

Standing the test of time

Surrey’s digital team has undergone structural changes over the years. Developers have come and gone. Surrey recently rebranded, requiring changes to their suite of sites. But they say the Platform.sh team has given them the confidence to weather it all.

And as Surrey approaches a decade of partnering with Platform.sh, the digital team is grateful for the efficiency, collaboration, and agility they’ve gained. The seamless integration, combined with robust support and configuration flexibility, has enabled the university to maintain a smooth and productive digital presence. And as the university continues to grow and evolve, Platform.sh remains a trusted partner in their digital transformation journey.