Skip to main content
3 min read

Give Developers Self-Service Infrastructure

Give Developers Self-Service Infrastructure

Goal: developers get the infrastructure they need in minutes, and the platform team still controls what gets built.

Without StackGen, a developer files a ticket, a platform engineer writes or copies Terraform, reviews it, and runs it. Each request waits in a queue, and each copy drifts from the standard.

With StackGen, the platform team publishes approved modules and templates once. Developers assemble appStacks from them on a canvas, StackGen generates the Terraform and checks it against policy, and the result is deployed or pushed to Git.

Who does what​

RoleDoes
Platform team (Admin, DevOps)Publishes modules and templates, sets environments and credentials, assigns governance.
DeveloperCreates appStacks from templates or modules, fills in inputs, deploys.

Set it up (platform team)​

  1. Create a workspace for the team. Add the developers with the Developer role. See Create a workspace.
  2. Publish approved modules. Import your Terraform modules from Git or the Terraform Registry into the Module Registry. See Module Registry.
  3. Set up environments. Give the workspace default environments, cloud credentials and a state backend so developers never handle them. See Environment configurations and Plan & Deploy requirements.
  4. Assign governance. Attach the policies every appStack in the workspace must pass. See Governance Configuration.
  5. Publish templates for common architectures. Build an appStack, open Edit appStack Details and select Mark as Template. Developers then see it under Start from appStack templates. See IaC from Templates.

Use it (developer)​

  1. In appStacks, select New appStack and pick a template, or start from scratch.
  2. Add modules from the registry and fill in their inputs. Required inputs and policy violations are flagged as you go.
  3. Select Actions > Plan & Deploy to deploy, or Push to git to hand the Terraform to your pipeline.

The Quickstart walks through these steps with screenshots.

Other ways in​

  • Backstage. Developers can create appStacks from Backstage software templates. Available on request. See Backstage self-service.
  • IDE and AI assistants. Developers can create and change appStacks from Cursor, VS Code or Kiro through the StackGen MCP server. See StackGen MCP.

What you get​

  • Developers ship infrastructure without waiting on a ticket queue.
  • Every appStack uses approved modules and passes the same policies.
  • The platform team changes a module or policy once, in one place.