Deploying Infrastructure
Deploying in Archie is a 5-step wizard that takes you from blueprint to live infrastructure in minutes. No terminal, no Git, no CI pipeline.
The Deploy Modal
Click Deploy on any company blueprint to open the Configure Deployment wizard.
Step 1: Method
Choose how to deploy:
- UI Deploy — deploy directly from the dashboard (default)
- Git / PR — create a pull request with IaC code (coming soon)
Step 2: Config
Configure the deployment context:
| Field | Description |
|---|---|
| Target Environment | DEV, STAGING, or PROD (toggle buttons) |
| Stack Name | Auto-generated from the blueprint name, editable |
| App Group | Organize stacks under a named group (optional) |
| Deployment Mode | Greenfield (create from scratch) or Brownfield (adopt existing) |
| Est. Cost | Monthly cost estimate based on the blueprint tier |
App Groups
App Groups organize related stacks. Instead of free-text, you select from a dropdown:
- Choose an existing group (e.g., "networking")
- Or click "+ Create new group" to add one inline
- New groups are saved to your organization — all team members see them
- No typos, no duplicates
Step 3: Parameters
Fill in the configuration fields. Three types of fields appear:
- Locked (grey) — "GOV-002: Locked by platform team" — set by your PE, you can't change these
- Required (red asterisk) — must be filled before deploying
- Editable — free to customize with sensible defaults pre-filled
Fields are organized into sections: Basic Settings, Network Settings, VPC Endpoints, Naming, Monitoring, etc.
Step 4: Credentials
Select which Cloud Account to use:
- Saved account — pick from your organization's Cloud Accounts dropdown
- Shows: account name, account ID, region
- ✓ "Using saved account — no manual credential entry needed"
Deploy Region — pre-filled from the Cloud Account's default region. Override here without editing the account. This lets one Cloud Account deploy to any region.
"+ Use custom credentials" — for one-off deploys with different keys
Step 5: Review
Final check before deployment:
Deployment Summary:
- Blueprint name and cloud provider
- Deploy method, environment, stack name
- Estimated monthly cost
Compliance & Policies:
- Cloud-specific security checks (all must PASS)
- Policy warnings (non-blocking)
- "Ready to Deploy" confirmation
Click Proceed to Preview to run the actual infrastructure plan.
Preview Changes
Archie runs a real Pulumi/Terraform plan against your cloud account:
- Shows +N resources to be created, modified, or deleted
- Lists each resource with its name and status (PLANNED)
- "Schedule for later" option (coming soon)
Review the resource plan, then click Confirm Deploy.
Deployment Progress
After confirming, Archie provisions infrastructure in real-time:
- Progress bar — percentage complete
- Resource Timeline — each resource shows CREATING → CREATED
- Live Logs — expandable, real-time WebSocket log stream
- Cancel — abort the deployment
- Minimize — continue browsing while deploying in the background
Typical deployment times:
- Simple Lambda: 1-2 minutes
- VPC with subnets: 3-5 minutes
- Enterprise 3-tier network: 10-15 minutes
After Deployment
On success, Archie shows:
- "Deployment Complete — Your infrastructure is live and ready"
- Quick Access — key outputs like VPC ARN, endpoint URLs
- All Outputs — expandable list of every Pulumi/TF output
- Resource Timeline — all resources with CREATED status
- View Stack — navigate to the stack detail page
What's Next
- Stacks & Lifecycle — manage, upgrade, and destroy stacks
- Drift & Compliance — monitor for configuration drift