Can I command a mixed fleet of drones, arms, and mobile bots from one interface?

The mixed-fleet problem

Drones, arms, and mobile bots have wildly different kinematics, telemetry, and tool sets. Trying to build one command interface by mashing their vendor SDKs together produces a brittle, bespoke console. The winning approach is abstraction: treat every unit as the same kind of thing and let the shared interface delegate to per-unit capabilities. bRRAIn's actor model does exactly this. Every robot in the fleet — regardless of form factor — is a Service/Agent actor registered through the Embedded SDK.

The actor model at the heart of it

In bRRAIn, an actor has a stable identity, a Workspace, a role, and a declared tool set. A drone's tools are fly-to, capture-image, and return-home. An arm's tools are pick, place, and inspect. A mobile bot's tools are navigate-to and pick-up-package. The GUI does not need to know any of that; it just lists actors and asks the platform which tools each one exposes. Command dispatch becomes uniform. The Auth Gateway ties every action back to the actor's identity for audit.

One API, many clients

bRRAIn exposes the fleet through a single API that serves a GUI client, a desktop sync client, and any custom tooling you build. An operator sees a consistent fleet view — filter by type, drill into a unit, dispatch a tool call — no matter how heterogeneous the underlying hardware is. The MCP Gateway brokers the tool calls that reach actual hardware, so the GUI talks policy and never talks motors directly. Adding a new robot type is a matter of registering its actor profile and tool set, not rewriting the interface.

The SDK does the hardware-specific heavy lifting

The per-hardware reality of drones versus arms is handled inside each robot's Embedded SDK integration. The SDK quickstart shows how to register an actor, declare tools, and wire them to the underlying firmware. The GUI stays generic because the SDK layer hides the specifics. Commission a new chassis by writing a small SDK adapter and the existing command interface already knows how to drive it. Fleet expansion becomes additive rather than disruptive.

Relevant bRRAIn products and services

• Embedded SDK — the actor registration and tool-declaration surface for any robot type.
• SDK quickstart — the seven-step path to a new actor appearing in the fleet GUI.
• Workspaces — scoped actor state that works identically for drones, arms, and mobile bots.
• MCP Gateway — the policy-aware broker for tool calls across mixed hardware.
• Auth Gateway — ties every command to the correct actor identity for audit.
• Book a demo — see a mixed fleet commanded from one GUI.