Using Restormel with Portkey

If you use Portkey today, keep it as your provider access layer (gateway execution and vendor-managed credential handling). Use Restormel Keys as the control layer for policy-driven routing, explicit fallback chains, health checks, cost governance, and embeddable UX.

What stays where

• Portkey owns: gateway endpoint and Portkey-side routing/observability features you already rely on
• You own: where Portkey credentials/config live (env/secrets manager), your app call sites
• Restormel owns: routes/policies/health/analytics settings as a separate governance surface

Adoption path

1. Model your desired behavior in Restormel. Define routes and policies that reflect what you want to happen.
2. Resolve then execute via Portkey. Restormel decides; Portkey executes.
3. Use strangler rollout. Run old and new in parallel, shift traffic incrementally, verify, then retire old behavior.