Integration vs key custody

Restormel Keys does not take custody of raw provider secrets as a core product feature. This page clarifies the boundary: what Restormel stores, and what should live in your gateway/provider account or your own secret store.

What Restormel owns (v1 default)

  • Restormel control plane keys (Gateway/Restormel API keys) used to authenticate to Restormel APIs
  • Routes and policies that describe how requests should be handled
  • Health and analytics configuration for the control layer
  • Embeddable UX for model selection and optional BYOK flows

Where provider credentials should live (v1 default)

  • Gateway-backed: in OpenRouter / Vercel AI Gateway / Portkey (or your gateway vendor), with your app holding the gateway key in env/secrets manager
  • Builder-managed direct: in your env vars / secret manager, never pasted into Restormel-hosted infrastructure by default
Practical guidance — If a doc or UI flow implies “paste your OpenAI key into Restormel,” treat that as legacy. Use your own storage (env, secret manager, gateway vendor) and keep keys user-controlled.