Good evening, operator.
Here is what RONIN sees across your simulated environment.
Important findings
Cost overview · simulated
“staging-api-01 has averaged 1.8% CPU for 96 hours. Review whether it needs to run continuously.”
Deterministic template · no external AIRecent demo activity
Rules evaluation completed
Cost snapshot refreshed
Health score calculated
Resources
Operational details from Kairo Labs’ fictional environment.
Findings
Every result is traceable to a simple demo rule.
Possible underutilised instance
staging-api-01 · i-003
Average CPU below 5% for at least 72 hours.
Average CPU: 1.8%
Observation period: 96 hours
Sustained utilisation is below the demo threshold.
staging-api-01 has averaged 1.8% CPU for 96 hours. Review whether it needs to run continuously.
Potentially oversized EC2 instance
dev-worker-01 · i-004
CPU below 15% and memory below 25% for at least 168 hours.
Average CPU: 7.2%
Average memory: 14.5%
Instance type: m5.xlarge
Compute and memory use remain low.
Compare dev-worker-01 with a smaller instance class in a controlled test.
Unattached EBS volume
staging-snapshot-temp · vol-02
State is available and no attachment is present.
Volume state: available
Attachment: none
Monthly cost: £7.50
The volume is billed but unattached.
Confirm whether staging-snapshot-temp is needed, snapshot it if appropriate, then consider deletion.
Cost spike detected
Kairo Labs (Demo) · environment
Spend exceeds baseline by more than 20%.
Current spend: £286.40
Historical baseline: £220.00
Increase: 30.2%
Current demo spend is materially above its synthetic baseline.
Review EC2 growth and recent simulated resource changes.
Costs
Six-month spend trend
Service allocation
EC2 £142.60
ECS £61.20
EBS £37.40
Load Balancers £29.10
Other Services £16.10
Directional estimates from educational rules, not production-grade advice.
About RONIN
Pre-beta · Demo mode
Fictional AWS data and explainable deterministic checks.
Current functionality
- Synthetic resources and costs
- Four deterministic rules
- Read-only APIs and health
Future local-first companion
Future credential access is intended to remain local. This hosted demo does not access customer AWS accounts.
No credentials. No customer data.
No accounts, keys, uploads, personal data, AWS calls or write actions.