Operations

Your governance layer for every robot on-site — live permission decisions across your buildings, and a console to test any scenario.
connecting…
—
0
Permission Checks
0
Allowed
0
Denied
0
Needs Approval

Permission Console

POST /permission-check
Property
Robot
Action
Configure a scenario and run it.

Live Decision Feed

real-time
No decisions yet.

Sites

Add the buildings you own or manage. We verify ownership once, then you decide what robots can do there — in plain settings, no code.
Add a building
We verify ownership before it goes live — upload a utility bill, deed, or statement.

Approvals

Robots waiting on a human decision. Approve or deny — the robot polls until you answer.
No pending approvals.

Insights

How robots behave across your sites — decision mix, why requests are denied, where activity concentrates, and compliance at a glance.
0
Decisions
0%
Allow rate
0
Denied
0
Sent to approval

Why requests were denied

recent
No denials yet.

Activity by site

No activity yet.

Compliance snapshot

insurance & policy per site
SiteTypeInsuranceMin coverageRulesDefault

Fleet

Every robot cleared to operate across your sites, and how a robot resolves its GPS to a site before it acts.

The Robot's View

coordinates → property → policy

A robot doesn't know it's "at the hospital" — it knows its GPS. It streams coordinates to Ground API, which resolves the geofence to a property and returns the verdict. Off every registered fence, it's public space and GateOS imposes nothing.

Latitude
Longitude
Jump to a site
Enter coordinates (or jump to a site) and resolve.

Robot Fleet

coverage verified with the carrier — not the vendor's word
RobotCompanyClassInsuranceCoverage sourceStandingGround ScoreCredentials

Admin

GroundLabs super-admin — everyone who's signed up and platform-wide activity. Only you can see this.
0
Accounts
0
Robot Companies
0
Robots
0
Total Decisions

Ownership Reviews

—

Owners can't self-add a property — they submit proof (utility bill, deed, statement) and it lands here. Approve to create the space and grant it to their account; reject with a reason.

Accounts

—
EmailNameTypeRoleScopeKeysJoined

Developers

API keys live here — and only here. A robot company gets one universal key and embeds it in all its robots. Property owners never need a key.
How a robot company integrates
1
Register the company
One-time. Receive a secret key (shown once) — the company's single credential.
2
Enroll robots under that key
Every robot the company operates, worldwide.
3
Each robot calls the API
Authorization: Bearer <key> — the same key everywhere. GateOS checks it against whatever owner's rules apply at the robot's location.

This is the whole scaling model: one key per company, rules per space. No key per owner, no key per building.

Try the integration

register · enroll · call

Run a real robot-company onboarding against the live API. A company can act only as its own robots — the ownership boundary in action.

Step through a real integration → sign up → key → enroll → call the API as that company.

Team

Add the people who manage your robots — front desk, facilities, ops. They sign in to the GroundAssist help desk to answer robots that need a hand, scoped to the sites you choose. They can't change any policy or see the console.

Add a staff member

help desk access

Your staff

—
Loading…