For developers

Compose the code. Compose the decision.

Use familiar programming tools to express business logic, combine policies with different responsibilities, and carry their execution across hosts.

Start with a policy

A policy specifies the action and resource it applies to, its effect, and a condition. The condition can use request data, business rules, and reusable functions.

TypeScript is the first authoring language. Its functions and tooling let teams express logic using concepts they already know, with additional authoring languages part of the direction.

// spending.ts
export function withinLimit(amount: number, limit: number) {
  return amount <= limit;
}

// expense.policy.ts
import { withinLimit } from './spending';

// Inside the policy condition:
withinLimit(request.amount, request.limit)

Expense and purchase policies can import the same helper. Functions, arrays, collections, and regular expressions let teams compose more than simple field comparisons.

Explore a complete policy

Combine policies into a decision

A policy set evaluates its policies together. An allow contributes a reason to permit the action; it does not bypass a denial or an enforce requirement.

Allow
Contribute a reason to allow the action when the condition matches.
Enforce
Require a condition to pass without granting approval. Every applicable requirement must pass.
Deny
Block the action when the condition matches.
Observe
Observe an evaluation without deciding access. The current authoring effect is MONITOR.
Escalate
A deny policy can specify an approval path and return an approval-required outcome.

That gives shared requirements their own home. A verification or spending policy can be combined with different allow policies rather than copied into each one.

Try cumulative enforcement

Author, explain, and audit

Expressive policies introduce complexity. Familiar tools, static analysis, and an organization-wide view help teams manage it.

AI-assisted authorship

Write policies with existing editors and AI coding tools, using shared functions to reuse known business logic. The authoring workflow can start with a business requirement and produce code that the team can inspect and test.

Plain-English analysis

Static analysis examines the source to describe the policy’s conditions and effects in plain English. Reviewers can connect the code to the business rule it expresses.

Organization-wide policy audits

Inspect policies together to surface which actions can happen, when they can happen, and what conditions apply. Follow a decision back to the policies that shape it and identify interactions across policy sets.

Authoring language and execution are different

Writing a policy in TypeScript does not make it dependent on a JavaScript application. The compiler translates the policy’s logic into executable WebAssembly ahead of time.

The host runs that compiled program without needing a JavaScript engine to execute the policy. The same execution implementation, including operations such as regular expressions,travels across hosts.

This gives security review a shared implementation to examine, rather than separate interpretations of the same rule in different host libraries.

Explore portable execution

Build an RBAC interface on top

An RBAC wrapper can associate a role name with policy sets and use a person’s role assignments to select those sets. Finance Manager becomes a familiar interface to policies with expressive conditions and business rules.

The policies evaluate the request. Role organization belongs to the wrapper, so teams can choose the interface that suits their application.

Explore the wrapper

Try the technology

Open the policy explorer · Compare approaches