Frequently Asked Questions

Disipate is a Cloud Resource Intelligence platform for AWS teams. It infers resource ownership across your environment, surfaces tag recommendations for human review, and turns that ownership layer into cost savings and a stronger security posture.

Disipate analyzes your AWS environment to identify signals that indicate which team or individual is responsible for each resource. Inferred ownership is surfaced as a recommendation for your team to review — not applied automatically.

All tag recommendations require human review and approval before being applied. Nothing is written to your AWS environment automatically. You see the inferred owner, review it, and approve or reject before any tag is created.

Disipate integrates with AWS Security Hub and Wiz, surfacing resource intelligence and ownership context so security findings are attributed to the teams responsible for remediating them.

Disipate reads from your AWS Cost and Usage Report (CUR). For tagging, it requires write access scoped exclusively to the Disipate tag namespace — for example, disipate:inferred-owner. No broad IAM permissions are required. Disipate cannot read, modify, or delete your workloads, configurations, or existing tags.

No. Disipate only writes and removes tags within its own namespace (disipate:*). Your existing tags are never overwritten or deleted. The two tag sets are entirely separate.

Disipate offers two processing options. In the first, all processing happens within your own AWS account — Disipate provisions resources inside your environment and your data never leaves. In the second, the CUR is temporarily exported for processing and then deleted. No customer data is stored persistently outside your environment under either option.

Disipate is currently in early access and is designed to align with SOC 2 and ISO 27001 requirements. Formal certification is on the roadmap. Our Security & Trust page documents the specific access model, data handling, and architectural decisions that underpin our security posture.

Offboarding is clean. Disipate removes all tags in its namespace from your resources. No other tags, configurations, or infrastructure are affected. Your environment returns to exactly the state it was in before Disipate was connected.

Disipate is built for engineering and platform teams operating AWS at scale — typically organizations spending $50,000 or more per month on AWS, where resource ownership has become complex, tagging is inconsistent, and the cost of invisibility is measurable.

Early access is free. We work with a select group of organizations at no cost in exchange for the opportunity to document outcomes — anonymized if preferred — as case studies.

Beyond early access, pricing will be available in two models:

• Savings-based: a one-time fee tied to annualized savings identified — you pay from what you save
• Subscription: a monthly fee for ongoing resource management, tagging, and security visibility

Start by getting in touch. We're selectively onboarding early access organizations and work closely with each team through setup. There's no self-serve trial at this stage — we want to make sure the fit is right before either side commits.