Sentrilite
From deployment to final report, the assessment is fully managed by Sentrilite. Your team's involvement is typically less than two hours in total.
2-minute deployment. No code changes. No SDKs. No billing API credentials. No resource tagging.
If your team spends hours trying to explain why cloud costs changed, this assessment identifies the responsible workloads, quantifies the financial impact, and recommends where to focus first.
2-week Fixed Price Assessment includes:
Cloud Cost Assessment
Walkthrough Demo
Example Assessment Report
Sample Cloud Cost Assessment Report · click to read full-screen
This is a representative sample report demonstrating the format and types of insights delivered. Each assessment is generated from the customer's own environment and findings will vary.
We handle the assessment with minimal effort from your team. No long-term deployment, no operational overhead, and no platform migration.
Everything else is handled by Sentrilite.
After deployment, Sentrilite automatically collects workload telemetry in the background — there is nothing for your team to run or watch.
At the end of the assessment, we review the findings together, and the deployment can be removed immediately if desired.
Most cloud cost platforms explain where your cloud spend went. Sentrilite explains what changed in your infrastructure, quantifies the financial impact, and prioritizes what engineering should investigate first.
Traditional cloud cost platforms provide valuable visibility into cloud spending using billing data, cloud APIs and resource allocation. Sentrilite complements those platforms by identifying workload behavior and infrastructure changes that are difficult to infer from cloud invoices alone. Instead of only showing where money was spent, Sentrilite identifies what changed, estimates the financial impact, and prioritizes engineering actions.
Think of cloud billing as the invoice. Sentrilite identifies the engineering changes that created the invoice.
| Traditional Cloud Cost Platforms | Sentrilite |
|---|---|
| Shows where money went | Explains what changed |
| Shows historical spend | Quantifies financial impact |
| Billing dashboards | Engineering investigation |
| Resource allocation | Workload attribution |
| Requires tagging | No additional tagging |
| Reports costs | Prioritizes what to fix first |
That's all.
Designed for Production Environments
Measured on an EC2 t2.micro instance. Actual usage varies with workload activity and traffic volume.
One fixed price for a fully managed assessment, scoped by deployment size — not your cloud bill. If your environment is larger than the standard scope, we quote it individually before any work begins, always fixed-price.
Need to assess a larger environment? We provide custom assessment pricing for:
Every engagement is scoped before deployment to ensure a fixed price with no surprises.
▶ Contact us for a custom assessmentThe Standard Assessment is designed for small to medium Kubernetes environments. Larger environments are quoted individually based on deployment scope—not software licensing. Our goal is to keep the assessment predictable, transparent, and fixed-price.
If you don't believe the assessment provided meaningful value or actionable insights for your environment, we'll refund the assessment fee—no questions asked.
Our goal is to build long-term relationships by delivering a report your engineering team finds genuinely useful.
A representative slice of what an assessment surfaces — the cost trend, the workloads behind it, and the dollar impact. Your report flags the equivalents hiding in your own environment, each with a recommended fix.
Namespace frontend increased its share of cluster egress from 37% to 44% after a deployment change — the single biggest driver of the week's increase. Estimated impact: $1,650/month.
One existing workload — checkout-svc — began generating cross-region traffic it wasn't before, quietly billing inter-region transfer rates. Estimated impact: $900/month.
3 new workloads appeared during the period and, together, added $1,200/month in egress cost before anyone noticed — flagged the week they started, not at month-end.
Patterns we see consistently across cloud environments. Standard cloud bills show line items — Sentrilite adds runtime workload context, without code changes or instrumentation, so your team can see which workloads are driving spend.
During the assessment, Sentrilite analyzes workload behavior and produces a written report with prioritized findings and recommendations.
One command on your Linux nodes or one DaemonSet for Kubernetes — we're on the call to assist your team through the ~30-minute session. No code changes, no API credentials, no Prometheus required.
Sentrilite collects workload telemetry in the background — no dashboards to monitor, no tuning, no engineer babysitting. Two weeks gives a clean baseline plus a week of comparison data, enough to surface week-over-week patterns, not just snapshots.
You receive the Cloud Cost Intelligence Report, the What Changed Report, and prioritized recommendations. We review the findings together on a 60-minute call, and the deployment can be removed immediately afterward if you'd like.
You keep all the findings, the report, and any savings your team implements. No retainer, no ongoing engagement required.
Every assessment delivers three artifacts: a Cloud Cost Intelligence Report, a What Changed Report, and prioritized recommendations. Findings cover network egress, compute waste, and week-over-week patterns — each with the responsible workload, the dollar impact, and a remediation recommendation.
Process-level cost attribution across your environment. Top spending workloads, cross-region call-outs, internet egress drivers — broken down by namespace, pod, container, and process. The "who is spending what" view your cloud bill can't give you.
Week-over-week patterns: concentration shifts (which workloads are growing share of spend), new workload adoption with dollar impact, cross-region behavior changes, and downsize candidates. The "what changed" view, not just the "what is."
Findings ranked by annual cost impact. Each one includes a recommended fix, estimated savings, and an effort estimate so your team can decide what to tackle first.
Top cost flows by process and destination. Cross-region transfers flagged automatically. Internet vs. intra-cloud traffic distinguished by destination IP. The exact services driving your data transfer bill.
Idle pods with reserved resources running 24/7. Over-provisioned workloads using a fraction of their CPU and memory limits. Dollar value of waste per workload, per week, per year.
AWS, GCP, and Azure in the same report. Bare-metal Linux and hybrid environments supported. One agent across the whole estate.
If your team spends hours trying to explain why cloud costs changed, or struggles to prioritize where engineering should focus first, this assessment is designed for you.
A single Docker container or Kubernetes DaemonSet on the nodes you want to observe. No code changes, no API credentials, no billing integrations. The agent reads at the kernel level using eBPF and ships findings to a local dashboard.
No. All data collection and analysis happens within your environment. The report is generated locally and shared with you over your preferred secure channel. Nothing about your workloads or traffic patterns goes to a third-party cloud.
The Standard Cloud Cost Assessment is a flat $995 — a fully managed, 2-week assessment covering one Kubernetes cluster with up to 5 worker nodes. Larger environments (more nodes, multiple clusters, or multi-cloud) are scoped individually and quoted as a fixed price before any work begins. Pricing is based on deployment size, not your cloud bill or software licensing.
Three deliverables: (1) Cloud Cost Intelligence Report with process-level cost attribution, top spending workloads, and cross-region call-outs; (2) a What Changed Report covering week-over-week patterns — concentration shifts, new workloads, downsize candidates; (3) prioritized recommendations ranked by estimated savings. Plus a 60-minute walkthrough call.
Yes. The agent stays in your environment if you want it to. Many customers who see real-time cost visibility working choose to continue on a subscription basis. The assessment and subscription are priced separately — there's no obligation either way.
Engagements typically start within 5–7 business days of the initial intro call. The 14-day data collection period begins as soon as the agent is installed and verified.
15-minute intro call. No commitment. We'll learn about your environment, you'll learn whether the audit is a fit, and we'll quote you a start date.
Tell us a bit about your environment. We'll reach out within one business day to confirm scope and schedule a short intro call before the assessment begins.