Title: Hi HN, we&#x27;re Lucas and Lucas, the authors of Layerform (https:&#x2F;&#x2F;github.com&#x2F;ergomake&#x2F;layerform). Layerform is an open-source tool for setting up development environments using plain .tf files. We allow each engineer to create their own &quot;staging&quot; environment and reuse infrastructure.<p>Whenever engineers run layerform spawn, we use plain .tf files to give them their own &quot;staging&quot; environment that looks just like production.<p>Many teams have a single (or too few) staging environments, which developers have to queue to use. This is particularly a problem when a system is large, because then engineers can&#x27;t run it on their machines and cannot easily test their changes in a production-like environment. Often they end up with a cluttered Slack channel in which engineers wait for their turn to use staging. Sometimes, they don&#x27;t even have that clunky channel and end up merging broken code or shipping bugs to production. Lucas and I decided to solve this because we previously suffered with shared staging environments.<p>Layerform gives each developer their own production-like environment.This eliminates the bottleneck, increasing the number of deploys engineers make. Additionally, it reduces the amount of bugs and rework because developers have a production-like environment to develop and test against. They can just run &quot;layerform spawn&quot; and get their own staging.<p>We wrap the MPL-licensed Terraform and allow engineers to encapsulate each part of their infrastructure into layers. They can then create multiple instances of a particular layer to create a development environment.The benefit of using layers instead of raw Terraform modules is that they&#x27;re much easier to write and reuse, meaning multiple development environments can run on top of the same infrastructure.<p>Layerform&#x27;s environments are quick and cheap to spin up because they share core pieces of infrastructure. Additionally, Layerform can automatically tag components in each layer, making it easier for FinOps teams to manage costs and do chargebacks.<p>For example: with Layerform, a product developer can spin up their own lambdas and pods for staging while still using a shared Kubernetes cluster and Kafka instance. That way, development environments are quicker to spin up and cheaper to maintain. Each developer&#x27;s layer also gets a tag, meaning FinOps teams know how much each team&#x27;s environments cost.<p>For the sake of transparency, the way we intend to make money is by providing a managed service with governance, management, and cost-control features, including turning off environments automatically on inactivity or after business hours. The Layerform CLI itself will remain free and open (GPL).<p>You can download the Layerform CLI right now and use it for free. Currently, all the state, permissions, and layer definitions stay in your cloud, under your control.<p>After the whole license change thing, I think it&#x27;s also worth mentioning we&#x27;ll be building on top of the community&#x27;s fork and will consider adding support for Pulumi too.<p>We&#x27;d love your feedback on our solution to eliminate “the staging bottleneck&quot;. What do you think?
Upvote: