Transforms.
Automatic MSI/MST transformation for first-install.
On the roadmap — vote it up.
What's broken without it.
MSI packaging in 2026 is still a manual craft. First-install configuration — license keys, server URLs, feature flags — gets baked in via hand-authored MST transforms or post-install scripts that nobody owns. The result: a folder of brittle MSTs, a wiki page that goes stale, and a deployment that breaks every time a vendor reships.
The approach.
Attestree Transforms generates and signs MSTs from declarative policy. You describe what should be true after first-install — registry keys, services, permissions — and the control plane synthesizes a transform, attaches an attestation, and applies it during ingest. Vendor reships do not break your deployment.
Roadmap, in three moves.
Declarative MST DSL
Describe post-install state in YAML; the compiler emits a signed MST.
Vendor-reship resilience
Detect upstream MSI changes and regenerate transforms automatically.
Policy lint + dry-run
Catch conflicts and unintended changes before they ship to a single endpoint.
Ready for transforms on your fleet?
Get on the list — your vote moves this up the roadmap.