CRUSBRO · SHANGHAI · AGENT-OS

crusbro agent-OS Agent Operating System | Controllable delivery · 600k hours in the field

Our foundational product. Business automation, drawing, vision, robot and freight agents are built on it—stable, auditable, replayable.

  • Assemble: roles, workflows, rules, permissions, data sources — configure and run.
  • Control: HITL, freeze‑before‑send, end‑to‑end traceability, replay and human takeover.

Governance

Delivery and governance

From solution design and system integration to production operations, the crusbro agent-OS brings workflows, permissions, data boundaries and human review into one delivery framework—so agents run reliably, every action is traceable and every result can be verified.

Built for production

We configure, integrate and validate each agent around real business workflows before a staged launch.

  • Acceptance criteria tied to business outcomes
  • Phased rollout with minimal disruption

Transparent and traceable

Critical tasks, tool calls and human decisions are logged end to end, making exceptions easier to locate and results easier to review.

  • Auditable, replayable execution
  • Human review and takeover controls

Secure, sustainable operations

On-prem, VPC and edge deployment options combine with configurable access and data policies for reliable long-term operations.

  • Configurable data boundaries and permissions
  • Monitoring, optimization and operational support

Technology ecosystem integration examples

  • AWS
  • OpenAI
  • Anthropic
  • Qwen
  • MiniMax
  • Kimi
  • GLM
  • Baidu AI Cloud
  • Volkswagen

Industrial delivery

Production needs controllable delivery, not buzzwords

Clear boundaries, clear accountability, calculable error cost. Agents run as controlled execution units—outputs align to system fields; actions are auditable and replayable.

Control plane

Write "what can be done" as a switch and "when can it be done" as a gate.

  • The Tool gate control table is on by default and can be turned off one by one in the background.
  • Freeze → Preview → Send only after approval
  • Single-step replay and manual takeover

Data plane

Align model output to system fields and enable source location.

  • Field → Element/Page Number/Attachment Index Link
  • Project dimension file merging and status view
  • Low confidence fields go into manual queue

Integration

Treat "access cost" as the first constraint, rather than a patch after going online.

  • OPC UA subscriptions and controlled writes
  • IMAP/SMTP monitoring, classification and distribution
  • Contractual interface with MES/ERP/booking gate API
Audit
Sessions, tool calls, and outgoing queues are associated according to business order numbers; frozen snapshots can be reviewed each time they are sent.
Latency
Visual acceptance by workstation: delay, missed detection and replacement cost; decoupling edge reasoning and central training.
Boundary
On-prem/edge split by environment; outbound policy can disable public LLM endpoints and keep local fallback only.

Chart

The risk falls from "semantics" to "interfaces"

Most field issues come from uncontrolled boundaries: outbound sends, writes, version drift. Gates + freeze + replay turn risk into signable acceptance items.

Failure modes
Turn problems into monitorable interface events
UNCONTROLLED → CONTROLLED Outbound content freeze+approve device write guarded write Version drift pin+rollback Field traceability lineage

Chart

Delivery is not a feature list, it is an acceptance matrix

The same set of "controllable" methods falls on three core technology stacks: agents (actions and audits), drawings (fields and lineage), and vision (delay and type change).

Acceptance matrix
Each line has a signable indicator caliber
LINE AUDIT LATENCY BOUNDARY agent drawing Vision interface rollback freeze queue tenant lineage batch on-prem trace SLO edge

Technology stacks

Three Core Technology Stacks

Stable technology foundations support a focused portfolio of products and solutions. Each stack can be accepted independently or combined for a complete workflow.

Agent · Design & Build

Agent Design & Build

Foundation: crusbro agent-OS · crusbro agent studio · robot / business automation / freight agents

InputMail/API/UA subscriptions; business documents, attachments and constraints.
ProcessStudio zero-code config for Tools/Skills/LLM/prompts; agent-OS runtime and Harness; high-risk steps to HITL.
OutputControlled writes and outbound queue; replayable evidence packs (input/output/version/accountability).
Failure and acceptance criteria
FailUnapproved outbound, session mix-up, missing rules → locate and fix by order-level replay.
AcceptFreeze snapshots match; approval gates enforceable; full audit trail per business order.

Industrial Drawing · Extraction

Industrial Drawing Agent

SCENE · 3D/2D DRAWINGS · PROCESS ROUTES · BOM

enter2D/3D drawings and CAD models: PDF / DWG / DXF / STEP / IGES / PRT and other mainstream formats, plus enterprise process standards and historical process cards.
deal withDrawing analysis → process-route generation → BOM validation → Excel/Word output → automatic drawing annotation; low-confidence results enter focused human review.
outputAuditable process routes, BOM and documents; field ↔ primitive/page/rule lineage; structured interfaces to PLM/MES/ERP.
Failure and acceptance criteria
failScan distortion, cross-page reference breaks, and symbol library inconsistencies.
acceptanceYou can click on the original image element for random inspection fields; you can align the field diff for change orders.

Inspection Agent · Device–Edge–Agent

Industrial Visual Inspection Agent

SCENE · AOI · Workstation re-inspection · End-edge agent collaboration

enterStation image streams, trigger signals, SKU metadata and inspection recipes.
ProcessPer-station camera, lighting, model and rules; defect/size/pose/assembly checks; low confidence to HITL and alerts.
outputVerdict + disposition + evidence (original, parameters, model version, rule); QMS / MES writeback and replay.
Failure and acceptance criteria
failLighting drift, model change is not synchronized, and categories are unbalanced.
acceptanceSign the time delay, missed inspection, and model change window according to the work station; do not write "one number for the whole factory".

Field notes

From the field

What actually changed on site in three real delivery projects.

Equipment manufacturing · Drawing and process unificationDrawing key elements are extracted automatically; the agent generates process routes and a BOM, then exports results to Excel, Word and auto-annotated drawings. Engineers shift from re-typing to confirming and correcting, and any disputed field links straight back to the original annotation.
Parts maker, East China · Industrial Drawing Agent
International freight · Email agentBooking and documentation emails are drafted by the agent and sent after a single human review; every message keeps a full processing trail, so customer queries can always be answered with evidence.
Freight forwarder · Freight Agent
Electronics manufacturing · Vision inspection Per-station camera, lighting, edge models and recipes are configured for the line; model switchover goes live the same night as changeover. Miss rate is tracked as an independent quality metric—standards clear, results verifiable.
Electronics assembly line · Industrial Visual Inspection Agent

Demo

Demo appointment

We will follow up shortly after you submit. You can also email us at service@crusbro.com.

Deploy

Deployment forms

Choose by network boundary and compliance. Common dimensions in contracts and acceptance:

FormConstraints
Private cloudTenant isolation, egress allow-list
On-premData stays on campus; offline update packs
EdgeSame segment as camera / PLC; latency in SLO
HybridTrain centrally, infer at edge; sync auditable