> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-cpf-integration-guide/v21/about.md).

# About

### Overview

This document provides the technical guidance required to deploy and use the Parallels RAS Custom Provider Framework. It consolidates the design, feature definitions, implementation guidance, and sample scripts into a single reference to help organizationso start using the Custom Provider Framework.

Parallels RAS Custom Provider is a framework that allows organizations to integrate hypervisors not currently supported as built-in Tier 1 providers in RAS. Using a script-based connector that acts as middleware, organizations can do the following:

* Onboard a custom provider.
* Enumerate virtual machines.
* Retrieve guest information.
* Perform supported power operations.
* Promote VMs to a RAS Template.
* Clone VMs.
* Perform Template versioning through Parallels RAS.

Custom Provider lets organizations integrate any hypervisor or cloud platform with Parallels RAS by supplying a script or executable that implements the Parallels RAS connector interface.

### Support

Parallels supports the Custom Provider framework and its integration with RAS. Hypervisor-specific scripts, provider-side logic, and any required third-party dependencies are customer-owned unless explicitly agreed otherwise. Sample scripts are provided as examples and accelerators, not as a Parallels-certified compatibility badge.


---

# 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.parallels.com/landing/ras-cpf-integration-guide/v21/about.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.