Every Harness user knows the moment. It's late. A CD pipeline is failing in a way you've never seen. A Feature Flag rollout isn't behaving the way it did in staging. A Chaos experiment surfaced something ugly right before a release, and you have thirty minutes to decide whether to ship. The docs get you 80% of the way there. The rest is a mix of tribal knowledge, hard-won intuition, and hoping someone somewhere has already solved this exact thing in their Harness setup.
Running a modern delivery platform is full of these moments. So is the work of adopting AI agents responsibly across your SDLC. The problems are getting harder, the Harness platform keeps expanding to meet them, and the people doing the work often figure it out alone.
We think that's worth changing. Today, we're launching the Harness Community, an open space where the people building, shipping, and operating software with Harness come together to work through the hard problems, share what they've learned, and shape where the platform goes next.
You can join us at community.harness.io.
Why we built this
Harness has always been more than a product. It's a growing group of practitioners who care deeply about how software gets delivered, and who have opinions about the tools they use to do it. That group has been having brilliant conversations for years — in support tickets, at {unscripted}, in customer Slack channels, over coffee at meetups. Great conversations, but scattered.
The Harness Community brings those conversations into one place, in the open, where any Harness user can learn from them.
It covers the full surface area of the Harness platform: CI, CD & GitOps, Feature Flags, Infrastructure as Code Management, Chaos Engineering, Internal Developer Portal, Cloud Cost Management, our AI DevOps Agents, and everything in between. Whether you're just spinning up your first pipeline or you've been running Harness at scale across hundreds of services for years, there is a seat for you here.
A discussion forum, not a ticket queue
We were intentional about what this space is, and what it isn't.
It isn't a replacement for Harness Support, and it isn't another Q&A board where questions get closed as duplicates and answers go stale. It's a discussion forum, built for the kind of conversation you'd have with a trusted colleague who happens to have solved the exact problem you're facing by using Harness.
That means threads have room to breathe. The interesting part is often the follow-up: "here's how we structured our stage templates," "this is the trigger pattern that finally worked for our monorepo," "we tried the same IaCM workflow and here's why we ended up doing it differently" — the context that turns an answer into an understanding. We care more about whether you leave with clarity than whether a thread gets marked resolved.
Who you'll meet here
You'll meet two kinds of people here, and one kind of helper that isn't a person at all.
First, the Harness team. Product engineers, solution architects, developer advocates, and support specialists who work on the platform every day. When you have a question about how a capability is meant to work, or how to push it further than the docs describe, they're here.
Second, the group we're most excited about: Harness customers, just like you. Highly technical practitioners running Harness in production, solving real problems at real scale, and generous enough to share what they've learned. Some of the best answers in any technical community come from someone who was in your exact situation six months ago and figured it out. This is where you'll find them.
Alongside them, you'll also see AI agents trained on the Harness developer documentation. They can surface the right docs, offer a starting point when no human has replied yet, and help unblock you at odd hours. They exist to support the humans in this community, not to speak for them. Human first, always.
Human first, AI as backup
Harness is an AI-native platform, and we use AI everywhere it genuinely helps our customers ship faster and more safely. But when it comes to community, we start from a clear principle: humans first, AI as backup.
The primary voices in every thread are real Harness practitioners sharing lived experience. AI shows up in supporting roles — surfacing related past discussions, keeping the space organized, and offering a starting point when no human has replied yet so you're not left waiting. When a response is AI-generated, we say so. You will always know who, or what, you are talking to.
The goal is a community that feels like a room full of thoughtful Harness engineers, with quiet automation handling the parts that machines do better than we do.
A home for the Harness open source family
A lot of what Harness is built on, and a lot of what we ship back to the ecosystem, is open source. That heritage matters to us, and the Harness Community reflects it.
You'll find dedicated space for the open source projects in the Harness family:
- Drone — the container-native CI engine that many of you first met Harness through
- OpenTofu — the open source infrastructure-as-code project Harness helped launch and continues to steward
- Harness Open Source — the self-hostable platform for source code management, pipelines, and artifact registries
- harness-cli — the command-line interface for managing Harness resources as code
- LitmusChaos — the CNCF chaos engineering project incubated at Harness
We'll keep adding more as our community continues to contribute to and steward projects across the ecosystem.
Whether you're self-hosting a Harness Open Source instance, filing your first pull request against Drone, running LitmusChaos experiments before a big release, or debugging an OpenTofu state late at night, this is a place to talk about that work. Contributors, maintainers, and users all sit at the same table.
Open source has always been a conversation. Someone writes code, someone else reads it, improves it, questions it, extends it. That conversation is what turns a project into a community, and a community into something that outlasts any single company or contributor. We want the Harness Community to honor that tradition: transparent, generous, welcoming to newcomers, and rigorous with each other when it matters.
How to get started
Joining takes less than a minute. Head to community.harness.io and sign in. Introduce yourself, tell us which Harness capabilities you're using, and what you'd love to learn or share.
From there, you can ask a question, start a discussion, share a pipeline pattern that worked for your team, post a Chaos experiment you wrote, or simply read and learn. All of those are valid ways to be part of this.
Come build with us
Communities are shaped by the people who show up early and set the tone. If you care about running Harness well, about contributing to the open source projects we all depend on, and about doing AI in the SDLC responsibly, we'd love to have you.
Join us at community.harness.io. Bring a question, a story, or an opinion. We're saving you a seat.
All this author’s posts
Dewan Ahmed is a Principal Developer Advocate at Harness, a company that aims to enable every software engineering team in the world to deliver code reliably, efficiently and quickly to their users. Before joining Harness, he worked at IBM, Red Hat, and Aiven as a developer and QA lead.
All this author’s posts
Ankit Kumar is a Senior Software Engineer on the Customer Experience Engineering team at Harness, where he works at the intersection of platform architecture and customer-facing delivery.
