Clasper Core

FAQ

Common questions about Clasper Core's architecture, open source model, and cloud offering.

Frequently Asked Questions

Is Clasper Core open source?
Yes. Clasper Core is open source and built for local, single-tenant governance of AI execution. Clasper Cloud adds shared authority, approvals, fleet views, and externally verifiable audit that require centralized trust and accountability.
Why do I need Clasper Cloud if there’s open source?
Open source is sufficient when you govern execution you own. Once multiple users, environments, or compliance needs are involved, you need centralized authority, shared approvals, and external proof — which is what Clasper Cloud provides.
Does Clasper Cloud run my agents for me?
Clasper Cloud can optionally run a stateless LLM execution runtime. It does not perform OS, browser, or data-side actions. Those always remain in your systems and are explicitly governed by policy. Clasper’s role is to decide whether execution is allowed — not to take control of your environment.
What data does Clasper Cloud see?
Clasper Cloud receives governance metadata and execution traces needed for approvals, audit, and fleet visibility. It does not require access to your source code, secrets, or customer data, and does not perform side-effecting actions in your environment.
When should I use open source versus Cloud?
Use open source for local, single-operator governance and experimentation. Use Cloud when you need shared authority, human approvals, compliance guarantees, or fleet-level governance across teams.