Iron Clear lifecycle boundaries
Keep development, test, and production agents and settings visible as separate operating environments.
EnvironmentsSeparate development from production.
Separate development from production.
Plan the right operating boundary.
Keep development, test, and production work in distinct environments with their own lifecycle, region, experimentation, protection, and assigned-agent settings. Enterprise agreements can add contracted residency, deployment regions, and private runtime arrangements.
How it works
Commercial availability and runtime residency are different decisions.
Iron Gorilla is generally available to customers in the United States and European Union. The Environments workspace separates development, test, and production inside the organization’s active deployment pattern. Contracted residency, region, private, dedicated, hybrid, on-premise, or air-gapped commitments are defined in an Enterprise agreement.
Product Walkthrough
Review customer boundary, deployment pattern, and environment protections.
See how development, testing, and production stay separate, how live work is protected, and where Enterprise deployment commitments become part of the plan.
Production protection in view
Production environments require live-operations protection and do not expose experimentation as an active option.
A deployment pattern you can review
See whether the organization uses a hosted, private, or hybrid pattern; migration is coordinated through support rather than changed with a toggle.
Why it matters
What this changes once the work gets real.
Assigned agents affect changes
The environment shows how many agents are assigned, and an environment in use cannot simply be deleted.
Region stays inside the active pattern
Available placement options reflect the organization’s deployment arrangement rather than general commercial availability.
Enterprise commitments stay contractual
Residency, contracted regions, dedicated or private infrastructure, on-premise, and air-gapped arrangements depend on the signed agreement.
Give every stage of AI work a deliberate operating boundary.
Separate lifecycle, protection, placement, and assigned agents while keeping Enterprise commitments explicit.