HypothesisVery high confidenceCurrent
Microsoft-native and open self-hosted profiles shift operational and lock-in costs but should not change authorization, evidence or outcome invariants.
Use a shared conformance suite rather than feature parity claims.
Valid from2026-08-23
Last reviewed2026-08-23
Review again2026-11-21
Dataheart stanceexploring
Evidence for
Microsoft services impose capacity, run-duration, ownership and lifecycle constraints.
Microsoft — Fabric Activator limitations · learn.microsoft.com ↗Microsoft — Power Automate limits · learn.microsoft.com ↗Temporal — Self-hosted deployment guide · github.com ↗Self-hosted workflow infrastructure requires persistence, isolation, upgrades and schema operations.
Microsoft — Fabric Activator limitations · learn.microsoft.com ↗Microsoft — Power Automate limits · learn.microsoft.com ↗Temporal — Self-hosted deployment guide · github.com ↗Evidence against
Some profile-specific capabilities cannot be reproduced with identical economics or user experience.
Microsoft — Fabric Activator limitations · learn.microsoft.com ↗Microsoft — Power Automate limits · learn.microsoft.com ↗Temporal — Self-hosted deployment guide · github.com ↗How this claim can fall
Replace this placeholder during human review with an observable result that would materially weaken or falsify the claim.
A published claim remains useful only while it remains possible to prove it wrong.