Hey Product Hunt 👋 Yuanlin here, founder of Zeabur and now building Nuphos.
Nuphos started from something we learned while building Zeabur.
We used to describe where Zeabur was going as “Your AI DevOps Engineer.”
But eventually we realized:
A PaaS asks you to adapt to its rules. A DevOps engineer adapts to your team’s infrastructure.
They learn the systems you already have, work within your permissions, and follow the way your team operates.
AI DevOps engineers should too.
Nuphos is an AI-native DevOps workspace that brings AI agents into the infrastructure your team already runs, without giving up control.
Our team of fewer than 10 engineers operates across 8+ clouds, 20+ Kubernetes clusters, and more than 10,000 hosts. We’d already been using coding and terminal agents in production, and they were surprisingly capable.
The hard part wasn’t getting an agent to run kubectl or inspect logs. It was everything around the action:
Whose permissions is it using?
What can it change?
Who approved it?
What exactly changed?
That’s what we built Nuphos around.
With Nuphos, you can connect your existing AWS, GCP, Kubernetes, and observability stack, keep agents read-only by default, require approval for write actions, and keep the context and audit trail shared with your team.
You can try it with your own infrastructure, or use the live demo on our homepage without signing up.
🎁 Use code PH100OFF to get your first month of Nuphos free.
👉 Got questions or want to follow what we’re building? Join our Discord: https://nuphos.ai/dc
And I’d love to hear from people running production:
What kind of experience would make an AI feel like a real DevOps engineer on your team, rather than just another AI agent?
Report
The point that running kubectl or inspecting logs was not the hard part really stood out to me. We already know agents can execute commands. The real challenge is whether a team can trust them in production. Permissions, approvals, and a clear record of what changed are what turn a capable agent into something an engineering team can actually work with. Congrats on launching!
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.
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.
Report
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?
Nuphos builds shared memory from past investigations, incidents, and the context your team gives it, so the next session doesn’t start from zero.
We also want it to learn team-specific runbooks and operational conventions over time, so it behaves less like a generic agent and more like someone who already knows how your team runs production.
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.
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!
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.
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".
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.
Replies
Nuphos
Hey Product Hunt 👋 Yuanlin here, founder of Zeabur and now building Nuphos.
Nuphos started from something we learned while building Zeabur.
We used to describe where Zeabur was going as “Your AI DevOps Engineer.”
But eventually we realized:
A PaaS asks you to adapt to its rules. A DevOps engineer adapts to your team’s infrastructure.
They learn the systems you already have, work within your permissions, and follow the way your team operates.
AI DevOps engineers should too.
Nuphos is an AI-native DevOps workspace that brings AI agents into the infrastructure your team already runs, without giving up control.
Our team of fewer than 10 engineers operates across 8+ clouds, 20+ Kubernetes clusters, and more than 10,000 hosts. We’d already been using coding and terminal agents in production, and they were surprisingly capable.
The hard part wasn’t getting an agent to run kubectl or inspect logs. It was everything around the action:
Whose permissions is it using?
What can it change?
Who approved it?
What exactly changed?
That’s what we built Nuphos around.
With Nuphos, you can connect your existing AWS, GCP, Kubernetes, and observability stack, keep agents read-only by default, require approval for write actions, and keep the context and audit trail shared with your team.
You can try it with your own infrastructure, or use the live demo on our homepage without signing up.
🎁 Use code PH100OFF to get your first month of Nuphos free.
👉 Got questions or want to follow what we’re building? Join our Discord: https://nuphos.ai/dc
And I’d love to hear from people running production:
What kind of experience would make an AI feel like a real DevOps engineer on your team, rather than just another AI agent?
The point that running kubectl or inspecting logs was not the hard part really stood out to me. We already know agents can execute commands. The real challenge is whether a team can trust them in production. Permissions, approvals, and a clear record of what changed are what turn a capable agent into something an engineering team can actually work with. Congrats on launching!
Nuphos
@sandy_liusy Exactly. Capability is only half the problem!
The harder part is making an agent a team can actually trust in production.
That’s why permissions, approvals, and a clear record of every action are such a big part of Nuphos.
Thanks for the thoughtful comment!
@yuaanlin Totally agree. You’re tackling the part that really matters for production teams. Excited to follow Nuphos!
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
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.
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?
Nuphos
@abby_mao1 Yes, that’s exactly the direction.
Nuphos builds shared memory from past investigations, incidents, and the context your team gives it, so the next session doesn’t start from zero.
We also want it to learn team-specific runbooks and operational conventions over time, so it behaves less like a generic agent and more like someone who already knows how your team runs production.
Nuphos
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.
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!
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.
Nuphos
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
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.