Lens sits between your infrastructure and any observability backend. It scores every log, routes what matters, and drops the noise — before it hits your bill. Most teams save 40–70% in the first week.
Health checks, debug traces, successful 200s, routine cron jobs — all getting indexed and charged at the same rate as your critical errors.
Most observability backends charge by volume — the same rate for a critical error as for a /healthz 200 OK. Volume is your enemy.
Manually configuring Fluent Bit transforms or Vector filters for each service takes weeks and breaks every time someone adds a new log format.
Every new service, every debug statement left in production — they all compound. Without a filter layer, costs scale with your success.
Lens is a lightweight agent that runs alongside your existing log shippers. No code changes, no backend reconfiguration, no downtime.
One command deploys the Lens agent on any Linux host, Docker container, or Kubernetes cluster. It starts listening for logs immediately.
Use the visual editor to define rules, or hit ✨ AI Suggest and Claude analyses your live log schema to recommend the highest-impact rules instantly.
The dashboard tracks every filtered log and converts it to dollars saved in real time. See exactly which pipelines and agents are generating savings.
Lens gives you fine-grained control over your log pipeline — with AI that does the heavy lifting so you don't have to start from scratch.
Click one button and Claude analyses your live log schema to suggest the highest-impact filtering rules — which fields to drop, which patterns signal noise, and the estimated cost reduction for each.
Every log gets a score (0–100) based on your rules. High scores route to your destination; low scores get archived or dropped. No binary yes/no filtering.
Build complex routing logic with a drag-friendly editor. No YAML, no Lua scripts, no rebuilding Fluent Bit configs when something changes.
Route high-score logs to Datadog, Splunk, or any endpoint — mid-score to S3 or Elasticsearch, drop the rest. One pipeline, multiple outputs, zero duplication.
OTLP, Kubernetes, Syslog, CloudWatch, HTTP, and Windows Event Log — Lens speaks every log format your infrastructure produces.
See exactly how much each pipeline, agent, and rule is saving you — converted to dollars, updated live. Share the number with your CFO.
Assign different pipelines to different agents. Strict filters for staging, detailed capture for production — managed from one dashboard.
The agent runs entirely inside your network. Log content never touches Lens servers — only anonymous counters (bytes filtered, logs dropped) are sent to the dashboard.
Lens processes logs inside your infrastructure. No data is sent to Lens servers — only anonymous usage metrics (bytes processed, logs dropped). Your log content goes directly from your servers to your chosen destinations.
Install it on any Linux host, Docker container, or Kubernetes pod. It runs as a local process — nothing is proxied through Lens servers.
After filtering, logs are forwarded directly to Datadog, Splunk, S3, or any endpoint you configure. Lens never sees the payload.
The dashboard shows bytes processed and logs dropped — raw counts, no content. Compliant with HIPAA, SOC 2, and GDPR by architecture.
Pipeline configuration is pulled from the dashboard to the agent — not the other way around. Your rules, your network, your data.
Adjust your current bill — savings update instantly.
Lens takes a share of the savings it generates. If you don't save, you don't pay.
Savings are estimated from log volume reduced × your backend's published per-GB ingest price. · Billed monthly. Cancel anytime.
Start filtering in under 5 minutes. No credit card required.