> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/about-kumu/what-is-kumu.md).

# What is Kumu?

Kumu is a powerful visualization platform for mapping systems and better understanding relationships. We blend systems thinking, stakeholder mapping, and social network analysis to help the world’s top influencers turn ideas into impact.

Kumu is a Hawaiian term for "teacher" or "source of wisdom." We're a remote team with roots in Oahu and Silicon Valley. Read more about our story on the [About Us](https://kumu.io/about) page.

## Who's using Kumu?

Kumu supports hundreds of organizations across the world to more effectively engage complex issues. Make sure to check out a few of our highlighted case studies:

* Humanity United: [Building a Better Brick Market in Nepal](https://kumu.io/stories/humanity-united-building-a-better-brick-market-in-nepal)
* Stanford ChangeLabs: [Launcing Large Scale Sustainable Transformations](https://kumu.io/stories/stanford-changelabs-launching-large-scale-sustainable-transformations)
* Hewlett Foundation: [Making Congress Work Again](https://kumu.io/stories/hewlett-foundation-making-congress-work-again)

## A tool AND a community

Kumu is more than just a tool. It's also a robust community of do-ers who are paving the way for how to create lasting impact. Don't miss the [manifesto](https://kumu.io/manifesto) and make sure to check out our curated team of expert consultants available to help on your next project by reaching out to <support@kumu.io>!

## This is Kumu

{% embed url="<https://player.vimeo.com/video/135341213>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kumu.io/about-kumu/what-is-kumu.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.