> For the complete documentation index, see [llms.txt](https://docs.switchboard.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.switchboard.xyz/how-it-works/switchboard-protocol/running-a-switchboard-oracle/hardware-tested-providers-and-setup.md).

# Hardware: tested providers and setup

Switchboard Oracles are designed to provide secure and reliable data within various hardware and provider environments.

The successful operation of these systems hinges on compatibility and performance across multiple platforms.

This section details the specific hardware and technologies that have been rigorously tested to meet these standards.\
**AMD SEV SNP** forms the backbone of the secure computing environments leveraged by Switchboard Oracles.

The following subsections will list the hardware providers and setup that we validated and tested to be working with Switchboard Oracles.

More will be added as we get to validate them first hand.


---

# 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.switchboard.xyz/how-it-works/switchboard-protocol/running-a-switchboard-oracle/hardware-tested-providers-and-setup.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.