Help Center← Back to Dashboard
Getting Started
What is Aithroyz?Quickstart: First EnvironmentCloud CredentialsPlans & Approvals
Environments
OverviewLifecycle PhasesTTL Auto-DestroyExtending TTLDestroying an Environment
Tools Reference
OverviewElastic Stack (SIEM)Wazuh (XDR)MITRE CalderaTheHive & DFIR-IRISVelociraptorOpenCTIGrafana + PrometheusShuffle SOARn8nUptime KumaLLM GatewayOpen WebUIFlowiseOpenClawOllamaQdrantLangfusePortainerGiteaSonarQubeCode ServerMattermostMinIOMetabaseHashiCorp VaultKeycloak SSONetBoxLocalStack
Access & Security
Google SSOTenant IsolationPasskeys & MFATeam Members
API & Integrations
API KeysMCP Tools (Clevername)Terraform ExportWebhooks & Callbacks
Stack Presets
SOC PlatformIR / DFIR LabThreat HuntingQuick Sandbox
Settings
Cloud KeysAPI KeysBillingAudit Log
Troubleshooting
Common IssuesDeployment FailuresDNS & ConnectivityTool Health Checks
Aithroyz Help
Help CenterEnvironmentsLifecycle Phases

Lifecycle Phases

Every Aithroyz environment moves through a defined set of phases from plan creation to destruction. Understanding these phases helps you track what's happening and when to take action.

draft— Draft

The plan has been generated but not yet submitted. No cloud resources exist. You can edit the tool selection, name, or TTL, then submit when ready.

Edit planSubmit for approvalDiscard
queued— Queued

The plan is submitted and waiting for an operator to approve. Nothing is deployed. The operator will see it in their request queue.

Approve & Apply (operator)Reject (operator)
pending_sa_approval— Pending SA Approval

If SignedApproval is integrated, the plan waits for a cryptographically signed approval from the iOS app. The dashboard polls every 4 seconds and updates automatically.

Approve on iOSReject on iOS
deploying— Deploying

OpenTofu is running. VMs, DNS records, and tool containers are being created. Live status updates appear on the request detail page. Takes 8–20 minutes.

View live logsWait for completion
live— Live

All tools are deployed and health checks have passed. Tools are accessible via their HTTPS subdomains. TTL countdown is running if configured.

Access toolsExtend TTLDestroy environment
failed— Failed

Deployment encountered an error. Partial resources may have been created. Check the live log for the specific failure. Use Retry to re-attempt from where it left off.

View error logRetry deploymentDestroy partial resources
destroying— Destroying

OpenTofu destroy is running. All VMs, DNS records, and GCS state are being deleted. This takes 2–5 minutes.

Wait for completion
destroyed— Destroyed

All cloud resources have been deleted. No further cloud costs. The environment record is kept in the dashboard for reference but all compute is gone.

View audit logCreate new environment
ℹ
The retryoption on a failed deployment re-runs OpenTofu from the current state — it doesn't start from scratch. Resources that were already created are preserved and the apply picks up from where it failed.
Related Articles
TTL Auto-DestroyRead article →Destroying an EnvironmentRead article →Plans & ApprovalsRead article →