Ask your infrastructure bill a question. Get an answer.
OpsLens connects to your cloud cost exports, Kubernetes metrics, and on-prem observability data — then lets you query everything in plain English using your own AI key. No data leaves your infrastructure.
Works with AWS · GCP · Kubernetes · Prometheus · On-prem
Your cloud bill is a black box
Engineering teams are drowning in cost data but starving for answers.
Raw numbers, zero answers
Cloud dashboards and billing exports tell you what you spent, not why it spiked, which team owns it, or what to fix first. You are left joining spreadsheets by hand.
SaaS FinOps tools are a privacy risk
Most FinOps platforms require you to send your billing data and infrastructure metadata to their cloud. Your spend patterns, team structure, and resource names become their data.
Enterprise tooling, startup price shock
Comprehensive FinOps platforms are built for enterprises with dedicated FinOps teams. Startups and small engineering teams pay for complexity they do not need.
Built for engineers, not FinOps analysts
OpsLens puts cost intelligence directly in the hands of the people building and running your infrastructure — without requiring a dedicated FinOps team.
AI cost Q&A — with your own key
Ask "Which service drove the cost spike last Tuesday?" in plain English. OpsLens uses your OpenAI or Anthropic key to query your data directly — your prompts and cost context never touch our servers.
Your data never leaves your infra
Cloud cost exports, Kubernetes cost allocation, and Prometheus metrics are queried in-place with DuckDB. No ingestion pipeline, no third-party copy, no trust required.
Automated savings scanner
Scheduled scans surface idle resources, oversized instances, unused storage, and wasteful spend patterns across your cloud accounts, Kubernetes clusters, and on-prem infrastructure.
Community plugin ecosystem
Write a scanner plugin in TypeScript and publish it. Plugins work across AWS, GCP, Kubernetes, Datadog, and custom on-prem sources. Open API, no approval process, no revenue share.
Running in minutes, no data pipeline required
One Docker container, one data source, one API key. That is the entire setup.
Connect your billing data source
Point OpsLens at your cloud cost exports (AWS CUR, GCP BigQuery billing), Kubernetes cost metrics, or Prometheus data. OpsLens queries in-place using DuckDB — no copying, no ETL, no third-party ingestion. Your data stays in your infrastructure.
Drop in your own LLM API key
Add your OpenAI or Anthropic key to the environment config. OpsLens calls the API directly from your server — your cost data and conversation history are never routed through us or stored anywhere outside your infrastructure.
Ask questions, catch waste, extend with plugins
Chat with your cost data in plain English, browse the interactive dashboard, and let the savings scanner run on a schedule. Install community plugins for Kubernetes, Datadog, on-prem metrics, or write your own — all from the same UI.
We can not see your data.
By design.
Most FinOps SaaS tools require you to trust them with your most sensitive infrastructure data. OpsLens is architected so that trust is never required — because we never have access in the first place.
Your AWS data never leaves your infra
DuckDB queries CUR Parquet files in your own S3 bucket. No ingestion, no pipeline, no copy.
LLM calls go from your server to your key
We never proxy your OpenAI or Anthropic requests. Your prompts, cost context, and AI responses are entirely private.
MIT licensed, fully auditable
Every line of code is public. No hidden telemetry, no phone-home, no vendor lock-in. Fork it, extend it, run it forever.
Community plugins, not a closed marketplace
Write a scanner plugin in TypeScript and publish it. The plugin API is open — no approval process, no revenue share.
Help shape OpsLens
We are building in public with early adopters who have real infrastructure cost problems. Join the waitlist and get early access, direct influence on the roadmap, and a lifetime discount on the managed tier.