User-owned state
Keep user files and local changes in place across updates.
What This Covers
Version Rollout for customer-facing OpenClaw deployments.
This section explains the product model, control points, and operating requirements behind this part of the customer-facing OpenClaw system.
Why This Matters
Updates need a release path as soon as customer sandboxes diverge.
A customer sandbox is not just a template once users start working inside it. Without a clear release path, every update risks overwriting files, creating confusion, or turning rollback into guesswork.
User files need to stay attached to the right sandbox.
Creator updates should move through a release path instead of live edits.
Rollback has to be normal, not improvised.
Release path
Move creator changes forward as explicit versions the team can inspect and control.
Architecture
Separate creator releases from user-owned sandbox state.
The rollout layer should package creator changes independently, target the right sandboxes, and apply updates without flattening the work the user owns.
Creator changes should be versioned before they reach customer sandboxes.
Rollout should support targeting, sequencing, and pause points.
Rollback should restore confidence without rebuilding environments by hand.
Version package
Capture creator changes as a release with history and clear ownership.
Targeted apply
Control which sandboxes receive an update and when they receive it.
Rollback path
Keep prior versions ready so the team can reverse a bad rollout quickly.
Operational Payoff
Teams can ship with confidence once rollout is explicit.
Clear release boundaries make upgrades easier to reason about, easier to support, and much safer to run at customer scale.
Rollouts become easier to inspect and explain.
Support can see what changed and where it landed.
The team can move faster without treating every update as a risk event.
Safer upgrades
Move forward without clobbering user-owned state.
Faster support
Version boundaries make incidents easier to trace and explain.
Bring your OpenClaw. We will talk through how Lodestone wraps the layer around it.
If your team already has OpenClaw logic working, the next conversation should be about sandbox persistence, version rollout, per-user metering, spend cutoffs, scoped secret injection, and what it takes to support real customers without turning the infra layer into a second company.
Sandbox persistence
Version rollout
Metering + cutoff
Secrets + auth
Book a Call
Tell us about the deployment.
Open the intake form to share your deployment context, current blockers, and what kind of conversation would be useful.