Amazon Web Services
Every AWS dollar has an owner. Tags optional.
Tagging tracks less than half of cloud spend. Cloud Intelligence™ reads your Cost and Usage Report, then reads runtime traffic to put shared EKS clusters, databases, NAT and Bedrock calls on the team, customer or feature that used them.
Read-only IAM role · CUR 2.0 · Data within 4 hours of AWS
AWS · October
you can't tag your way to 100%
Cost allocation tags stop at the shared stuff. We don't.
Shared EKS clusters, RDS, MSK, NAT gateways and data transfer have no clean tagging surface. Cloud Intelligence™ reads runtime traffic and allocates every dollar by what actually happened. Your existing tags still count, as one more signal.
See how runtime attribution worksbedrock included
Know what every Bedrock call costs. And who made it.
Bedrock shows up on your AWS bill as one line per model. The sensor reads InvokeModel, Converse and streaming calls, so each token lands on the customer, feature or agent that triggered it.
Explore AI Hubsavings plans, laddered
Commitment savings. Without the big bet.
PerfectScale for Commitments buys Compute and Database Savings Plans in small steps that track your hourly usage, inside guardrails you set.
everything in your aws bill
One AWS view, from bill to fix
Cost & Usage reports
Drill from total spend to a single SKU, by account, service, region or cost allocation tag.
Anomalies in near real time
EC2 and RDS spikes caught from CloudTrail, before the bill.
Insights
Our own checks plus Trusted Advisor and Cost Optimization Hub.
EKS Intelligence
Cluster, namespace and workload cost, with utilization.
Cloud Diagrams
Your AWS architecture, drawn and priced automatically.
Budgets, alerts and CloudFlow
Guardrails and automations on the same numbers.
live in minutes
Connect AWS in three steps
Connect your payer account.
A read-only cross-account IAM role. We find your CUR and import history.
Add the sensor.
One Helm install on EKS, or a script on EC2. About 15 minutes.
Every dollar gets an owner.
Shared and untagged spend allocated by real usage.
Read-only access. Console, CloudFormation StackSets or Terraform.
Start freeFrequently asked
questions
How does Cloud Intelligence™ connect to AWS?
With a read-only cross-account IAM role. We discover your Cost and Usage Report (CUR 2.0 is supported) and import your history. You can link accounts from the console, with CloudFormation StackSets or with Terraform.
How fresh is the data?
Billing data is available in Cloud Intelligence™ less than four hours after AWS publishes it. Near real-time anomaly detection for EC2 and RDS reads CloudTrail, so spikes show up before they reach the bill.
Can I allocate AWS costs without tags?
Yes. The runtime sensor reads traffic to assign shared clusters, databases, network and Bedrock calls to the team, customer or feature that used them. Your cost allocation tags are still ingested, and virtual tags clean up inconsistent keys.
Where does the sensor run?
On EKS and self-managed Kubernetes as a Helm chart, on Linux EC2 instances as a service, and on ECS Fargate. It is read-only and built on eBPF.
Do you manage Savings Plans?
Yes. PerfectScale for Commitments manages Compute and Database Savings Plans in small laddered steps, with optional approval before each purchase.
Do I need to buy AWS through DoiT?
No. You can connect AWS accounts you buy from anyone. Standalone accounts need an Enhanced or Enterprise plan.
Connect AWS. Find the owner of every dollar.
Free to start. Read-only. Live in minutes.