@orman_canida Thank you! That’s one of the ideas at the core of Nuphos.
A real DevOps engineer learns how your team already works instead of asking you to rebuild everything around them. We think AI should work the same way.
@olliez1 Yes! The all-in-one DevOps workspace is free forever. If you want to add the AI agent, paid plans start at $29/month per workspace. You can start free and upgrade whenever you’re ready 😊
@olliez1 Yes! You can use it free as a team shared DevOps workspace. And also we have 1 month free for the Dev plan ($29/month) that you can try the AI features~
AI agents that understand your infrastructure and can investigate production issues is a powerful direction. The shared workspace angle makes this feel especially practical. Congrats on the launch!
@jocky Thank you! The shared workspace was really the starting point for us, we wanted the agent and the human to investigate from the same live context, rather than passing screenshots and log snippets back and forth. Really appreciate the support, and we’d love to hear your feedback if you give it a try! 🙌
@jocky Thank you! The shared workspace is a big part of how we think about Nuphos.
We want the agent to work with the same infrastructure context and operational knowledge as the rest of the team, instead of living in a separate chat window.
Adding a PM's angle to what the team's shared above: the part I keep coming back to internally is the shared context layer. So much DevOps knowledge normally lives in one person's head or one terminal session — when an incident hits, you're paying for that every time. What made Nuphos click for me was watching the agent's understanding of our infra become something the whole team could see and build on, not siloed. That shift from "individual knowledge" to "team context" is subtle but it's honestly the part I'm most excited to keep developing.
@vita1109 +1. This is the part I think people underestimate: the agent is useful, but the shared context is what makes it useful for a team. When an incident is unfolding, it’s not enough for one person or one terminal session to “know” what happened. The team needs the evidence, the current state, the plan, and the approval trail in the same place. That’s where Nuphos starts feeling less like a chatbot and more like an operational workspace.
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.
Report
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.
@carlvert On point! The guardrails and read-only access are the default mode (and our suggested way) for Nuphos agent. We believe that Trust is earned through approvals, and the human-in-the-loop process is a must! Think of it as an intern to your SRE team!
@carlvert Completely agree. We consider “knowing when to stop” part of agent correctness, not a failure mode. When signals conflict, Nuphos should surface the evidence and uncertainty, ask for clarification where needed, and avoid crossing from investigation into mutation without explicit approval.
@carlvert Absolutely. We think uncertainty should be a first-class state, not something the agent tries to hide.
If the evidence is conflicting or the agent doesn’t have enough confidence, it should surface what it knows, what’s unclear, and ask a human before taking the next step.
Knowing when not to act is a big part of being trustworthy in production.
@carlvert Absolutely. In Nuphos, uncertainty is a reason to pause, not to guess. If an action can’t be confidently classified as safe and read-only, the agent presents a plan and asks for human approval before proceeding.
@carlvert Absolutely, and we agree. In production, knowing when not to act is just as important as finding a likely fix.
Nuphos is read-only by default.
When signals conflict or the evidence isn’t strong enough, the agent should surface what it found, explain the uncertainty, and ask for human input rather than forcing a confident answer.
Any proposed change is shown as a plan and still requires approval before execution.
This is also an area we’re actively testing, so we’d love to hear about the messy edge cases you think we should try.❤️
Report
We use AWS significantly more than GCP, mainly to avoid the learning curve associated with GCP. This tool looks like it can help lower the learning curve for operating new platforms. Right?
@siningio Exactly! That’s one of the use cases we’re excited about.
Nuphos brings AWS, GCP, and Kubernetes into the same workspace, so the agent can help you understand unfamiliar resources, map dependencies, and plan changes or migrations using the context of your existing setup.
It won’t replace platform knowledge entirely, but it can make the first steps much less intimidating.
We’d love to hear how it works with your AWS-heavy stack!
One of the things we want Nuphos to do is reduce the operational learning curve when your stack expands into a platform your team knows less well.
Instead of learning every console and command from scratch, you can ask Nuphos to inspect the environment, explain what it’s seeing, and help you operate it using the context from your existing infrastructure.
Launch day! I worked on growth side, it’s fun watching Nuphos evolve. From “can we stop hogging across 10 tools for every incident?”, to something we now use in our own infrastructure, dogfooding every single day. Can't wait to see more devops engineer start using Nuphos, bringing more thoughts on the idea of AIOps!
Replies
Love the idea of an AI agent that adapts to the team’s existing infrastructure. Congrats to the Nuphos team!
Nuphos
@orman_canida Really appreciate this lovely shout‑out! We’re glad the vision resonates with you. Thanks for the support❤️
Nuphos
@orman_canida Thank you! That’s one of the ideas at the core of Nuphos.
A real DevOps engineer learns how your team already works instead of asking you to rebuild everything around them. We think AI should work the same way.
DeckSpeed
We’ve been using @Nuphosas their design partner. This is pretty much how I want AI to work with our production infra. Congrats@yuaanlin
Nuphos
@yuaanlin @miltonheyan Glad to hear this, Milton! Keen to have you onboard!
Nuphos
@miltonheyan Really appreciate you being one of our early design partners. A lot of Nuphos was shaped by real feedback from teams like yours.
Excited to keep building this with you 🙌
InsForge
agent devops is the way!!! i hate reading raw events
Nuphos
@tonychang430 Same here!!! Btw love InsForge!!!
Nuphos
@tonychang430 Haha exactly 😂
Raw events are useful, but nobody wants to spend their night stitching them together by hand.
That’s exactly the kind of work we want the agent to take over.
Tabbit AI
Congrats! Is it free?
Nuphos
@olliez1 Yes! The all-in-one DevOps workspace is free forever. If you want to add the AI agent, paid plans start at $29/month per workspace. You can start free and upgrade whenever you’re ready 😊
Full details here: nuphos.ai/pricing
Nuphos
@olliez1 Yes! You can use it free as a team shared DevOps workspace. And also we have 1 month free for the Dev plan ($29/month) that you can try the AI features~
Teable
AI agents that understand your infrastructure and can investigate production issues is a powerful direction. The shared workspace angle makes this feel especially practical. Congrats on the launch!
Nuphos
@jocky Thank you!
The shared workspace was really the starting point for us, we wanted the agent and the human to investigate from the same live context, rather than passing screenshots and log snippets back and forth.
Really appreciate the support, and we’d love to hear your feedback if you give it a try! 🙌
Nuphos
@jocky Thank you! The shared workspace is a big part of how we think about Nuphos.
We want the agent to work with the same infrastructure context and operational knowledge as the rest of the team, instead of living in a separate chat window.
Really appreciate the support!
Nuphos
Adding a PM's angle to what the team's shared above: the part I keep coming back to internally is the shared context layer. So much DevOps knowledge normally lives in one person's head or one terminal session — when an incident hits, you're paying for that every time. What made Nuphos click for me was watching the agent's understanding of our infra become something the whole team could see and build on, not siloed. That shift from "individual knowledge" to "team context" is subtle but it's honestly the part I'm most excited to keep developing.
Nuphos
@vita1109 +1. This is the part I think people underestimate: the agent is useful, but the shared context is what makes it useful for a team. When an incident is unfolding, it’s not enough for one person or one terminal session to “know” what happened. The team needs the evidence, the current state, the plan, and the approval trail in the same place. That’s where Nuphos starts feeling less like a chatbot and more like an operational workspace.
Nuphos
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.
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.
Nuphos
@carlvert On point! The guardrails and read-only access are the default mode (and our suggested way) for Nuphos agent. We believe that Trust is earned through approvals, and the human-in-the-loop process is a must! Think of it as an intern to your SRE team!
Nuphos
@carlvert Completely agree. We consider “knowing when to stop” part of agent correctness, not a failure mode. When signals conflict, Nuphos should surface the evidence and uncertainty, ask for clarification where needed, and avoid crossing from investigation into mutation without explicit approval.
Nuphos
@carlvert Absolutely. We think uncertainty should be a first-class state, not something the agent tries to hide.
If the evidence is conflicting or the agent doesn’t have enough confidence, it should surface what it knows, what’s unclear, and ask a human before taking the next step.
Knowing when not to act is a big part of being trustworthy in production.
Nuphos
@carlvert Absolutely. In Nuphos, uncertainty is a reason to pause, not to guess. If an action can’t be confidently classified as safe and read-only, the agent presents a plan and asks for human approval before proceeding.
Nuphos
@carlvert Absolutely, and we agree. In production, knowing when not to act is just as important as finding a likely fix.
Nuphos is read-only by default.
When signals conflict or the evidence isn’t strong enough, the agent should surface what it found, explain the uncertainty, and ask for human input rather than forcing a confident answer.
Any proposed change is shown as a plan and still requires approval before execution.
This is also an area we’re actively testing, so we’d love to hear about the messy edge cases you think we should try.❤️
We use AWS significantly more than GCP, mainly to avoid the learning curve associated with GCP. This tool looks like it can help lower the learning curve for operating new platforms. Right?
Nuphos
@siningio Exactly! That’s one of the use cases we’re excited about.
Nuphos brings AWS, GCP, and Kubernetes into the same workspace, so the agent can help you understand unfamiliar resources, map dependencies, and plan changes or migrations using the context of your existing setup.
It won’t replace platform knowledge entirely, but it can make the first steps much less intimidating.
We’d love to hear how it works with your AWS-heavy stack!
Nuphos
@siningio Yes, exactly.
One of the things we want Nuphos to do is reduce the operational learning curve when your stack expands into a platform your team knows less well.
Instead of learning every console and command from scratch, you can ask Nuphos to inspect the environment, explain what it’s seeing, and help you operate it using the context from your existing infrastructure.
Nuphos
Launch day! I worked on growth side, it’s fun watching Nuphos evolve. From “can we stop hogging across 10 tools for every incident?”, to something we now use in our own infrastructure, dogfooding every single day. Can't wait to see more devops engineer start using Nuphos, bringing more thoughts on the idea of AIOps!