IronArchitects Documentation
IronArchitects turns solution requirements into a governed architecture package: an AI-generated, control-checked design that a human architect decides on, a reviewer approves, and the platform then watches in production for drift.
Everything in the product hangs off one object, the design package, and every package moves through the same five-stage lifecycle. This documentation follows that structure, so the navigation above mirrors the tabs you see inside a package.
The five stages
-
1 · Design Inputs
What the design is built from: requirements, uploaded knowledge documents, applicable regulations, and structured input fields. Includes Jira import/export for requirements.
-
2 · Architecture
The automated design loop: generate, review the components and flows, decide open gaps, keep the authorization boundary stable, and capture decisions, cost, and value.
-
3 · Assurance
The evaluation home: control-by-control compliance results, the multi-agent design review, the risk register, and governed exceptions.
-
4 · Review & Approval
The stage gate: approval readiness, assigned reviewers, request-changes and approve decisions, and the revision lifecycle after approval.
-
5 · Operate
The approved design in production: continuous drift detection, the conformance gate for CI/CD, delivery planning with Jira or Azure DevOps, and migration planning.
-
Diagrams
C4 views generated from the design itself: Context, Container, Component, and Deployment, with exports.
Where to start
- New to the product? Start with Getting started: sign in, create a package, and walk the lifecycle once.
- Setting up your organization? Go to Settings for the technology catalog, members and roles, and integrations.
Feature availability by plan
Some capabilities are plan-gated (for example, design chat on Medium and above, drift detection on Medium and above, the conformance gate on Large and above). Each page notes its required plan; the full picture is on Plans and feature tiers.