Rules, programmable
Integrations
Library, not a service. Embedded in Broker, TrustGate, and your JVM app as a Maven dependency.
Policy Engine is library, not service. Every consumer embeds it directly. There's no HTTP endpoint to deploy, no cluster to run, no version to coordinate. Every caller gets deterministic, in-process evaluation.
Thoryn catalog composition
Policy Engine + Broker
Pattern: Broker embeds Policy Engine and calls it after trust-chain verification, before webhook delivery. Wallet profiles carry a policy_rule_id. DENY short-circuits the flow; the session is marked failed with the decision trace as the reason.
Policy Engine + TrustGate
Pattern: TrustGate optionally calls Policy Engine after Broker verification to decide whether to open the door. ALLOW triggers the unlock; DENY is logged anonymously.
Policy Engine + your JVM app
Pattern: Any Kotlin/Java app imports the Maven artifact and calls evaluate(rule, facts). Useful for authorisation decisions inside your own service — same rule engine, same shape, no service to operate.
Also on Policy Engine
Ready to turn policy into code?
Request access to see the library, the rule schema, and the evaluation fixtures.