102 Pantheon Testimonials

"Pantheon’s managed distribution tools are unbelievable. Without Pantheon, we’d need to do another 100 hours of custom development operations. There’s nothing else on the market like it, period."

"The new website is serving the Senate and New York State well. We think that every legislature in the country could benefit from this toolset."

"Now we can react to the metrics in a way we couldn’t before."

"Pantheon makes our whole team more efficient."

"Using Pantheon wasn’t a question—we knew it was the best fit for the backend, and that not having to manage infrastructure would help us meet our deadline."

"Thanks to Pantheon, I am no longer spending the majority of my time maintaining servers. I am confident that our site can keep up with pace of the organization."

"On Pantheon, Patch.com is running at 50 million pageviews & 20 million uniques a month at 99.969% uptime across approximately 35 million URLs, 40 terabytes of images, 500 terabytes of video, 6 million registered users, 15 million stories and we have 4 developers."

"It is so comforting to run our website on Pantheon. I know we’re covered no matter what might happen tomorrow."

"Working with [Pantheon’s] engineers and seeing the same enthusiasm and excitement we have on our side, I thought, ‘This is locked in. We are going to be customers for a very long time."

"As an agency, we focus on helping clients drive continual improvement and see an ever-increasing return on their investment. No one wants to get hung up on infrastructure."

"Not having to use local dev environments and virtual machines reduced production time by 50%. That’s why we use Pantheon."

"Pantheon saves my team at least 5 hours a week just in the speed of dev environments."

"We had our own internal development infrastructure, but we saw that Pantheon was better. Multidev branches have become essential for our development process."

“The development pipeline was not working effectively, and it was causing delays and inefficiency. As an example, I would need to send a team member files so he could update code, but I was in the U.S., and he was in Belgium. Our time zones didn't line up, so I had to wait until the next day to update anything.”

“Our content was not with one hosting provider. Some of our sites were hosted by the product teams. Some of the sites were hosted by agencies. We needed to bring everything onto a single roof.”