See what Stag says about a change like yours

• [01]

  Is Stag only for migrations and upgrades?

  No. Simulate routine changes, from network policies to database access. Small changes can affect other systems.

• [02]

  Will Stag catch changes outside our pipeline?

  Yes. Stag detects changes visible through cloud APIs on its next scan, then simulates their effects. Terraform and CI/CD are optional. You can also simulate proposed scripted changes through the CLI before applying them.

• [03]

  Can our agents ask questions and run simulations?

  Yes. Agents can query the deployed environment through MCP without proposing a change. They can also run simulations through the CLI and use the results while writing code.

• [04]

  What if a change affects another team, account, region, or cloud?

  Stag follows dependencies across the environments you connect, including accounts, regions, and clouds. One deployment can cover multiple AWS accounts and Azure subscriptions.

• [05]

  Can Stag help with a migration that’s already underway?

  Yes. Simulate upcoming changes before applying them. Review findings for changes Stag has already observed, and address risks as the migration continues.

• [06]

  What if nothing breaks immediately?

  Stag flags risks to performance and security even when nothing has visibly failed. Use the findings to investigate changes that might otherwise go unnoticed.

• [07]

  Can we use Stag during an incident or to look back at previous changes?

  Yes. Review recorded changes and related simulation findings to focus the investigation. Use the same records for incident reviews and audits.

• [08]

  How does Stag fit into change reviews?

  Reviewers get findings they can inspect: the risks, the reasons, and what to adjust. You decide how simulation fits into your approval process.

• [09]

  What does Stag cover?

  Stag covers AWS, Azure, and Kubernetes resources, including networking, roles and policies, DNS, load balancers, and database settings.

• [10]

  Is Stag SaaS?

  No. You install and run Stag inside your environment.

• [11]

  What does Stag read? Does it need write access?

  Stag uses read-only access to infrastructure metadata, including settings, roles, policies, and connections. It does not inspect business data or network traffic. A detailed data inventory is available for security reviews.

• [12]

  How long does installation take?

  Typically 15–30 minutes. Initial results appear within minutes of providing cloud credentials.

• [13]

  How does Stag use AI?

  Stag uses a breakthrough in causal subgraph enumeration to select and systematically evaluate side effects. AI helps users and agents understand what's happening and how to fix it.

• [14]

  Do we have to let Stag block deployments?

  No. Start in advisory mode and review the findings without blocking deployments. When you’re ready, configure your pipeline to stop changes Stag identifies as unsafe. A break-glass override lets you proceed when needed.

• [15]

  Do all our teams need to use the same pipeline?

  No. Each team can keep its own pipeline. Stag checks their proposed changes against its model of the connected environment.

• [16]

  Will Stag slow down our applications?

  No. Stag reads metadata and simulates against its model. Your application traffic does not pass through it, and your applications do not wait for its results.

• [17]

  Will Stag slow down our CI/CD pipeline?

  Stag adds an inspection step. Most inspections finish in under a minute. Reviewers get the risks, the reasons, and guidance on what to adjust.

• [18]

  How do we update Stag?

  You apply container-image updates inside your environment. Stag does not contact Stag servers to initiate them.

No questions match that search.