Organizations are in constant need of sandboxes for developing the next great thing. I wrote a blog back in 2013 about how the ease of access and low costs available via public clouds enable computer science students to develop, test, and learn at a quicker pace. I realize now that this does not at all apply exclusively to students – even Snapchat started out as a concept with the burden of proof prior to becoming the behemoth they are today. Google Cloud Platform (GCP) provides the ideal environment for such development and test workloads. Without the traditional bounds of procuring computing resources for dev/test, teams can develop, iterate, test, fail, and learn at a quicker clip without the costs previously associated with such work. Furthermore, GCP provides access to numerous intelligent management tools which are fully integrated within the platform. GCP also provides access to a new generation of developer tools, designed to allow developers to focus on their code with little regard for the underlying infrastructure. Essentially, they can expect things to “just work.” In this post, I’ll review the extremely simple process required to spin up (and down) a dev/test environment based in Google Cloud Platform. We’ll explore the work required to create an environment which will collect, store, process, and present information from our front door (entry scans).