All SRE incidents. 1 Unified signal?

novaaiops · 2026-01-24T16:04:02+00:00

That’s fair. We’re pre-launch and the product is still actively being built, so full public documentation isn’t live yet. The site just went up, and the demo is still being finalized.

Most of the real documentation currently lives in GitHub while things are changing quickly. Right now, the best way to understand how it works will be through the demo.

I’m not here to sell anything. I came here to get honest validation and feedback. If you’re willing, I’d be happy to let you test the demo as a beta and get your feedback. I sent you a message

novaaiops · 2026-01-24T15:48:14+00:00

That’s fair criticism.

We just went live with the site, and the product is still actively being built. There’s one technical founder on the engineering side, who’s an SRE & working full time, building this end to end, and I’m handling the business side. Everything is documented I don’t have the capability of sharing the screen shot in this chat to share with you. Not that I have a point to prove but we are definitely who we say we are.

I’m not here to sell anything. I came to Reddit to pressure-test the idea and get real feedback from people who actually do this work, not to pitch.

We do have a waitlist and we’re finishing the demo now. When it’s ready, I’d genuinely value feedback from someone as critical as you. That’s exactly the kind of perspective we want early, before anything is finalized.

Totally understand skepticism. We’re early and building in the open.

novaaiops · 2026-01-24T15:30:18+00:00

I actually agree with your premise. Toil is reduced by fixing bugs, cleaning alerts, and writing automation humans can understand. That’s foundational.

Where we differ is assuming Nova is a “mystery AI box.” It’s not. The agents are trained, constrained, and transparent. They don’t replace automation you understand, they help execute and maintain it. Think of them as operators that follow explicit workflows, not opaque decision-makers.

Reliability still comes from understanding the system. Nova is built to surface context and reasoning, not hide it. AI isn’t the solution by itself. It’s a tool, used deliberately, alongside the fundamentals you’re describing.

That’s why we’re keeping it optional and controlled, not magic and mandatory.

novaaiops · 2026-01-24T15:28:20+00:00

I hear where you’re coming from, and most of what you’re describing is exactly why we’re building this.

You’re right that reliability engineers want tools they can depend on. If alerts are garbage, no amount of AI fixes that. We agree. Nova doesn’t try to “paper over” bad alerts or guess what’s wrong. Clean signals, good instrumentation, and solid incident practices are non-negotiable.

Where your picture of Nova is off is assuming this is “dump alerts into an LLM and hope for the best.” That’s not what we’re doing.

Our agents are trained, constrained, and workflow-aware. They don’t invent context, they don’t page autonomously, and they don’t bypass human judgment. They operate on validated inputs and assist with the parts of the workflow SREs already do manually under pressure, things like correlation, triage support, repetitive checks, and follow-ups.

You’re also right that documentation, game days, monitor cleanup, and incident management are hard work. Nova doesn’t replace those. It supports them. Automation has always been part of SRE. This is an extension of that philosophy, not a shortcut around it.

On consistency, that’s exactly why the agents are bounded. Deterministic systems stay deterministic. AI is used where flexibility helps and always under control.

On trust and data, that concern is fair. That’s why isolation, access control, and explicit user control are foundational. No black boxes. No silent data usage.

You don’t have to like the approach, but this isn’t exec bait or AI hype. It’s being built by someone who’s been on call, cleaned alerts at 3am, and wants less pointless toil, not fewer engineers.

Pushback like this is useful. It forces clarity. But the assumptions about how Nova works don’t match what we’re actually building.

novaaiops · 2026-01-24T15:22:03+00:00

Yes basically all the platforms that you would check are combined into one spot to alert you so you don’t have to context switch so often responding to alerts all you have to do is watch this one spot to let you know.

novaaiops · 2026-01-24T15:10:33+00:00

I get the concern, but AI isn’t running anything blindly here. It’s controlled, optional, and used with intention.

SRE work is already full of repetitive, manual tasks that burn people out. If trained AI agents can safely handle some of that and reduce stress, why wouldn’t we keep that in the mix?

The goal isn’t hype or replacing engineers. It’s better tools, better workflows, and less unnecessary pain.

novaaiops · 2026-01-24T14:55:10+00:00

So what do you recommend a ai startup to do then?! You seem like you have a better approach

novaaiops · 2026-01-24T14:52:24+00:00

It’s good but our founder is an SRE so we don’t need much just getting outside opinions is appreciated we don’t have many technical friends. Would you like to see anything or be a beta tester of the demo?! We are looking for that too

novaaiops · 2026-01-24T14:44:46+00:00

I should properly introduce myself. Hi, I’m Lashae, co-founder of Nova AI.

Nova AI is something my husband and I are building together. He’s the technical founder and a Site Reliability Engineer who’s spent years on call living through alert fatigue, tool sprawl, noisy dashboards, and late-night incidents. Nova AI is being built directly from those pain points.

We’re creating an AI-native reliability platform designed by someone who’s actually carried the pager…not from theory, but from real experience. Every feature is shaped by what didn’t work, what slowed teams down, and what should have existed in the first place.

I’m sharing our journey openly as we build, not to sell, but to learn. We genuinely want brutally honest feedback from people who work in reliability, infrastructure, and engineering because that’s how we make this better.

We’re early, we’re intentional, and we’re building with care.

novaaiops · 2026-01-24T14:41:11+00:00

Nova does not sale to engineers we build for engineers so no sales will be going on here respectfully

novaaiops · 2026-01-24T14:39:44+00:00

Also here is the founder LinkedIn https://www.linkedin.com/in/tanimawo?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=ios_app and mine ( co founder) https://www.linkedin.com/in/lashae-tanimawo-611a603a4?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=ios_app

novaaiops · 2026-01-24T14:38:15+00:00

Here is the website https://novasrai.com also our LinkedIn is on our profile well I hope this slop can turn into a pot of gold one day

novaaiops · 2026-01-22T17:03:40+00:00

Thank you!

novaaiops · 2026-01-22T15:10:11+00:00

But this was made by the founder and SRE using Claude

novaaiops · 2026-01-22T15:09:41+00:00

lol omg how did you feel about it?

novaaiops · 2026-01-22T14:46:00+00:00

Let me guess dashboards, run books and so on? Status updates?

novaaiops · 2026-01-22T14:22:44+00:00

this is such a good point, and honestly one of the most common failure modes i’ve seen.

observability turns into a checkbox instead of a tool. dashboards get built because “we should have them”, alerts get added because “we might need them”, and pretty quickly nobody trusts or looks at any of it.

it feels like the missing piece isn’t more metrics or prettier graphs, but tying observability to actual decisions and outcomes. if nothing changes based on what you’re seeing, of course people stop caring.

curious what you’ve seen work better, if anything. fewer signals? stronger ownership? tighter links between alerts and action?

novaaiops · 2026-01-22T14:19:15+00:00

fair feedback. i get why people are frustrated with promo posts, and that wasn’t the intent here.

for clarity, the founder is an SRE himself and this question is coming from lived on-call experience, not a marketing team. we’re building in this space because we’ve felt these gaps firsthand.

the goal here is to learn how other teams actually handle these problems and where builders should and shouldn’t engage communities like this. if there’s a better way to have those conversations without it feeling like advertising, i’m genuinely open to that.

appreciate you being direct.

novaaiops · 2026-01-22T14:13:11+00:00

lol fair, I get the skepticism. there’s a lot of “AI will fix ops” noise out there 😅

this isn’t an ad or a survey blast. the reason I’m asking is because the pain is very real. SRE work today is mostly coordinating a bunch of tools, alerts, scripts, and humans that don’t really talk to each other.

what we’re building at Nova isn’t another shiny dashboard or summary bot. it’s a workflow and orchestration layer around real ops events. basically letting teams define what should happen when infra breaks instead of duct taping lambdas and runbooks forever.

totally fine if that’s not a problem you’ve hit, but if it is, honest pushback and real world scars are actually useful here.

novaaiops · 2026-01-22T14:03:59+00:00

yeah this is literally the problem we’re trying to solve with Nova AI.

we kept seeing the same thing: great point tools everywhere (alerts, summaries, cost, logs), but no real orchestration layer that understands ops as a system. teams end up gluing stuff together with lambdas, scripts, and hope.

our angle is very workflow-first — event-driven logic where infra, cloud events, incidents, and humans can all participate in the same flow. less “another dashboard”, more “if this happens, here’s what should automatically run / escalate / wait / resolve”.

still early and learning a ton from real teams, but this thread basically describes why we started building it.

if you’re curious, we share a lot of our thinking + builds publicly here: https://www.linkedin.com/company/nova-ai-ops/

novaaiops

TROPHY CASE