Open-source Fallback

Permit OSS as fallback

Permit is not an open-core company, but many of its underlying components are open source. That gives you a fallback: you can migrate away from Permit, avoid vendor lock-in, and mix components into your own stack. This page explains how to leave Permit if you choose to. We hope you stay, and we want the choice to be yours.

Permit OSS foundations

Key open-source components in Permit:

• OPAL is a core part of Permit's control plane. It manages PDPs at scale by pushing policy and data updates to them in real time, event-driven.
• OPA is one of the policy engines that power Permit PDPs.
• Cedar-agent is the other policy engine option for Permit PDPs.
• The Permit SDKs, one per language, wrap the Permit API and send checks from your code to the policy engines.

Fallback Concept Guide

To migrate from Permit to a self-managed stack:

1. Use Permit's GitOps feature to sync the policies generated by the Policy Editor into your Git repository. You now have policy code that runs on your policy engine of choice, and you can edit it freely.
2. Set up your own control plane on OPAL to replace Permit's control plane.
3. Build PDP container images with the OPAL client and your policy engine of choice.
4. Write your own SDK, or use Permit's SDKs in passthrough mode, talking directly to the policy engines in your PDPs.
5. (Optional) Build the back-office and customer-facing interfaces you need on top, as an API or UI.