> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/getting-started/about-rhino-federated-computing.md).

# About Rhino Federated Computing

General information about Rhino Federated Computing.

**Rhino Federated Computing** was founded with the vision of transforming how organizations collaborate with data. 

Rhino’s roots are in healthcare, where data are fragmented, heterogenous, and sensitive. This combination has historically made collaboration difficult, and has stunted the ability to improve health outcomes through data. 

Rhino is now changing that paradigm with the **Federated Computing Platform** (FCP).

* For more information Rhino Federated Computing and our work, check out the [Rhino Federated Computing Homepage](https://www.rhinofcp.com/).
* Take a look at our [Case Studies](https://www.rhinofcp.com/case-studies) as well as [White Papers and Publications](https://www.rhinofcp.com/publications) for examples on how our platform is being used.
* For compliance and control information, check out our [Trust Center](https://trust.rhinofcp.com/).

For more information, feel free to contact us at [support@rhinofcp.com](mailto:support@rhinohealth.com)


---

# 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.rhinofcp.com/getting-started/about-rhino-federated-computing.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.