Deterministic by construction
The same inputs and the same pinned profile version always produce the same output. No model, no heuristics, no hidden clock — evaluation dates are always explicit.
Compliance SDKs · Versioned rules · Deterministic
Regulatory logic your engineers can actually verify.
WardenKit builds deterministic, developer-installable SDKs for compliance and governance engineering work: versioned, effective-dated rule profiles, reproducible output, recorded provenance and explicit error states. Execution stays local wherever the requirement permits, and where hosted execution is necessary it is narrowly bounded and stated on the product's own page.
The WardenKit model
Versioned rules, preserved history, recorded provenance
- Where a product evaluates against published rules, those rules are versioned and effective-dated.
- Predecessor versions are preserved, so a past result can be reproduced exactly.
- Each version records the official source that defines it.
- Evaluation is anchored to an explicit as-of date, never to the system clock.
How WardenKit is built
Four commitments behind every SDK
Local execution where the requirement permits
WardenKit is SDK-first: where a requirement can be evaluated from data you already hold, it runs in your process with nothing to call. Where hosted execution is genuinely necessary, it is kept narrowly bounded and described on that product's own page.
Versioned, effective-dated rules
Where a product evaluates against published rules, each profile carries a version, an effective date and provenance pointing at the official source, and predecessor versions are preserved so past results stay reproducible. Each product states its own rule or data model on its own page.
Inspectable outputs
Every result is a reviewable, structured record: the profile version it was evaluated against, the as-of date, the inputs that mattered and an explicit, typed error state when something cannot be evaluated. Your team can read, log, diff and reproduce exactly what was decided and why.
Built for engineering teams
Compliance logic that behaves like the rest of your codebase
WardenKit products install as packages, evaluate as functions and return data you can test, review and keep. They slot into an existing codebase and pipeline without a portal, a dashboard or a new account system to run.
Reproducible in CI
Pin a profile version and an as-of date and the evaluation is a pure function of its inputs — it runs the same on a laptop, in a test suite and in production.
Clear decision inputs
Results name the rule version, the effective date and the data they relied on, so a reviewer can see the basis for an outcome without reverse-engineering the code.
Typed, not guessed
Unsupported or malformed input yields a typed error state rather than a best guess, and result types are discriminated unions your compiler can check.
Explicit per-product topology
Each product states its runtime, where processing runs and what — if anything — it transmits, so the integration and data boundary are known before you install.
Commercial terms
Try first, pay once you need production rights, cancel renewal anytime
Free evaluation
Start on the free evaluation tier: install the package and run it locally with no account, licence key or network call. Production rights are what a paid tier adds.
30-day initial paid guarantee
A 30-calendar-day initial-purchase refund guarantee applies once, from your organization's first paid transaction for a product. You do not have to show a defect or delete anything first.
Cancel renewal anytime
Cancelling stops renewal and keeps paid access to the end of the paid period. Nothing installed is remotely deleted or disabled, and evaluation use continues.
Full terms: Terms and Refund Policy. Paid tiers are listed on each product's own page.