PickaxeDriftstone sits above the runtime and centralizes customer access, rollout, spend controls, workspace continuity, and scoped auth across OpenClaw, Claude Agents, Hermes Agent, OpenCode, and Browserbase Agents.
Why this is hard
A single OpenClaw, Claude Agents, Hermes Agent, OpenCode, or Browserbase Agents demo is easy to love. The customer-facing harness layer is where the infrastructure work shows up: sandbox lifecycle, persisted installs, user-owned file state, version rollout, model-cost attribution, spend cutoffs, and secret plus auth flows that have nothing to do with the prompt itself.
Lifecycle control
Driftstone spins up the right sandbox for each user with the right packages, workspace, and scheduled work already connected, so launches stay fast and setup stays minimal.
Controlled rollout
Keep each user sandbox current while preserving the files and local state inside it. Driftstone gives your team a clear release path for updates, so improvements roll out cleanly without overwriting user work.
creator change
prompt.md + parser.ts
draft saved
snapshot
release/v14
snapshotted v14
apply
target sandboxes
idle
User sandboxes
Usage controls
Driftstone ties model usage, spend limits and runtime credentials to the right user sandbox so teams can show what was used, control costs as they happen and give each agent runtime only the access it needs.
Runtime access
Driftstone makes Mac runtime and home-network access part of the product, so teams can support harder workflows without building a separate stack.
Driftstone broker
mac mini
agent runtime
The runtime is only part of the job. Once customers are involved, you need separation, usage controls, runtime access, and rollout paths that keep the product usable without turning every launch into custom infrastructure work.
Keep each customer's usage, data, and access rules cleanly separated across environments.
Give users a real product surface with the right runtime, context, and controls already in place.
Bring Mac runtime and home-network access into the same platform when a workflow needs more than standard compute.
Turn one working runtime integration into a repeatable system your team can use again and again.
Pricing Plans
Starter
For small teams getting started with customer-facing agent deployments.
Team
For growing teams that need more capacity and control.
Enterprise
For organizations that need security, scale, and dedicated support.
Because a runtime demo and a customer product are different jobs. Once real users show up, you need access control, customer separation, secret handling, usage limits, rollout control, and a product surface people can actually log into and trust. The runtime can power the agent. Driftstone is the layer that makes it customer-deployable.
Agent harness review
Book a call to talk through your runtime stack and see how Driftstone fits around it.
