Blueprint Deploy User Guide Blueprint Deploy lets you create, monitor, and manage live website deployments from GitHub with just a few click, no AWS or CI/CD expertise required. What Is Blueprint Deploy? Blueprint Deploy is a dashboard that helps you: Spin up live preview environments from a GitHub branch Automatically assign a subdomain to each deployment Monitor deployment progress in real time Cleanly remove deployments when they’re no longer needed It abstracts away infrastructure and CI/CD complexity so you can focus on shipping and testing your product. Who Is This For? Developers testing features on real infrastructure Product managers reviewing work-in-progress Teams managing multiple temporary environments You do not need AWS or DevOps knowledge to use this tool. Getting Started Sign In Open the Blueprint Deploy dashboard Sign in using your organization credentials Once signed in, you’ll land on the Deployments Dashboard You will stay signed in across sessions unless you explicitly log out. Dashboard The dashboard is your control center. You’ll see: A list of all active deployments Name Subdomain GitHub repository & branch Current status Each deployment’s: From here, you can: Create a new deployment Monitor an in-progress deployment Delete an existing deployment Creating a New Deployment Click “Create Deployment” to open the deployment form. Required Information You’ll be asked for: Field What It Means Name A unique identifier for this site Subdomain The URL prefix (e.g. alpha → alpha.yourdomain.com) GitHub Repository The repo to deploy Branch The branch to deploy (usually main) Requires Authentication Whether login is required to view the site Include Root Domain Whether the root domain should also point to this site What Happens Next? Once you submit: The deployment is queued automatically You are redirected to the Deployment Status page Infrastructure and site setup begin in the background No further action is required from you. Monitoring a Deployment Each deployment has a status view that updates automatically. What You’ll See The deployment progresses through stages such as: Source – pulling code from GitHub Build – preparing the site Deploy – making it live Each stage shows one of: In Progress Succeeded Failed If something goes wrong, the deployment clearly shows where it failed. When It’s Done Once successful: A live URL appears You can open the site immediately The link can be shared with others You can bookmark or share the status page—it will continue to work. Viewing Existing Deployments From the dashboard, you can: See all active deployments Quickly identify which are running or completed Click into any deployment to see its details or status This helps teams track infrastructure usage and avoid forgotten environments. Deleting a Deployment When you no longer need a site: Click Delete on the deployment Confirm the action What Deleting Does Removes the live website Deletes the associated infrastructure Cleans up the GitHub repository created for that deployment This helps keep costs and clutter under control. Deletions are immediate and cannot be undone. Best Practices Use clear names for deployments (e.g. feature-auth-redesign) Delete deployments once testing or review is complete Use separate deployments for parallel feature work Share the live URL with stakeholders instead of screenshots