Launching today
Nuphos
The AI-Native DevOps Workspace.
308 followers
The AI-Native DevOps Workspace.
308 followers
Nuphos gives engineering teams a shared environment where AI agents can learn your infrastructure, investigate issues, and operate production systems.
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?
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.
@yuaanlin Appreciate the thoughtful answer! Building on past investigations instead of starting fresh every time feels like a really important step toward making the agent part of the team. Best of luck with the launch!
Cloud World Model
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?
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.
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.
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?
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!