HUMΛN Cloud vs self-hosted: what changes and what does not
HUMΛN Team··11 min·Enterprise evaluators
Primary intent
Choose deployment before procurement deadlock — without treating “self-hosted” as a moral good or “cloud” as a toy.
What stays the same
- Workflow manifests and SDK contracts — Same protocol semantics.
- Governance model — Policy packs, approvals, and provenance concepts carry across modes.
- Marketplace bundles — Install mechanics are designed to inherit governance, not bypass it.
What changes
- Operational responsibility — Who patches, monitors, and backs up the estate.
- Data residency posture — Where bytes live vs how policy is enforced.
- Support and escalation — What the vendor runs vs what your team runs.
When to start hosted
When you need motion now and can accept vendor-operated boundaries — especially for teams proving value before a sovereignty program lands.
When self-hosted from day one
When regulatory or threat models require explicit control of the runtime environment — not as a vibe, but as a written constraint.
Deep reference
See also Field notes: hosted to self-hosted, same manifests for the migration story.