u/Expert-Ear3883

Hey folks,

I'm a founder working on observability infrastructure aimed at FinServ, fintechs(including crypto and AI) , and data-heavy enterprises. We have a functional product and small private betas lined up. Before we go any wider, I want to hear from SREs and platform engineers running production observability in regulated industries, because our own pain isn't necessarily yours.

Quick context on where we're coming from. My CTO has 8 years at a top US bank running Splunk, Grafana, and Datadog pipelines at petabyte scale. Our third co-founder is an SRE lead with 15 years across F500s. I'm a Fortune 500 tech lead and personally sign off on our observability bill every quarter. So we are operators, not consultants showing up with a deck.

Honest takes I'd love on any of these:

• What is the single most frustrating thing about your current observability stack in 2026?
• Where does compliance or audit posture force tradeoffs you wish you didn't have to make? Data deletion to manage cost, retention compromises, data-residency constraints, anything else?
• What would you never give up about your current tooling and UI (Datadog, Splunk, Grafana, Elastic, whatever it is for you)?
• If a tool could meaningfully cut your observability bill but required migrating off something you currently use, would you do it? Where's your line?
• For regulated industries specifically, what does "audit-grade integrity" actually look like in practice? What do your auditors require?
• One feature you'd consider a "must have" before evaluating anything new, versus a "nice to have"?

Also: what's a question you wish vendors would ask before showing up to pitch you?

I will respond to every comment. Happy to share what we're building in DMs if anyone wants the detail, but I'm deliberately not posting links here because this is a question post, not a launch.

Thank you.

Hey folks,

I'm a founder working on observability infrastructure aimed at FinServ, fintechs(including crypto and AI) , and data-heavy enterprises. We have a functional product and small private betas lined up. Before we go any wider, I want to hear from SREs and platform engineers running production observability in regulated industries, because our own pain isn't necessarily yours.

Quick context on where we're coming from. My CTO has 8 years at a top US bank running Splunk, Grafana, and Datadog pipelines at petabyte scale. Our third co-founder is an SRE lead with 15 years across F500s. I'm a Fortune 500 tech lead and personally sign off on our observability bill every quarter. So we are operators, not consultants showing up with a deck.

Honest takes I'd love on any of these:

• What is the single most frustrating thing about your current observability stack in 2026?
• Where does compliance or audit posture force tradeoffs you wish you didn't have to make? Data deletion to manage cost, retention compromises, data-residency constraints, anything else?
• What would you never give up about your current tooling and UI (Datadog, Splunk, Grafana, Elastic, whatever it is for you)?
• If a tool could meaningfully cut your observability bill but required migrating off something you currently use, would you do it? Where's your line?
• For regulated industries specifically, what does "audit-grade integrity" actually look like in practice? What do your auditors require?
• One feature you'd consider a "must have" before evaluating anything new, versus a "nice to have"?

Also: what's a question you wish vendors would ask before showing up to pitch you?

I will respond to every comment. Happy to share what we're building in DMs if anyone wants the detail, but I'm deliberately not posting links here because this is a question post, not a launch.

Thank you.

Hey folks. Genuine ask, not a pitch.

I'm a founder working on observability infrastructure aimed at FinServ, fintechs(including crypto and AI) , and data-heavy enterprises. We have a functional product and small private betas lined up. Before we go any wider, I want to hear from SREs and platform engineers running production observability in regulated industries, because our own pain isn't necessarily yours.

Quick context on where we're coming from. My CTO has 8 years at a top US bank running Splunk, Grafana, and Datadog pipelines at petabyte scale. Our third co-founder is an SRE lead with 15 years across F500s. I'm a Fortune 500 tech lead and personally sign off on our observability bill every quarter. So we are operators, not consultants showing up with a deck.

Honest takes I'd love on any of these:

• What is the single most frustrating thing about your current observability stack in 2026?
• Where does compliance or audit posture force tradeoffs you wish you didn't have to make? Data deletion to manage cost, retention compromises, data-residency constraints, anything else?
• What would you never give up about your current tooling and UI (Datadog, Splunk, Grafana, Elastic, whatever it is for you)?
• If a tool could meaningfully cut your observability bill but required migrating off something you currently use, would you do it? Where's your line?
• For regulated industries specifically, what does "audit-grade integrity" actually look like in practice? What do your auditors require?
• One feature you'd consider a "must have" before evaluating anything new, versus a "nice to have"?

Also: what's a question you wish vendors would ask before showing up to pitch you?

I will respond to every comment. Happy to share what we're building in DMs if anyone wants the detail, but I'm deliberately not posting links here because this is a question post, not a launch.

Thank you.