Skip to content

What is ZStrike?

ZStrike is an authorization platform. It moves permission logic out of your application code and into Cedar policies that are authored centrally, evaluated in milliseconds by a decision engine near your workloads, and recorded in a complete audit trail.

Permission checks written as if statements accumulate everywhere: controllers, middleware, database queries. They drift, they can’t be audited, and answering “who can access this?” means reading code. ZStrike replaces that with a single model:

  • Policies say who can do what, in Cedar — a policy language built for authorization, with formal verification behind it.
  • Your application asks one question at runtime: may this principal perform this action on this resource?
  • Every answer is recorded: the decision, and exactly which policy produced it.
  1. Model — define a schema for your domain (entity types, actions, attributes) and write Cedar policies against it. Policy validation catches mistakes before they reach production.
  2. Test — run authorization requests in the Console’s simulator, entirely in-browser, with expected results acting as pass/fail test cases.
  3. Enforce — attach your project to a Policy Decision Point and call POST /authorize from your application. Decisions are evaluated in-memory against continuously synced data.
  4. Audit — watch decisions stream live in the Console, query history by principal, resource, or policy, and archive events durably in open formats.
Component What it does
Console Web app for modeling, testing, and operating authorization — schemas, policies, entities, simulation, audit views, and team management.
Control Plane API The REST API and system of record behind everything: projects, policies, schemas, entities, tokens, and audit queries.
Policy Decision Point The runtime engine your applications call for allow/deny decisions.
Audit The pipeline that turns every decision into a streamable, queryable, archivable event.