4 docs tagged with "migration"

You already run Open Policy Agent (or a self-hosted OPA Control Plane pipeline) and want EnforceAuth as the enterprise control plane — without rewriting Rego or redeploying every PDP on day one.

EnforceAuth supports incremental migration from legacy Styra DAS™ deployments and Enterprise OPA (EOPA) fleets without forced re-architecture.

Moving to Policy as Code is not a single flip — it is a sequence of decisions about where policies live, how they reach runtimes, and how you prove enforcement. This page helps you pick a path before you wire EnforceAuth.

Zift finds authorization logic buried in application code and helps you extract it into Policy as Code — Rego for OPA (what EnforceAuth deploys today) or Cedar for AWS Verified Permissions and other Cedar engines.