How Step2Dev Handles Multi-Project DevOps: The Technical Design

How Step2Dev Handles Multi-Project DevOps: The Technical Design I am building in public, so I want to share the actual technical decisions behind Step2Dev's multi-project architecture. This is how we handle the core challenge: multiple projects, multiple AWS accounts, one consistent experience. ## The Problem We Are Solving A DevOps engineer managing 5 projects across 3 AWS accounts today uses: Multiple browser sessions for different AWS accounts Different pipeline configurations stored in different repositories Separate monitoring dashboards per account Mental overhead to track which account/project/environment they are currently in The tools are not connected. The engineer's brain is the connection layer. ## Design Principle 1: The Project Is the Abstraction In Step2Dev, the "project" is the top-level concept. Not the AWS account. Not the region. Not the environment. A project contains: its AWS account connections, its environments (dev, staging, prod), its services, its pipelines, i