Products
Deterministic, developer-installable SDKs for compliance and governance engineering work. Released WardenKit products appear here with the technical and commercial information needed to evaluate them.
Generally available
Published packages that can be installed today. Where a paid tier exists, production entitlement can be obtained through that product's own page.
Open-source licence policy as code. Turn your licence policy into an enforceable build rule: validate SPDX licence evidence locally and fail CI when a component breaks your policy.
Evaluating a product
Each WardenKit product is documented the same way, so an engineering team can assess fit, integration effort, data boundary and commercial terms from one page before installing anything.
What the product evaluates, the exact checks it performs and the structured output it returns.
The npm package, supported runtimes and how the SDK is called from your code, with examples.
Where evaluation runs, whether any hosted component exists and what — if anything — the product transmits.
Plans, prices and the production rights each plan carries, including Production and Platform / Agency use.
Where the product evaluates against published rules: how profiles are versioned, effective-dated and sourced.
Quickstart, usage reference, error states, activation instructions and the support route for the product.
Product shape is set by the requirement, not by a house style: most WardenKit products are developer-installable SDKs evaluated locally, and where a requirement genuinely needs a hosted component it is stated plainly on that product's own page.