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

# Platform Status & Roadmap

> What's available today, what's coming next, and what we're building toward: an honest accounting.

<Note>
  We change this documentation frequently to show the current state of the architecture.
</Note>

<Info>
  **Key point:** Prem API is available today with full end-to-end encryption, CPU + GPU attestation, and a complete AI capability set (chat, audio, vision, documents, search). The main gap at launch is **image reproducibility**. Image reproducibility lets you rebuild the Prem enclave image from source and verify that it is identical to the production image. This gap is the top priority on the roadmap. All other items in the lists below are available now.
</Info>

## What Is Available Today

### Encryption & Privacy

All features below are ready for production and available now.

| Feature                              | What It Means for You                                                                                                                                             |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| End-to-end encryption (post-quantum) | The SDK encrypts your data on your device. Only the sealed enclave decrypts the data. The encryption protects against current threats and future quantum threats. |
| Client-side key sovereignty          | You generate and hold the master key. Prem never has the master key and cannot decrypt your data.                                                                 |

### AI Capabilities

All standard AI features, with full encryption:

| Capability              | Details                                                          |
| ----------------------- | ---------------------------------------------------------------- |
| **Chat completions**    | OpenAI-compatible, streaming, tool calling, multi-step reasoning |
| **Audio transcription** | Whisper and Deepgram models                                      |
| **Audio translation**   | Audio to English                                                 |

### Attestation

Hardware-backed proof that the correct code runs on genuine hardware:

| Feature                                | What It Means for You                                                                        |
| -------------------------------------- | -------------------------------------------------------------------------------------------- |
| AMD SEV-SNP CPU attestation            | Verify that the enclave runs the expected code on genuine AMD hardware                       |
| Intel TDX CPU attestation              | The same verification for Intel-based deployments                                            |
| NVIDIA GPU attestation                 | Verify that GPU confidential computing is active on genuine NVIDIA Hopper/Blackwell hardware |
| Combined CPU + GPU attestation         | Verify the full processing pipeline, not only one component                                  |
| Multi-GPU attestation & load balancing | Attest and distribute inference across multiple GPUs with per-GPU verification               |
| Rust/WASM verification stack           | Memory-safe verification code that you can run in a browser. No server trust is necessary    |

### Platform & SDK

| Feature                | What It Means for You                                                             |
| ---------------------- | --------------------------------------------------------------------------------- |
| TypeScript SDK         | A full-featured client with automatic encryption. It operates like the OpenAI SDK |
| Local proxy server     | Use Prem API from any language (Python, Go, Java, etc.) with no code changes      |
| Organizations & teams  | Multi-org support with role-based permissions                                     |
| Scoped API keys        | Fine-grained permissions with IP restrictions                                     |
| Rate limiting (4-tier) | Fair usage across Free, Tier 1, Tier 2, and Tier 3                                |
| Usage-based billing    | Stripe integration with tier progression                                          |

## What Is Not Available at Launch

We tell you about the gaps clearly. Work on these features continues, but the features are **not ready at launch**.

### Image Reproducibility

<Warning>
  **Not available at launch.** This feature is the roadmap item with the highest priority.
</Warning>

**What it is:** Image reproducibility lets each person rebuild the exact enclave image from the published Prem source code. The person can then verify that the binary is identical, byte for byte, to the binary in production.

**Why it matters:** Today, attestation proves that the enclave runs a *specific* image (the fingerprint agrees with a published value). But you cannot verify that the published fingerprint agrees with the open-source code. You trust the Prem build process. Reproducible builds close this gap. You build the image yourself, compare the fingerprint, and verify the match independently.

**The current status:**

* The build infrastructure is ready (Packer-based, pinned base images, pinned driver versions)
* The build pipeline produces consistent images
* You **can** verify attestation fingerprints against the published Prem values
* You **cannot yet** reproduce the exact binary independently, because we did not remove all sources of non-determinism (timestamps, file order, package manager variance)

**The planned work:**

* Deterministic build tools that remove non-determinism
* Published step-by-step instructions for independent reproduction
* Automated tools for hash comparison
* CI/CD integration that publishes reproducibility proofs with every release

### Attestation Hardening

Incremental improvements to the attestation system. We release them continuously:

| Improvement                                | Why It Matters                                                                                              |
| ------------------------------------------ | ----------------------------------------------------------------------------------------------------------- |
| Certificate Revocation List (CRL) checking | Find automatically if an attestation signing key is revoked                                                 |
| Embedded root CAs                          | Include the manufacturer root certificates in the verification libraries. This removes runtime dependencies |
| Stricter TCB matching                      | Tighter validation of platform firmware and security versions                                               |
| Automated measurement verification         | Compare attestation fingerprints against published known-good values automatically with each release        |

## Roadmap

The list is in priority sequence. We release features when they are ready, not on set dates.

### Next Priority

<CardGroup cols={1}>
  <Card title="Reproducible Enclave Images" icon="clone">
    Deterministic builds with published instructions for independent verification. This completes the trust chain from source code → build → operational enclave. This is the most important gap for Prem to close.
  </Card>

  <Card title="Attestation Hardening" icon="shield-check">
    CRL checks, embedded root CAs, stricter TCB matching, and automated measurement verification. Incremental improvements that we release continuously.
  </Card>

  <Card title="Third-Party Security Audit" icon="magnifying-glass-chart">
    An independent audit of the platform is planned. We will publish the results here when the audit completes.
  </Card>
</CardGroup>

### Medium-Term

<CardGroup cols={1}>
  <Card title="Additional Self-Hosted Models" icon="brain">
    More model families on the Prem confidential infrastructure.
  </Card>

  <Card title="Enhanced Document Search" icon="magnifying-glass">
    Improved embedding models, better document chunking, and cross-document search.
  </Card>
</CardGroup>

### Longer-Term

<CardGroup cols={1}>
  <Card title="Native SDKs for More Languages" icon="code">
    Python, Go, and Rust SDKs with built-in encryption, in addition to the current local proxy method.
  </Card>

  <Card title="Verification Center" icon="display">
    A visual interface to examine attestation reports, see measurement history, and monitor enclave health. It makes verification accessible to non-specialists.
  </Card>

  <Card title="Enclave-to-Enclave Chaining" icon="link">
    Multi-hop confidential computing in which enclaves attest to each other. This permits complex confidential workflows across services.
  </Card>
</CardGroup>

## The Trust Progression

The Prem API trust model becomes stronger in stages. Each milestone decreases what you must accept without proof:

```mermaid theme={"system"}
flowchart TD
    A["Today: Attestation"]
    A -->|"proves"| B["The enclave runs specific code on genuine hardware"]

    C["Next: Reproducible Builds"]
    C -->|"proves"| D["That code matches the published source"]

    E["Then: Verification Center"]
    E -->|"makes"| F["Continuous verification accessible to everyone"]

    A --> C --> E

    style A fill:#22c55e,color:#fff
    style C fill:#f59e0b,color:#fff
    style E fill:#3b82f6,color:#fff
```

**Today**: Attestation proves that the enclave runs a specific, fingerprinted image on genuine hardware. You can verify the hardware signatures and confirm freshness. The gap: you trust that the published Prem fingerprints agree with the source code.

**Next**: Reproducible builds let you build the image yourself and compare the fingerprints. This closes the trust gap between the source code and the operational enclave. Then you trust only the hardware manufacturers and the laws of mathematics.

**Then**: A verification center makes continuous **monitoring** accessible to everyone. It supplies visual dashboards, alerts on fingerprint changes, transparency summaries, and historical audit trails. Each person in your organization can then check security verification, not only your security team.

<Note>
  This page shows the current state of the platform. We update the page when the platform changes. For questions about specific features or schedules, send an email to [support@premai.io](mailto:support@premai.io).
</Note>