Maple Proxy

Same tools, kept private

Maple Proxy is an OpenAI-compatible endpoint that runs on your own machine. It verifies Maple’s secure enclave and encrypts every request, so the clients you already use keep working.

Get the desktop app Read the guide

client.py

from openai import OpenAI client = OpenAI(-   base_url="https://api.openai.com/v1",+   base_url="http://127.0.0.1:8080/v1",  # Maple Proxy, on your machine    api_key=MAPLE_API_KEY,) stream = client.chat.completions.create(    model=model,  # any model the proxy lists    messages=[{"role": "user", "content": prompt}],    stream=True,)

Change the address and the key. The rest of your code stays as it is.

Chat completions

Streamed or in one response

Embeddings

For search and retrieval

Models

List what you can call

What it is

The private part, handled for you.

Talking to Maple privately takes two extra steps: checking that the server is the secure enclave it claims to be, and encrypting what you send. Most tools don’t know how to do either. Maple Proxy does both, and gives your tools the endpoint they already expect.

For tools on your own machine

Point a coding agent, an editor, or a script at the proxy. If it works with OpenAI’s chat, embeddings, or models endpoints, it can talk to Maple.

For developers shipping apps

Run the proxy next to your service and keep the OpenAI client library you already build with.

Open source

The proxy’s code is public. Read how it verifies the enclave and encrypts your requests, or build it yourself.

How a request moves

From your tool to Maple and back, in four steps.

Step 1

Your tool calls the proxy

It sends a normal OpenAI-style request, with your Maple API key, to the proxy on your machine.
Step 2

The proxy checks the enclave

Before anything is sent, it verifies Maple’s enclave attestation and agrees on encryption keys with it.
Step 3

The request leaves encrypted

Your prompt and your API key are sealed on your machine, then sent to the enclave.
Step 4

The answer comes back

The proxy decrypts the response and hands it to your tool, streamed or all at once.

Encryption starts at the proxy. The hop from your tool to the proxy is ordinary local traffic, which is why the proxy runs on a machine you control. See how Maple’s enclaves work.

Ways to run it