OSS vs Clasper Cloud

OSS vs Clasper Cloud

External Proof (defined term)

External Proof = evidence that can be verified by a party that does not trust the operator.

Clasper Core never generates External Proof.
Clasper Cloud is the only issuer of externally verifiable attestations.

Why it matters: auditors, regulators, and legal discovery.

---

The Boundary (Trust, not features)

OSS stops at single-tenant, self-attested governance.
Cloud begins at shared authority, shared trust, and external proof.

---

What Clasper Core Includes (OSS)

• Deterministic policy evaluation + decisioning (allow / deny / require_approval / pending)
• Capability request model + adapter contract
• Local execution adapters + local telemetry ingest
• Local trace store + local Ops Console (single operator)
• Local risk + cost primitives
• Local audit log and self-attested export bundles
• Local approvals — pending decisions resolved via Ops Console (self-attested)

OSS users should be able to say:
“I fully govern my agents — but only my agents.”

---

What Is Cloud-Only (Non-negotiable)

• Multi-tenant identity + org RBAC
• Human approvals with Cloud-issued decision tokens
• Evidence signing + attestation issuance (External Proof)
• Central policy distribution, promotion, and rollback with audit
• Fleet-wide dashboards, alerting, and compliance exports

---

Approvals: OSS vs Cloud

	OSS	Cloud
Pending decisions	Yes	Yes
Resolve approvals	Local (Ops Console)	Local or Cloud tokens
Trust status	Self-attested	Externally verifiable
Multi-approver	Single operator	Shared authority

OSS approvals are recorded and audited locally. They are self-attested — suitable for internal governance, not for third-party verification.

---

Upgrade Triggers

Move to Clasper Cloud when you need:

• more than one human approver
• multiple environments or teams
• compliance-grade retention and audit
• externally verifiable evidence

---

One-Sentence Rule

Open source Clasper governs execution you own.
Clasper Cloud governs execution you must answer for.