Compute
Sandboxes, VMs, VPSs, workstations, and disposable CIQualify execution environments and make them available to workers without treating every machine as a one-off setup project.
Persistent execution fabric
Turn the compute and AI tools you already have into a persistent execution workforce.
Bring a VPS, workstation, cloud host, or existing execution environment. Connect the agents and providers you already use. ClawKraft coordinates work, preserves progress across worker changes, and governs how work is reviewed, accepted, merged, and deployed.
Persistent workers · isolated execution · durable handoffs · governed delivery
$ clawkraft commission host
✓ host qualified
$ clawkraft connect workforce
✓ workers registered
$ clawkraft run program
research → implementation → evidence
review → merge → deploy → verify
worker-1 disconnected
✓ checkpoint preserved
✓ worker-2 resumed
What ClawKraft gives you
An execution system, not just another place to run code.
Use ClawKraft as the layer that turns infrastructure, agents, credentials, project state, review, and deployment into one durable operating system for AI work. Keep the tools you already use; add the coordination and control that makes them work together.
Credentials
Vault-backed secrets and credential brokerageKeep credentials governed and scoped to the work that needs them instead of copying long-lived secrets into every worker environment.
Workforce
Persistent workers across providers and sessionsConnect coding agents, browser agents, native workers, long-running workers, and external agents through the same execution model.
Programs
Dependency-aware orchestration from objective to deliveryPreserve the roadmap, dependency frontier, acceptance gates, evidence, handoffs, and next available work as durable project state.
Recovery
Checkpoint and hand off work when a worker disappearsWorkers can change without forcing the project to restart from a transcript or reconstruct what happened manually.
Control
Mission Control for programs, workers, decisions, cost, and policySee what is running, what is blocked, what needs a decision, who can receive work, and what the next transition is.
Connectivity
MCP as a first-class attachment surfaceExternal agents can connect to ClawKraft rather than requiring every client to learn the private topology of your infrastructure.
Delivery
Evidence-bound review, merge, deployment, and verificationMove work forward when current proof says it is ready—not simply because an agent says it finished.
Product views
From onboarding to operating the workforce.
ClawKraft is designed to be usable as a product, not only as a CLI or a collection of backend primitives. The public onboarding path explains what happens next; authenticated Mission Control exposes the operational state and decisions that matter.
Onboarding
Start with the infrastructure and agents you already have, then move through setup, qualification, connection, and the authenticated operating surface.
Mission Control
Program progress, next transitions, worker/provider state, autonomy, blocking decisions, cost, authority, and audit history in one operational view.
What it does
Real project work, not loose prompts.
ClawKraft is an execution fabric that coordinates workers, infrastructure, source changes, proof, review, and delivery. It is designed so useful work can survive sessions, providers, process failures, and handoffs.
Persistent workers
Coordinate interactive agents, long-running goal workers, coding agents, browser agents, native workers, and external connected workers.
Isolated execution
Use worktrees, disposable CI, containers, databases, caches, persistent storage, warm environments, resource limits, and host-qualified isolation.
Durable handoffs
Assignments, checkpoints, receipts, leases, evidence, and review state remain durable so the next worker can continue instead of restarting from chat history.
Governed review
Carry changes through diff inspection, corrective work, tests, evidence, approval, and handoff before accepted state advances.
Governed deployment
Bind deployment to authorization, evidence, rollback behavior, production verification, and durable receipts.
Private workloads
Ship generic platform capabilities while keeping project-specific Programs, repositories, policies, credentials, and execution context private.
Where ClawKraft fits
Compute and sandboxes are part of the system—not the whole system.
Modal and Daytona solve important infrastructure problems. ClawKraft overlaps at the execution layer, then extends into durable workers, project orchestration, credential brokerage, human decision points, evidence, and delivery.
| Capability | ClawKraft | Modal | Daytona |
|---|---|---|---|
| Execution environments | Coordinates qualified sandboxes, disposable CI, containers, customer hosts, VMs, and other execution lanes as worker resources. | Cloud compute and secure isolated sandboxes with configurable CPU, memory, GPU, storage, networking, and secrets. | Sandbox infrastructure is the center of the product, including containers and first-class Linux/Windows VM sandboxes. |
| VM / host model | Bring your own VPS, workstation, or cloud host and commission it into the workforce alongside other execution providers. | Primarily a managed cloud execution and sandbox platform rather than a general customer-host commissioning layer. | Provides managed VM sandbox classes, snapshots, forks, pause/resume, and related environment lifecycle primitives. |
| Secrets / vaults | Credential brokerage is tied to worker identity, execution policy, project context, and auditable delivery paths. | Named secrets can be injected into functions and sandboxes as environment variables. | Organization secrets use opaque placeholders and outbound substitution, with host allowlists for scoped use. |
| Orchestration | Persistent workers, dependencies, leases, checkpoints, decisions, review, evidence, acceptance, merge, deployment, and recovery. | Orchestrates cloud functions, jobs, and sandbox compute; project/program governance is outside its core abstraction. | Orchestrates sandbox lifecycle and parallel environments; higher-level project/program governance is not the primary abstraction. |
| MCP | First-class control and attachment surface for external agents to discover and use governed ClawKraft capabilities. | MCP can run on Modal infrastructure, but it is not the central control abstraction of the platform. | Provides a dedicated MCP server for sandbox, filesystem, Git, process, computer-use, and preview operations. |
| Durability | Durability follows the work: assignment, checkpoint, evidence, acceptance, handoff, and recovery survive worker/session changes. | Durability is centered on managed compute objects, volumes, and sandbox state. | Durability is centered on sandbox persistence, snapshots, forks, volumes, and VM memory/filesystem capture. |
Short version: Modal gives agents elastic compute. Daytona gives agents composable computers. ClawKraft connects compute, computers, credentials, workers, project state, and delivery into one execution system.
Bring your own infrastructure
Bring a normal machine. Commission an execution host.
A customer should not have to manually wire every runner, credential, lifecycle path, browser, and CI environment over SSH. ClawKraft turns supported infrastructure into a qualified host that can participate in the workforce.
1. InfrastructureVPS, workstation, or cloud host you control.
2. SetupCommission and qualify execution capabilities.
3. WorkforceAttach compatible workers and providers.
4. ProgramsExecute dependency-aware work with durable state.
Mission Control
See the program. Control the workforce.
Mission Control exposes the state that matters without turning the browser into a second control plane.
Program selection, progress, next transition, cost, resources, decisions, and blocking findings
Guide me, Run within plan, and Full R2E autonomy envelopes
Pause, Resume, Stop, worker ON/OFF, Enable All, Disable All, and Hard Stop
Work graph, decision inbox, authority envelope, and audit timeline
Durable execution
Progress should survive worker failure.
Worker A starts
↓
checkpoint
↓
Worker A disappears
↓
Worker B resumes
↓
evidence → review → completion
The durable model preserves assignment state, worker identity, leases, generations, checkpoints, receipts, evidence, review state, handoff state, and recovery history.
Programs
Turn objectives into governed execution.
Programs preserve why work exists, what it depends on, what counts as complete, what evidence is required, and what downstream work becomes available next.
research / objective
↓
dependency-aware work
↓
workers
↓
evidence
↓
review
↓
accepted result
Use cases
Work that needs more than a single agent session.
ClawKraft is useful when the work has dependencies, multiple tools or workers, infrastructure requirements, failure modes, or a real delivery gate. The common thread is that progress needs to remain understandable and resumable after the current chat disappears.
Multi-agent product delivery
Let different workers research, implement, review, test, correct, and deploy parts of the same product without losing the dependency graph between them.
Research → execution
Turn research, whitepapers, unfinished concepts, and projected use cases into reconciled program state, prioritized work, acceptance gates, and execution.
Bring-your-own infrastructure
Commission a VPS, workstation, VM host, or other compatible machine into a governed execution fleet instead of hand-wiring a new runner each time.
Disposable execution for parallel work
Give workers isolated CI and execution environments so parallel tasks can prove themselves without fighting over one mutable shared box.
Attach external agents through MCP
Give compatible clients a stable governed interface to the execution system while keeping private infrastructure topology and credentials behind the control plane.
Resume after worker or provider failure
Preserve checkpoints, leases, receipts, evidence, and assignment state so another worker can continue when a session, process, or provider disappears.
Operate a mixed AI workforce
Keep coding agents, browser agents, native workers, and long-running workers visible and controllable from one program-aware operating surface.
Broker credentials to the work that needs them
Keep secrets managed through governed vault and credential paths instead of spreading raw credentials across prompts, shells, and worker-local config.
Govern deployment and production proof
Require current evidence, authorization, rollback behavior, production verification, and durable receipts before delivery is treated as complete.
Security & trust
Governed execution with a clear boundary.
Isolated execution, governed review and deployment, private workloads, and a hard split between the public product surface and operational control on clawkraft.dev.
Disposable execution
Parallel work should not fight over one shared CI box.
Execution environments can be commissioned, assigned, checkpointed, handed off, returned, refreshed, replaced, or discarded. Proof remains bound to the work that produced it.
Failure and recovery
Failure should become state, not mystery.
ClawKraft is designed to reconcile worker death, stale leases, provider loss, CI failure, branch divergence, review invalidation, merge races, deployment failure, rollback, and stale or superseded work.
Governed delivery
Execution is only part of the job.
ClawKraft carries work through a delivery path that separates producing a change from proving, reviewing, accepting, merging, and deploying it.
ExecuteWorker performs the bounded work.
Inspect + correctReview the diff and resolve findings.
Test + evidenceProduce current qualification and proof.
Approve + deliverMerge, deploy, verify, and preserve receipts.
Architecture
Clear surfaces. One authority.
The public website explains the product. Authenticated applications operate it. The private ClawKraft control plane remains authoritative for execution state and privileged actions.
clawkraft.com
↓
setup.clawkraft.dev
↓
app.clawkraft.dev ←→ review.clawkraft.dev
↓
ClawKraft control plane
↓
execution hosts + workers
External agents: https://mcp.clawkraft.dev/mcp
Get started