> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prado.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Prado vs. TEEs

Prado and Trusted Execution Environments (TEEs) address **different trust problems**.

They are complementary, not competing.

## \\

**What TEEs provide**

A Trusted Execution Environment (e.g. Intel SGX, AMD SEV) guarantees:

* Code executes in an isolated, hardware-protected environment
* The host OS or hypervisor cannot tamper with execution
* A remote party can attest **which binary was executed**

**TEEs answer:**

> *“Was this code executed inside a protected enclave?”*

TEEs are primarily used for:

* confidentiality
* private state
* protecting secrets

## **What TEEs do not provide**

TEEs do not give strong guarantees about:

* What **external data** was observed
* Completeness or correctness of network inputs
* Auditable evidence of HTTP or API responses
* Post-hoc inspection of decisions

External I/O (APIs, networks, data feeds) lies **outside the TEE trust boundary**.

## **What Prado provides**

Prado produces **verifiable execution evidence**. It records and commits:

* what data was observed
* what output was produced
* under which runtime and rules

Evidence can be verified later without trusting logs or operators.

**Prado answers:**

> *“What inputs were observed and what output was produced?”*

Prado focuses on:

* auditability
* accountability
* inspection after execution

## **What Prado does not provide**

Prado does not:

* protect execution from a malicious host
* provide confidentiality or secrecy
* claim correctness or reasoning
* rely on special hardware