Compliance enforced in real-time,
not just on paper
Only approved pilots fly. Credentials and geofences are enforced automatically at the point of operation.
One operating picture,
no context switching
Live video, ADS-B traffic, weather, telemetry, and dock command unified in a single interface. No five screens, no fragmented tools.
Purpose-built for Australian BVLOS
CASA-verified airspace advisory, OzRunways EFB traffic integration, and Broad Area BVLOS Self-Assessment alignment, designed for how Australian operators fly.
Automatic records,
zero manual reconciliation
Every flight syncs back to CuroRPA, linked to the pilot, aircraft, operation and mission parameters. Always current, without anyone having to touch it.
HubX® and HubT® integrated, natively
CuroROC brings Sphere's Hub infrastructure into a single interface, combining dock command, 360° and PTZ site cameras, ADS-B traffic and real-time weather telemetry from on-Hub stations.
One ROC,
every site
Run remote and BVLOS operations across multiple sites from a single interface. Pilots in one place, drones across every site, with a shared operating picture and unified scheduling.
CuroRPA handles the governance and compliance layer. CuroROC handles live operations. CuroInsights with CuroAI handles data delivery, processing and detection. Together with HubX and HubT, they form a complete remote data capture solution.
Hardware and software designed and engineered in Australia by the Sphere team, built to work as one.
Built directly on CuroRPA, CuroROC enforces your compliance rules in real-time so your pilots have everything they need to fly safely, and your compliance record is always current and always complete.
Only pilots with a valid, open Operation in CuroRPA can fly in CuroROC. The approved operational area becomes the live geofence automatically, drawn directly from the CuroRPA Operation Assessment. There is no manual setup, no workarounds, and no gap between the approved plan and what happens in the air.
Full DJI Dock command and control through the DJI Cloud API integration. Remote pilots manage launch, mission execution, return-to-home, payload control and post-flight processing from a single interface, without switching tools.
Real-time ADS-B traffic in the same interface as the live operation, supplemented by OzRunways EFB community traffic data. Together they cover the low-altitude visibility gaps in remote environments where public ADS-B coverage is weakest, giving remote pilots traffic awareness GA pilots would recognise.
Airspace advisory is built on the same audited and approved CASA RPAS Platform integration as CuroRPA. Data is supplied directly from Airservices Australia and other official source providers, not a third-party generic dataset.
Plan and schedule recurring autonomous operations across one site or many, all from a single console. Schedule overnight inspection runs, recurring perimeter sweeps, or coordinated multi-site captures, and let CuroROC manage execution and enforcement.
CuroROC integrates natively with Sphere's HubX and HubT infrastructure, bringing dock command, site cameras, environmental telemetry and ADS-B into a single operating window.
Real-time wind speed, temperature, humidity and lightning data from on-Hub weather stations, surfaced directly in the operating interface. Go/no-go decisions are based on site-specific conditions, not the nearest regional forecast.
Live 360° and PTZ site camera feeds from HubX and HubT, with remotely controlled floodlights for low-light operations. Pilots maintain visual situational awareness of both the aircraft and the operating environment from anywhere in the country.
HubX and HubT infrastructure is controlled from the same interface as your DJI Dock deployments so there’s no separate tool or context switching. Take full command of your entire deployed footprint in one operating window.
CuroROC is the same platform Sphere's own operations run on, built by a team that holds a ReOC, a Broad Area BVLOS Approval and a ROC.
From approval to analytics, everything runs inside a single connected platform. Compliance is enforced automatically. Records link themselves. Your team focuses on the mission, not the admin.
Remote pilots submit flights and approvals are processed automatically against your operational rules, in line with CASA requirements. All in CuroRPA. No emails, no manual sign-offs.
Remote pilots only see what they're qualified to fly in CuroROC. Asset records and pilot credentials are linked automatically. If something is out of date, the system flags it before it becomes a risk.
Flights are commanded and monitored through CuroROC, integrated into the same ecosystem. Operational data flows back into the platform the moment the mission ends.
Every flight automatically links to the pilot, aircraft, procedure and approval it belongs to. Your compliance record builds itself, no manual data entry, no gaps.
Operational data surfaces directly in CuroInsights with no export or re-entry. Trends, utilisation and compliance metrics are always current, always accessible.
Traditional drone compliance management has work spread across email threads, spreadsheets and disconnected tools. Compliance depends on someone remembering to update the right file. Records are reconciled by hand, usually after the fact. Your team spends as much time managing the paperwork as managing the program.
Flight requests are submitted manually, usually via email or a form. Approval depends on someone being available and informed. Rules are assumed instead of being enforced.
Qualifications and maintenance logs are tracked manually, often by different people in different files. Keeping them current is a task in itself, and they're rarely in sync.
Execution software and compliance records exist in different systems with no connection between them. What happens in the field has to be manually reconciled with what's on paper.
Flight logs are filled out by hand, or manually uploaded at the office. The quality of your compliance record depends entirely on the discipline of whoever is holding the pen.
Any operational insight requires someone to pull data from multiple sources, clean it, and build a report by hand. By the time it's ready, it's already out of date.
CuroROC is the execution layer where approved operations become live flights. It sits on top of CuroRPA's governance foundation and feeds completed flight data downstream into CuroInsights, so every part of the chain is auditable, accurate and traceable back to source.
See the complete Curo suite and Hub infrastructure working together in practice.
Book a live 1-on-1 demo with our team and get a real-time look at how our Remote Operations Centre runs BVLOS drone operations: compliantly, efficiently, and at scale.
Our team works closely with yours to migrate your existing program into CuroROC, configure it to your operating context and have you audit-ready from day one. We work closely with your team to ensure the optimal solution is seamlessly implemented onto your site.
1
We get to know you, your assets, team, sites and needs.
2
We tailor your CuroROC instance to you, built for the way you operate.
3
We continuously support and improve your drone program as it evolves.
Best suited to operators standing up a new drone program, or those looking to replace a fragmented setup with a single, integrated and purpose-built system.
Best suited to operators who already have a compliance program in place and need a dedicated live operations platform to run remote and BVLOS flights on.
As the foundation layer of the Curo suite, CuroRPA is required for CuroROC
If you have the operational demand but not the in-house Remote Operations Centre capability to match, Sphere's team can bridge the gap.
Let our Sydney-based remote pilots use CuroROC fly your BVLOS operations for you: the same platform, the same team, contracted to your outcomes.
Get in touch with our team for a walkthrough of CuroRPA, scoped to your drone program.
