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 CenterEnvironments

Environments

An Aithroyz environment is a fully isolated, pre-wired collection of SOC tools deployed to your cloud account. Each environment gets its own VPC, DNS zone, and HTTPS subdomains.

Each environment is completely isolated from other environments — separate VPC, separate DNS zone, separate credentials. You can run multiple environments simultaneously, each with different tool combinations.

In this section

Lifecycle PhasesTrack environments from draft → queued → deploying → live → destroyedTTL Auto-DestroyAutomatically teardown environments after a configured time to avoid runaway costsExtending TTLExtend an active environment before its TTL expiresDestroying an EnvironmentManually tear down all cloud resources for an environment

What gets deployed per environment

VPC + Subnet
Dedicated 10.0.0.0/24 network for the environment
Firewall rules
Allows HTTPS (443) from internet, internal tool-to-tool traffic
Gateway VM
Caddy reverse proxy on a static IP — routes traffic to each tool, runs Google SSO forward auth
Cloud DNS zone
Wildcard DNS for all tool subdomains under <env>.ops.aithroyz.com
Tool VMs
One VM per selected tool (or shared VMs for small tools)
GCS bucket
Terraform state storage — used to track and update the deployment
Related Articles
Lifecycle PhasesRead article →TTL Auto-DestroyRead article →Tools OverviewRead article →