bespoke to your environment
Your environment is bespoke. Your insights should be too.
Every insight is bespoke, built from your cost and usage, your resource configurations, your ownership and allocation, and the full graph of how your cloud connects.
So it knows production from staging, who owns the workload, and how usage actually shifted.
Cloud providers surface what their built-in rules expose. We surface what matters in your environment.
key capabilities
Everything Insights gives you
800+ proprietary checks
Continuously evaluated across cost, security, performance, reliability, and operations.
Custom recipe builder
Policy editor with historical simulations before you enable in production.
History over time
Cost, usage, events, and configs with full history.
Resource relationship graph
The full graph, not individual nodes in isolation.
Real savings estimates
Derived from your actual billing and usage, not provider guesses.
Policy enforcement
Define once. Composer enforces continuously and catches regressions.
proprietary recipes
well-architected pillars covered
engine across every workflow
custom recipes
Build your own with the policy editor
The 800+ recipes cover most of what teams need. The policy editor covers the rest. Define a check for your architecture or cost thresholds, run it against historical data as a simulation, then enable it in production. Custom recipes are first-class citizens.
connected to what happens next
A finding is the start, not the end
Every Composer recipe that fires connects directly to investigation, automation, and enforcement, with no handoffs between tools. Investigate in Cloud Diagrams. Automate with CloudFlow. Create tickets in Jira or Linear. Send alerts in Slack or Teams. Define a policy, and Composer enforces it continuously.
Run your cloud on your terms
See what Composer finds in your cloud.
Frequently asked
questions
What is Composer?
DoiT's proprietary intelligence engine. It scans your environment across cost, usage, events, configurations, and resource relationships, then runs 800+ recipes against that data to surface issues your cloud provider can't.
How is this different from cloud provider recommendations?
Providers work from what their built-in rules expose, which is a narrow slice of what's important and relevant. Composer builds a real model of your environment, including longitudinal cost and usage, the event timeline, and the full resource graph. You can customize and build recipes based on your policies and context to remove any noise.
What clouds are supported?
The full breadth of the DCI platform is covered including AWS, Google Cloud, Azure, Kubernetes and more.
Can I build my own recipes?
Yes. The policy editor lets you define recipes specific to your architecture, naming, or cost thresholds, with historical simulations before you enable them.
How does Composer calculate savings?
From your actual billing data and actual usage over time. Not provider estimates. Dismissed insights don't inflate the total. Actioned insights are tracked separately so you can track, measure and report on realized value.
Are Insights only about costs?
No. Cost is one of five pillars — alongside security, performance, reliability, and operations. Every action path (CloudFlow, Terraform PR, Jira ticket) works for any finding type, regardless of category.