sweaver
📅 Joined in 2016
🔼 48 Karma
✍️ 19 posts
Load more
Show HN:
"Plural – Bringing AI to DevOps the way Cursor did for coding"
I’m Sam, co-founder of Plural (https://plural.sh/). Today we’re launching the next generation of our platform—an AI-powered experience for DevOps.
Our view is simple: what Cursor has done for software development, Plural is doing for DevOps.
DevOps teams are overwhelmed by:
- Kubernetes upgrades that break downstream workloads - Endless YAML diffs and drift - Reactive firefighting when incidents hit
Plural’s new release integrates AI directly into GitOps workflows, so platform teams can move faster and more safely:
- Autonomous upgrade assistant → orchestrates complex Kubernetes upgrades with guardrails
- AI-powered troubleshooting and Fix → leverage the resource graph from our GitOps engine to provide deep RAG into devops data, generating well-informed root cause analysis, and fixes PRs for a broad set of kubernetes and IaC issues
- Query Your Infrastructure with Natural Language - we will vectorize and index your devops information as they’re instantiated, giving a clean semantic understand of your entire estate which is useful for ad-hoc search and discovery and agentic workflows
- DevOps agents tuned to terraform and kubernetes - use all the information above to provide agentic workflows for modifying infrastructure managed via GitOps. Ask Plural to “double the size of my production database” and the combination of our semantic index and ability to do deep RAG against your infra and code will guide the AI to make the necessary change and issue a PR for you to review.
The future of DevOps isn’t more dashboards or more YAML. It’s AI-augmented workflows that multiply team productivity while keeping humans in the loop for control. GitOps is the ideal surface for that since it is fully auditable, easily composable with proven and rapidly improving capabilities around LLM coding, and provides a clean review-approval loop to ensure changes are performed safely.
We’d love feedback from the HN community on:
1. Where you’d want AI to take the toil out of your DevOps workflows
2. What would give you trust in AI systems operating in production
3. The biggest blockers you face managing Kubernetes at scale
Full launch post here with more technical details: https://www.plural.sh/blog/plural-now-with-ai-that-understan...
Excited to share this with you all — happy to dive deep on any part of the system.
— Sam, CEO/co-founder of Plural
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
I've seen cases where we started off as simply as possible with no k8's. We built the initial product really quickly using a ton of managed services. Whilst it was great to get us going, once we hit "growth" things just didn't scale. (1) The cost of cloud was getting astronomical for us (and growing with each new deployment) and (2) it was totally inflexible (whether that be wanting to deploy in a different cloud, or extend the platform's featureset) because we didn't own the underlying service.
We ended up porting everything to k8's. That was a long & arduous process but it gave us total flexibility at significant cost savings. The benefits were great, but not everyone has access to the engineers/skillset needed to be successful with k8's.
That's why we built Plural.sh – it takes the hard work out of k8's deployments. I've seen people go from zero to a full production deployment of a datastack on k8's in just 2 weeks. It deploys in your cloud, and you own the underlying infra and conf so you have total control of it. And because we believe in being open, you can eject your stack out of plural if you don't like it and keep everything running.
Great post, and hope all is well with you!
(Replying to PARENT post)