Built on your real environment
Insights that understand your environment
Every insight is built from a complete picture of your environment: cost and usage over time, the event timeline behind today's state, current configuration of every resource, ownership and allocation metadata, and the full graph of how your resources connect. That's why an insight knows the difference between your production and staging environments, which team owns the workload, and how usage has actually shifted over the last 90 days. Cloud providers surface what their APIs expose. Insights surface what actually matters in your environment.
Key capabilities
Everything Insights gives you
700+ proprietary recipes
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 700+ 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 700+ 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 APIs expose, which is a narrow slice of what's happening. Composer builds a real model of your environment, including longitudinal cost and usage, the event timeline, and the full resource graph.
What clouds are supported?
AWS has the richest data depth today. Google Cloud and Azure coverage are expanding.
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.
What plans include Composer?
Composer and the 700+ recipe library are available on DCI, Enhanced DCI, and Enterprise ChannelOps T3. Custom recipes, Cloud Diagrams, and CloudFlow automation are on DCI and Enhanced DCI. Policy enforcement is coming.