Who is responsible for what when robots do real work. The short version: you own and operate your robots; we are responsible for our software. The long version is below, in plain language.
The robots, the site, the mission, and every command issued. Operator credentials and consent grants belong to the fleet owner. Emergency stop is always in the owner's hands — never gated by anything in our platform.
Defects in the Swarmonic platform itself — coordination, safety-check, verification, and protocol software that fails to perform as documented. That comes with the territory, and it is why every release ships with a full regression and safety-invariant test suite.
Reckless, negligent, or unlawful operation: overriding safety refusals, commanding robots beyond their rated limits, operating without required permits or insurance, or deliberately misusing the fleet. What an owner chooses to do with their robots is on the owner.
Swarmonic is a coordination layer. It discovers, onboards, coordinates, and verifies robots the owner already controls, using each manufacturer's own owner-consent mechanism. Swarmonic does not manufacture robots, does not take ownership or physical custody of hardware, and acts only as the owner's software agent, within the owner's rights.
The fleet owner and its operators are solely responsible for how their robots are used. Swarmonic LLC is not liable for loss, damage, or injury arising from:
Where a defect in the Swarmonic platform itself — not the robot, not the operator — causes a failure, that responsibility is ours. We stand behind the platform with continuous adversarial testing, safety-invariant fuzzing, and a regression test for every defect ever found. Swarmonic maintains commercial insurance appropriate to deployments, and pilot programs run under written scopes with the site owner's insurer notified.
The platform keeps a signed, tamper-evident record of who commanded what, when, and why: command authorizations, named safety refusals, override and suppression records, and cryptographically hash-linked custody logs. In any dispute, the record shows whether an outcome traces to a platform defect or to an operator's decision. This is by design — clean attribution protects both sides.
No consent flow, permission tier, subscription state, or platform failure ever blocks an emergency stop. Protective device states block all commands. Every refusal names the check that produced it. These guarantees are enforced by automated tests on every release.
To the maximum extent permitted by law, Swarmonic LLC's aggregate liability is capped at the fees paid for the platform in the twelve months preceding the claim, and Swarmonic is not liable for indirect, incidental, or consequential damages. Nothing in these terms limits liability that cannot be limited under applicable law. The owner agrees to indemnify Swarmonic LLC against third-party claims arising from the owner's misuse described in §2.
The fleet shown at swarmonic.ai/demo is a simulation: the robots are simulated, the platform is not. No public demonstration commands physical hardware. Patent notices: eight U.S. patent applications filed July 30 – August 3, 2026 — these applications establish priority only.
These terms are governed by the laws of the Commonwealth of Pennsylvania. Deployments are governed by signed agreements that supersede this page where they conflict. We may update this page; material changes will be dated. This page is a plain-language statement of position, not legal advice. Last updated July 30, 2026.