Get up and running on AWS with DevOps best practices and world-class infrastructure in about 2 weeks

Building infrastructure for a software company is much harder than it should be. There are so many moving parts and so many concepts to learn. How do I build my code? How do I deploy it? Should I use Docker? How do I deploy a Docker container? Where should I store database passwords? How do I manage SSH keys? What do I do when a server goes down? How can I be sure I don’t lose data? How do I even know that a server is down? It seems like there is never enough time to get all of these right and many companies end up scraping their infrastructure together using duct tape and glue.

This was the problem I set out to solve when I launched Atomic Squirrel last year. Along the way, I met Josh Padnick, who was trying to solve the same problem at his company, Phoenix DevOps. 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.

Gruntwork’s mission is to make it an order of magnitude easier to understand, develop, and deploy software. We’ve taken the thousands of hours we spent building infrastructure on AWS at Atomic Squirrel and Phoenix DevOps and condensed all that experience and code into pre-assembled Infrastructure Packages that are:

Some of the most popular Infrastructure Packages that we offer are:

Using these packages, we can get your company up and running on AWS with DevOps best and world-class infrastructure practices in about 2 weeks. That’s a fraction of the time — and a fraction of the cost — it would take you to do it from scratch. This way, you can focus on your product, and we can take care of the grunt work.

For more info, and to get in touch, check out www.gruntwork.io, follow us on Twitter, Facebook, LinkedIn, Google, and GitHub, and subscribe to our newsletter.