%20(1).svg)
How The OpsPilot Works in Practise
Read Only Crawler
TOP connects to your AWS account using strictly read-only permissions.
The crawler observes, it does not modify, execute, or interfere with your infrastructure.
It is designed to understand:
- Your AWS topology and service layout
- How resources are connected
- Where data moves across services and availability zones
This gives TOP a grounded view of how cost is shaped by architecture in your environment.
The crawler collects signals, not application data.
These include:
- Infrastructure metrics
- Network traffic patterns and data transfer paths
- Resource metadata and configuration context
No raw application data is moved.
TOP only extracts derived results and metadata needed to understand cost behavior.
All collections are read-only, encrypted, and scoped to the minimum required permissions.
Using the collected signals, TOP builds a cost behavior model of your cloud:
- How workloads scale
- How data transfer contributes to cost
- Which architectural patterns are common vs exceptional
- Where cost grows linearly vs non-linearly
This model becomes the baseline for all future estimates.
Importantly, it reflects how your cloud actually behaves, not a generic best-practice template.
TOP integrates directly into how work is planned.
With our Jira integration, you can:
- Associate planned work with cost expectations
- View estimated cloud cost per ticket or initiative
- Compare architectural options before committing to them
This brings cost into the same place where scope, timelines, and risk are already discussed.
When you describe a new workload or feature, TOP combines:
- Your intent (what you’re planning to build)
- Your existing environment context (from the crawler)
- TOP’s service-specific cost engines
The result is a forward-looking estimate that reflects:
- Your architecture
- Your defaults
- Your growth patterns
Not an abstract calculator — a contextual prediction.
How You Use The OpsPilot.
Fully Adjustable, Not a Black Box
Whether you use TOP through Jira or the console, every estimate is transparent and adjustable.
You can interactively change:
- Instance types and sizes
- Availability and redundancy assumptions
- Scaling and utilization expectations
- Data transfer volumes and paths
- Service configurations and architectural choices
As you adjust inputs, TOP shows how cost behavior changes across scenarios.
This allows teams to:
- Understand why something costs more
- See which decisions matter financially
Explore tradeoffs instead of guessing
TOP provides guidance — you remain in control.
Cost Estimation in the TOP Console
TOP also provides a dedicated console where you can describe a workload in plain English.
For example:
“We’re building a service that processes ~2TB/day, uses EMR and S3, and needs high availability.”
TOP translates that intent into a structured estimate using:
- Your existing environment context
- Service-specific cost engines
Realistic architectural defaults
Instead of filling out forms or learning a new model, developers can explain the workload in plain English.TOP turns that description into a cost estimate grounded in your actual environment.
Cost Estimation Inside Jira
TOP integrates directly with Jira, allowing teams to request cost estimates from within the ticket where work is being planned.
From a Jira issue, you can:
- Call TOP to estimate the cost impact of the work
- View cost drivers tied to that ticket
- Compare alternative approaches before implementation
- Understand whether a change is financially minor or structurally significant
This brings cost into the same workflow as scope, timelines, and risk — without requiring a separate tool or process.
