Have you tried out our ROI calculator yet?
Enter your Logs, Traces, and Metrics into the calculator below to see how much we can reduce your observability bill. grepr.ai/roi-calculator
We spent last week at #KubeCon in Salt Lake City. A few things we heard, over and over: Cost and telemetry noise came up first in nearly every conversation. Everyone is building an AI SRE, and the pitches are starting to blur together. And all of them start at the alert, which is already too late. grepr.ai/blog/kubecon-2026-t…
Grepr retweeted
Three things determine how good of an AI-powered software engineer you are:
1. How well you understand the customer and their problems.
2. How quickly you review code and invent abstractions abstractions/layers.
3. How quickly you can context switch.
Grepr retweeted
Seems like we're starting to see improvement per unit of R&D spend flatten. However, this field is still new, I expect a ton of low-cost improvements to layer on top and keep the growth up but still... Interesting to see with model cos going IPO what appetite looks like for continued R&D spend.
I don't know if this graph from @sebkrier is correct. But with any other tech trend ever it's exactly what you'd expect. The fact that some people anticipate something else this time is the aberration and warrants extensive scrutiny.
Grepr retweeted
Replying to @grepr_ai
@grepr_ai's new AI harness catches what other tools can’t.
In the demo, I flipped a flag to make half of all charges fail with a 503. Our “Shop SRE” agent caught it as something new, found the root cause down to the code, and opened a fix PR with a retry and backoff.
➡️ catch what no alert was built for, then act on it.
grepr.ai/blog/introducing-gr…
We’re at #KubeCon + #CloudNativeCon NA in Salt Lake City this week, booth 291.
We just launched Grepr AI, agents that catch what no alert was built for, and we’ll be demoing it live at the booth.
Come see it. See you there.
Watch demo here: youtube.com/watch?v=x2DtqJcs…
From a third of cloud spend toward 5 to 7%. Barry Carter, ex-7-Eleven CTO, on the observability math. Watch: youtu.be/gkPwxtZrrUw
7-Eleven’s #observability bill was about a third of their cloud spend when Barry Carter took over as CTO. He wanted it at 5 to 7%. Here’s how he thought about getting there.
Did you miss @jadtnaous's walkthrough of Grepr AI today? Here's the full recording youtu.be/x2DtqJcsu6U
Grepr retweeted
Join me at 10 AM PT today for my talk on Grepr AI. Register here:
watch.getcontrast.io/registe…
I will show agents Grepr built for its own environment, catching problems no alert was written for, and walk through exactly how one of them was built.
Grepr retweeted
All our customers @grepr_ai are building their own AI-powered workflows for reliability and security. Almost universally, they’re building tools to help with the investigation and incident-time remediation, after lagging indicators like SLOs detect the issue. The question we asked was can we avoid at least some of these incidents altogether by finding leading indicators?
30 days on our own prod: 17K investigations, 20 needed a human.
grepr.ai/blog/introducing-gr…
Grepr retweeted
Huge release from @grepr_ai 🔥 Most AI for ops shows up after the outage. Grepr AI catches failures before they happen, and only Grepr can do it, because the real-time telemetry engine is built in. Petabytes in, live patterns out, agents act on what's new. Congrats @jadtnaous and team!
grepr.ai/grepr-ai
Building a threat-hunter agent sounds simple: stream the logs, spot bad behavior, alert the SOC. In production it’s a mess. Seven hard lessons learned: grepr.ai/blog/lessons-buildi…
New white paper ➡️ Closing the Loop: Why Self-Healing Operations Need Better Detection
Download for free: grepr.ai/ai-sre-detection-gu…
“Why not just point Claude at our logs and have it hunt threats?”
Because the token bill is brutal, partitioned logs blow past the context window, and asked to connect the dots, an LLM will hallucinate a kill chain.
Filter first, then reason. New post: grepr.ai/blog/why-ai-insuffi…
Engineering leaders told Grepr founder and CEO Jad Naous they spend 5 to 20% of their infrastructure budget on observability, and it's buying less and less reliability.
Jad, a former a16z partner, joins a16z's Martin Casado to discuss whether AI can run production systems as well as it writes code.
Grepr sits in a company's log stream, can scan a petabyte of logs a day, cuts observability costs by about 90%, and is building AI agents that use those signals to troubleshoot production issues.
How AI is changing engineering at Jad's 10-person company:
- A data lake feature that once took one engineer about six months took Jad 10 days
- The gap between okay and great engineers on his team "just multiplied 10X"
- He runs 3-4 agent sessions at once, with a "tech lead" agent reviewing every PR
Why running live systems is a harder problem for AI:
- Jad: AI can almost tune databases, but can't yet keep servers running on its own
- Martin: every bit of code doubles the ways a program can behave, which is why humans still own systems
- The real world is messier than AI's training data, self-driving took 20 years and $170B
0:55 From Stanford to a16z to Grepr
7:00 Why observability spend stopped paying off
11:00 From autocomplete to AI that trains engineers
13:10 Why AI widens the engineer skill gap
14:55 Syntax vs semantics
18:00 Inside Jad's AI workflow
22:55 Six months of work in 10 days
24:50 Can AI reason about how systems really run?
30:10 Why AI SRE tools start in the wrong place
32:30 Can AI run a distributed cluster yet?
37:35 Why engineers buy extra capacity over predicting
39:15 How AI could trace failures in production
43:45 Why AI for ops is harder than for code
49:55 Can AI do a VC's job?
52:05 Why self-driving took 20 years and $170B
57:05 Customers skipped the AI pitch for the 90% savings
YouTube: youtu.be/blkIGLlZePg
@jadtnaous @grepr_ai @martin_casado
Live preview, Nov 4 at 10 am PT: Introducing Grepr AI, the harness for proactive operational agents.
Register: watch.getcontrast.io/registe…
Build your own agents in natural language. They run in real time in your telemetry stream and catch what no alert was written for. Live demo, your questions.
Point an LLM at all your logs and you’re looking at ~$234M a year at 10 TB/day. So nobody does it.
Grepr only sends the new log patterns to the model, so it investigates what’s changing for thousands a year.
grepr.ai/blog/ai-investigate…
#Grepr CEO @jadtnaous joined @a16z's @martin_casado on why #AI can write code but can't keep it running (yet).
Read the recap and watch the recording here: grepr.ai/blog/ai-sre-harder-…
#AI can write the code. Running it in production is a much tougher problem. I talked with @martin_casado at @a16z about why, and how we approach it at @grepr_ai. grepr.ai/blog/ai-sre-harder-…
76









