Robots
Fleet capacity. Owners offer their robots' free time together with their operators. Rental is how supply joins, not what the customer buys.
Platform
Customers buy the job, not the robot.
Cyberstrata turns a job description into a plan, a crew of robots and operators drawn from several fleet owners, and a proof of work. Renting a robot leaves the mapping, programming and supervision to the renter. We deliver the finished job instead.
Every job runs through the same six steps, and every step leaves a record.
The records are what the marketplace learns from: track records for robots, owners and operators, and saved plans for repeat jobs.
| Step | What happens | Who | Record it leaves |
|---|---|---|---|
| 1 Post a job | What, where, by when, and what counts as done | Customer | Job description and acceptance criteria |
| 2 Plan | Fit check: which robot types can physically do which parts. Logistics: robot counts, transport, elevator schedule, charging, supervision | Cyberstrata | Job plan and quote |
| 3 Source | Match fleets that are able, free in the window and nearby; each brings its own operators | Cyberstrata, fleet owners | Booked crew of robots and operators |
| 4 Run | Owners' operators run their own robots; Cyberstrata coordinates across fleets, around the clock | Operators, on-site lead | Robot logs and shift record |
| 5 Prove | Robot reports plus spot checks, compared with the acceptance criteria | Cyberstrata, customer | Acceptance record |
| 6 Pay and learn | Owners paid, commission kept, track records and the job plan updated | Cyberstrata | Track record and saved plan |
Services are the product and robots are the supply. Knowledge makes every repeat job faster.
The product
Services
Jobs done. The customer buys an outcome, such as floors cleaned by 06:00 with a coverage report.
The supply
The memory
Knowledge
Track records of robots, owners and operators, and saved job plans per building, so repeat jobs start from a proven plan.
The long term
Skills
Loading a new task onto a general-purpose robot quickly, so one machine can do events by day and cleaning by night.
A robot counts as supply only if it can do the work, is free in the window and can reach the site.
Matching is capability × time × place. Options that fail any gate are removed before anyone compares prices.
Gate 1 · capability
Able
Can this robot type physically do this part of the job?
Gate 2 · time
Free
Is it free in the job's window?
Gate 3 · place
Nearby
Can it be moved to the site and up the building in time?
Result
In the plan
Only robots that pass all three gates are priced and scheduled.
| Limit | What it means | Why it matters |
|---|---|---|
| Decisive for cleaning | ||
| Area per hour | How fast the robot works, m²/h | Sets how many robots a time window needs |
| Tool | Scrubbing deck, vacuum, window rig | Decides which parts of the job a robot can take |
| Environment | Floor type, stairs, wet areas, dust | Hard floors and carpets need different robots |
| Logistics | Transport, elevators, charging, maps of each floor | Often the real bottleneck: see the planner |
| People nearby | Who is in the space, and when | Sets the safety rules and the time window |
| Decisive for handling tasks such as palletising | ||
| Reach and payload | How far the tool gets; kg carried, gripper included | Rules out arms that cannot reach or lift the part |
| Joints | Degrees of freedom; with 6, most points at most angles | Decides which poses are possible |
| Precision | How exactly it repeats a position, mm | Decides assembly and machine tending |
Acceptance rests on the robots' own logs, checked on site, not on anyone's word.
Autonomous floor scrubbers already report a coverage map and the exact area cleaned after every run. We combine those reports with spot checks into one acceptance record per job.
| Field | Source | Format |
|---|---|---|
| Acceptance criteria | Customer, agreed in step 1 | What counts as clean, per area type |
| Area cleaned | Robot cleaning report | m², per floor and run |
| Coverage map | Robot cleaning report | Map per floor and run |
| Start and end | Robot logs | 2026-10-12 22:04:10 |
| Spot checks | On-site lead | Photos and checklist against the criteria |
| Deviations | Operators, robot logs | Missed areas, stops, incidents |
| Result | Customer and Cyberstrata | Accepted, rework or disputed |
Safety stays on the robot and with its operator. Nothing on the platform can override it.
- 01
Each robot's own safety functions decide whether it moves, stops or falls back. They never depend on the network, on a payment or on the state of a contract.
- 02
Each owner's operators run their own robots. The platform coordinates the crew; it does not take control of machines.
- 03
Infeasible or unsafe options are removed before prices are compared. A plan that cannot be done safely is never the cheapest plan.
- 04
What we learn from past jobs becomes a proposal, not a change. A person reviews it before it reaches any robot or plan template.
Customers get outcomes, fleet owners get revenue, and operators keep running the machines they know.
Customers
Facility managers, building owners, contractors
Describe the job and the deadline. No buying, no learning a robot. Contractors use us for overflow capacity on nights they cannot staff.
Supply
Fleet owners
Fill your robots' idle time. We bring qualified jobs, a plan, a contract and payment, and your track record grows with every accepted job.
On site
Operators
Run the robots you know. Nobody else has to learn them, and the plan tells every crew where to be and when.