# Internal Tooling

# 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 <span class="s1">**live preview environments**</span> from a GitHub branch
- Automatically assign a <span class="s1">**subdomain**</span> 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?**

- <span class="s1">**Developers**</span> testing features on real infrastructure
- <span class="s1">**Product managers**</span> reviewing work-in-progress
- <span class="s1">**Teams**</span> managing multiple temporary environments

You do <span class="s2">**not**</span> 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 <span class="s1">**Deployments Dashboard**</span>

> 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 &amp; 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 <span class="s2">**“Create Deployment”**</span> to open the deployment form.

##### **Required Information**

You’ll be asked for:

<table id="bkmrk-field-what-it-means-" style="height: 244px; width: 98.7654%;"><thead><tr><th style="width: 49.9375%;">**Field**

</th><th style="width: 49.9375%;">**What It Means**

</th></tr></thead><tbody><tr><td style="width: 49.9375%;">**Name**

</td><td style="width: 49.9375%;">A unique identifier for this site

</td></tr><tr><td style="width: 49.9375%;">**Subdomain**

</td><td style="width: 49.9375%;"><span class="s1">The URL prefix (e.g. </span>alpha<span class="s1"> → </span>alpha.yourdomain.com<span class="s1">)</span>

</td></tr><tr><td style="width: 49.9375%;">**GitHub Repository**

</td><td style="width: 49.9375%;">The repo to deploy

</td></tr><tr><td style="width: 49.9375%;">**Branch**

</td><td style="width: 49.9375%;">The branch to deploy (usually <span class="s1">main</span>)

</td></tr><tr><td style="width: 49.9375%;">**Requires Authentication**

</td><td style="width: 49.9375%;">Whether login is required to view the site

</td></tr><tr><td style="width: 49.9375%;">**Include Root Domain**

</td><td style="width: 49.9375%;">Whether the root domain should also point to this site

</td></tr></tbody></table>

##### **What Happens Next?**

Once you submit:

1. The deployment is queued automatically
2. You are redirected to the <span class="s1">**Deployment Status**</span> page
3. Infrastructure and site setup begin in the background

No further action is required from you.

#### **Monitoring a Deployment**

Each deployment has a <span class="s2">**status view**</span> that updates automatically.

##### **What You’ll See**

The deployment progresses through stages such as:

- <span class="s1">**Source**</span> – pulling code from GitHub
- <span class="s1">**Build**</span> – preparing the site
- <span class="s1">**Deploy**</span> – 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 <span class="s1">**live URL**</span> 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:

1. Click <span class="s1">**Delete**</span> on the deployment
2. 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 <span class="s1">**clear names**</span> for deployments (e.g. <span class="s2">feature-auth-redesign</span>)
- Delete deployments once testing or review is complete
- Use separate deployments for parallel feature work
- Share the live URL with stakeholders instead of screenshots