Phoenix DevOps is now Gruntwork!

In 2014, I launched Phoenix DevOps to ramp up software teams on Amazon Web Services and DevOps. Along the way, I met Yevgeniy Brikman, who was trying to solve the same problem at his company, Atomic Squirrel. Our companies began working together and after many months and many happy clients, I’m happy to announce that we are now officially joining forces at a single new company called Gruntwork!

For more info, check out the Gruntwork announcement blog post and

Meet the Team

Josh Padnick

Yevgeniy Brikman

Our Clients

It has been our privilege to work with software teams of all sizes, including:

How We Help

Teams often need the help of an AWS & DevOps consultant
to build delivery automation, or train their engineers to do it themselves.
Our most common services include:

  • Use tools like terraform for "Infrastructure as Code"
  • Setup the build pipeline
  • Setup the asset pipeline (compilation, hashing, CDN)
  • Configure build servers like Jenkins or CircleCI
  • Automate deployment
  • Setup central log aggregation
  • Setup monitoring and alerting
  • Convert your app to 12-factor
  • Security (TLS/SSL, secrets management, VPC, etc.)

About Phoenix DevOps

Our mission is to make DevOps effective, accessible, and affordable to software teams that use Amazon Web Services.

There was a time a few years ago when Josh was responsible for delivering complex software. While working software was delivered on time, the team failed to deliver to its full potential. Setting up the first production infrastructure took 3 months. Deployments took 2 weeks. Setting up a new dev environment took 1 week. There was limited monitoring, no central logging, no metrics, no self-healing infrastructure, and sloppy secret sharing.

Because the team had no expertise in infrastructure automation, ops projects dragged on while core business features got delayed. Professionally, valuable business opportunities were missed. Personally, it was a source of stress and frustration.

There had to be a better way to build software, and a better way to live.

Josh began to dive deep on learning all aspects of infrastructure automation. He consumed countless books, articles, and videos. He attended local meetup's and national developer conferences. He used side projects to explore new technologies and techniques.

Soon he was invited to speak at small local conferences. Then larger conferences and meetup's. He published a Comprehensive Guide to Building a Scalable Web App on Amazon Web Services - Part 1 and began receiving inquiries from clients who needed help.

In late 2015, Josh and Jim got connected as they pursued the common interest of automating software infrastructure. Working together, they began to standardize an approach to DevOps, build a library of scripts and best practices, and work with increasing efficiency to help clients achieve their DevOps goals.

Today, our goal is to relieve teams of as much "undifferentiated heavy lifting" as possible by applying a thoughtful, personalized approach to each client engagement.

The Name "Phoenix DevOps" is a double-play on words:

  • The concept of a "Phoenix" Server is a central tenet of DevOps.
  • Phoenix DevOps is based in the Phoenix, AZ metro area.