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

# Why Cambrian?

Building NCNs traditionally requires extensive development time, deep technical expertise, and complex infrastructure management. Developers need to implement consensus mechanisms, establish secure communication channels, and manage distributed storage—all while ensuring robust security and reliability. Cambrian SDK addresses these challenges by providing:

* Battle-tested Building Blocks: Pre-built modules for consensus, gossip protocol, and storage&#x20;
* Streamlined Development: Reduce development time from months to days
* Developer-First Experience: Focus on your core logic instead of infrastructure complexity
* End-to-End Toolkit: From local testing to mainnet deployment


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cambrian.one/introduction/why-cambrian.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
