Nuphos

The AI-Native DevOps Workspace.

API

SaaS

Developer Tools

Visit WebsiteSee on Product HuntTwitter ⧉

This looks really exciting! One thing I’m curious about: how would you see Nuphos fitting into the workflow of a solo developer or a one-person team?

I build and experiment with multiple small products and AI projects, but I don’t necessarily have a large SaaS infrastructure or a dedicated DevOps team.

Would Nuphos still be useful at this stage? If so, what would be a good real-world use case for someone like me to start with?

Or is Nuphos currently more suited to larger teams that already have a fairly complex production infrastructure?

Would love to understand where a solo builder fits into the Nuphos vision.

We’ve been using @Nuphosas their design partner. This is pretty much how I want AI to work with our production infra. Congrats@yuaanlin

the read-only-by-default plus approval-for-writes model makes sense for trust. during an active incident when minutes matter, does that approval step ever become the bottleneck itself, or is there a break-glass path for that moment?

This feels like the right direction for AI in DevOps. Running commands is the easy part — understanding the infrastructure, permissions, past incidents, and how a team actually operates is much harder.

Really like the read-only-by-default + approval approach too. Agents touching prod need context and guardrails, not just more autonomy. Congrats on the launch!

This looks promising. I would be curious to see how Nuphos handles situations where the agent is unsure or finds conflicting signals. Knowing when to pause and ask a human could be just as important as knowing what action to take.

Congrats on the launch!

Really interesting to see agents operating directly against customer infrastructure.

How do you evaluate whether an agent will make the right infrastructure decision across scenarios it hasn’t encountered before, especially failures that would be expensive or risky to reproduce in a real cloud environment?

Love the idea of an AI agent that adapts to the team’s existing infrastructure. Congrats to the Nuphos team!

The point about running kubectl not being the hard part really resonated with me. Agents can already execute commands. The bigger challenge is making sure teams understand what they are doing and feel comfortable giving them access to production. Nuphos seems to be solving the right problem.

I worked on the agent experience in Nuphos. The hard part wasn’t getting an agent to propose a fix—it was designing the interface so operators can see the evidence, review a scoped plan, and hit stop the moment something doesn’t look right. In prod, trust is a UI/interaction problem as much as it is a model problem.

Part of the team here! One thing I really like about the permission admin design is how it makes the whole privilege escalation flow feel much safer. Instead of access changes being handled loosely or buried in chat, there’s a clearer approval path before anyone gets elevated permissions. That became a big part of how we thought about making admin workflows more trustworthy.

Team member here. My favorite part is actually not the AI—it’s finally having logs, cluster state, deployments, and the rest of the incident context in one place. The agent becomes a lot more useful once everyone is looking at the same thing.

I worked on the approval gate feature. There were a lot of internal debates around how much context to show, when to ask for approval, and what happens if someone interrupts halfway through. Would love feedback from people who deal with production systems every day.

This is a strong step toward practical AI-native DevOps. Giving agents real infrastructure context—while keeping humans in control of investigation and production actions—could save engineering teams a huge amount of time. Excited to see where Nuphos goes!

Really interesting approach. How does Nuphos learn the context of a team’s infrastructure over time? For example, can it pick up internal runbooks, past incidents, and team-specific operational conventions?

Been using early builds internally for a while, so today feels pretty special. It still makes mistakes (of course), but having it collect the clues before I jump into an incident has already saved me a lot of tab-hopping.

I’m one of the platform engineers building Nuphos, what concerns me the most is how each infra team adopt our product. I'd love to see the most brutal, realistic way on how every other SREs would use Nuphos. 🙂

Interrupt the agent mid-run, change direction, reject its plan, don't go easy on us. This is exactly how we dogfood and use Nuphos on our infra from day to day. We'd appreciate feedback, apart from just a simple "looks good".

Nuphos team here! 👋

My favorite part is the exact moment when monitoring FIREs, Nuphos agent starts investigating, and the context lands in our Slack channel. The agent gets to work automatically, with prod access under-watched, human approved. Being platform engineer myself, the collaborative workspace is what empowers me the most.

Coming from the marketing side of the team, I’ve been preparing for this launch for a long time.
I’ve watched Nuphos take shape through every piece of copy, every image, and every video we created.

The living runbook is probably the feature I’m most excited about. Too much valuable incident knowledge gets buried in Slack, only to be rediscovered at 2 a.m. months later.

So happy to finally see Nuphos live 🎉
Give it a try! We’d genuinely love to hear any feedback, especially what feels wrong or where it breaks.