Start with topology and failure simulation, then expand into dependency intelligence, change impact, security paths, and controlled recovery.
For focused AWS teams building dependency visibility.
For growing teams operating a connected cloud environment.
For organizations with custom scope, controls, and deployment requirements.
Resource and account limits provide a clear starting point. Enterprise scope is defined through an approved agreement.
On smaller screens, scroll horizontally inside the table to compare Growth and Enterprise.
| Capability | Starter | Growth | Enterprise |
|---|---|---|---|
| AWS accounts | 1 | Up to 10 | Custom |
| Discovered resources | Up to 500 | Up to 5,000 | Custom |
| Live topology | Core | Advanced | Advanced |
| Dependency analysis | Basic | Expanded | Expanded |
| Failure simulations | Basic | Advanced | Custom scope |
| Blast radius | Preview | Included | Included |
| Change impact | — | Included | Included |
| IAM paths | — | Included | Included |
| AI investigation | — | Included | Policy-configured |
| Infrastructure history | CloudTrail timeline | Expanded timeline | Custom retention scope |
| Reports | Email reports | Advanced reports | Custom reporting scope |
| Notifications | Email and workflow options | Contracted options | |
| Retention | Standard | Expanded | Custom options |
| User roles | Core workspace roles | Expanded workspace roles | Advanced access controls |
| Support | Standard email | Priority email | Contracted support options |
| Onboarding | Self-guided | Guided options | Scoped assistance |
A discovered resource is an infrastructure entity represented and retained in the StackScopes workspace, such as a supported compute, network, database, storage, identity, or messaging resource.
An AWS account is a distinct account identifier connected to a StackScopes workspace within the approved discovery scope. AWS Organizations structure does not merge multiple account identifiers into one billable account.
Discovery is designed around read-only access. Any controlled recovery capability uses a separate, restricted execution model and remains subject to policy, simulation, and human approval.
The standard discovery model uses a scoped cross-account read-only role for approved AWS discovery workflows. Permissions should follow least privilege, use an external ID where applicable, and remain visible through AWS audit records.
StackScopes will not silently expand the plan. The team can review usage and choose whether to reduce scope or move to a higher limit.
Account and discovered-resource usage is measured from the workspace scope and the infrastructure entities retained by the product. Temporary collection failures do not silently redefine the contracted limit.
A team can request a plan change when its account, resource, feature, or control needs change. Effective timing and any billing adjustment follow the applicable checkout terms or written order form.
Cancellation timing, renewal, service end date, data handling, and any refund rights follow the applicable checkout terms or written order form. Contact sales or support before the relevant renewal date.
Standard plan access does not automatically include a professional-services engagement. Optional onboarding and assessment services are scoped separately.
Yes. Dependency mapping, simulation readiness, change-risk review, recovery planning, and custom topology modeling can be scoped as separate services.
Annual agreements are available by discussion. Public monthly prices are shown for Starter and Growth; Enterprise uses custom annual pricing.
Enterprise scope can include custom account and resource limits, AWS Organizations context, multi-Region modeling, advanced access controls, configurable retention options, controlled-remediation workflows, onboarding assistance, and contracted support options.
Published prices exclude applicable taxes unless a written order form states otherwise.
StackScopes