01
Workflow
Define the work once.
Versioned graphs make dependencies, branches, budgets, and human gates explicit before work starts.
Product
One control plane for the complete workflow.
Define remote work, keep it durable, control it while it runs, and review what happened from one connected system.
control plane / live map
durableLatchboxworkflow state
agentstoolsruntimespeopleA shared model
Technical structure that stays legible.
Scroll through the layers to see how Latchbox keeps intent, execution, live state, and evidence connected.
01
02
Run
Keep long work durable.
A run preserves state outside any one agent or sandbox, so work can pause, retry, resume, and replay.
03
Step
Give each action a boundary.
Each step declares its agent, model, tool, environment, inputs, permissions, limits, and approval policy.
04
Event
See what changes while it runs.
Structured events capture tool calls, messages, decisions, checkpoints, errors, costs, and operator actions.
05
Output
Finish with evidence.
Artifacts, tests, approvals, diffs, costs, and errors become one reviewable proof record.
Product surfaces
A complete workflow lifecycle, without a closed stack.
Use Latchbox as the operating layer while you keep your preferred agents, models, tools, and execution providers.
01
Latchbox Studio
Define work without losing technical detail.
Move between natural language, a visual graph, code, and YAML. Version, review, dry-run, and reuse workflow parts.
02
Latchbox Engine
Keep remote work durable.
Coordinate branches, dependencies, checkpoints, retries, timeouts, budgets, approvals, and recovery.
03
Latchbox Runtime
Execute behind an explicit boundary.
Prepare isolated environments, repositories, credentials, permissions, networks, and snapshots across runtime providers.
04
Latchbox Connectors
Bring the right systems into each step.
Give agents, tools, data, browsers, APIs, MCP servers, people, and external runtimes declared contracts.
05
Latchbox Control Room
See and steer the run in real time.
Inspect messages, tool calls, changes, tests, costs, retries, gates, and failures. Pause, approve, reject, retry, or replay.
06
Latchbox Proof Record
Make evidence part of the output.
Keep inputs, versions, tools, changes, tests, approvals, errors, cost, duration, outputs, and artifacts together.
Control Room
Intervene at the boundary, not after the damage.
A workflow can run for hours or days. Each step is an agent run that operators can inspect, pause, retry, replay, or reassign.
- The same agent instance can be reused across steps
- Rerun a completed step without losing its earlier evidence
- Loops are first-class workflow structure
- Elapsed and total time, tokens in, tokens out, and cost for every run
Plan → Implement ↔ QA → Pull Request
Agent runPlan · Planner A
Planner A turns the goal, constraints, and checks into a versioned plan.
- Elapsed
- 00:00
- Tokens in
- 0
- Tokens out
- 0
- Cost
- $0.000
Category view
Know which layer you are buying.
These categories solve different parts of remote work. Latchbox controls the workflow across them.
CategoryPrimary roleWorkflow boundary
Sandbox infrastructure
Provides isolated execution environments.
The team still coordinates the workflow, state, controls, and evidence.
Agent runtimes
Executes an agent and its tools.
The team still manages work across agents, systems, and human decisions.
General automation
Connects triggers and actions across tools.
It does not operate durable remote agent work as one controlled lifecycle.
Latchbox
Controls the complete remote workflow.
Design, runtime orchestration, live control, and proof stay connected.
Early access
Build the operating layer for your agent work.
Tell us what you want to run. We will keep you informed as early access opens.