DroneHQ™
Calendar
System Status:
Checking DroneHQ notices and API status.
Updated just now Checking API

OPERATING LOCATION

Location

Current Location

Location not available

Allow browser location to calculate nearby aviation data.

Location has not been requested on this browser.

Saved Locations

No saved locations yet.

Allow browser to detect location Used for distance, preflight, weather, and nearby alerts.

WELCOME TO DRONEHQ

Allow location access?

DroneHQ uses your browser location to support aviation and mission features.

  • Weather, METAR, TFR, and airspace awareness
  • Nearby airport and distance calculations
  • Mission planning and preflight checks
DroneHQ does not continuously track your location. Your browser location remains separate from saved operating and mission locations.

DRONEHQ ADMIN

Verifying owner access...

Confirming that this account is authorized for the DroneHQ Owner Portal.

Return to My Dashboard
Back to System Overview

DRONEHQ ADMIN - OWNER ONLY

System Health

Monitor DroneHQ services, API boundaries, database dependencies, upload flow, incidents, maintenance windows, and operational readiness from one owner workspace.

System health overview

The live Crawler currently reports basic DroneHQ API status in the shared shell. This page will become the owner workspace for deeper service checks, dependency status, incident review, and maintenance planning.

System Health foundation is ready.

The route, owner access guard, shared shell, Crawler, tabs, and health-workspace layout are connected. Detailed service checks will appear only after the Admin health APIs are connected.

Awaiting API
Review Area Purpose Current State Next Connection
Services DroneHQ, API, Sync Agent, email, maps, and intelligence service readiness Awaiting API Admin service health checks
API Public API, internal admin endpoints, upload endpoints, and provider boundaries Foundation ready Endpoint health registry
Database Supabase/Postgres availability, migrations, storage buckets, and provider adapter status Planned Database dependency checks
Uploads Sync Agent upload sessions, pending queues, storage limits, and verification state Planned Upload-session visibility
Incidents Incident history, current impact, owner updates, and customer communication state Planned Incident records
Service Provider Status Last Check Impact Owner Notes Next Action
Service health records will appear here after the Admin service health API is connected.
Endpoint Group Purpose Current State Last Check Notes
DroneHQ API Core SaaS backend, authentication boundary, and system status foundation Foundation ready Shown in Crawler shell Detailed per-endpoint status should come from Admin health APIs.
Sync Agent API Pairing, heartbeat, upload sessions, evidence upload, and recovery visibility Planned Not connected here Should connect to device and upload-session records.
Admin API Owner-only system, account, subscription, support, and announcement administration Planned Not connected here Should remain owner-gated and audit logged.
Intelligence API Weather, TFR, NOTAM, airspace, and future mission intelligence endpoints Planned Not connected here Provider-specific details should stay behind DroneHQ-owned adapters.
Dependency Type Status Purpose Notes
Supabase Auth Identity provider Not checked here User sign-in and account sessions Provider status should be summarized without exposing secrets.
Postgres Database Not checked here Organizations, users, roles, evidence, uploads, and audit records Migration status should connect later.
Storage buckets Object storage Not checked here Sync Agent file uploads and preserved DJI records Upload limits and bucket availability should show here later.
Organization Device Session Source Status Protected Locally Cloud Verified Last Issue
Upload session health will appear here after Sync Agent upload-session visibility is connected.
Incident Impact Service Started Resolved Status Customer Notice Owner Notes
Incident history will appear here after incident records and announcement integration are connected.
Maintenance Area Purpose Current State Notes
Scheduled maintenance Planned service windows and customer-visible notices Planned Should connect to Announcements before customer release.
Provider maintenance Supabase, AWS, email, maps, AI, and intelligence provider advisories Planned Provider status should be summarized through DroneHQ-owned services.
Owner alerts Internal owner notifications for degraded services or failed checks Planned Should use the existing notices and Crawler foundation.
This owner workspace does not display fake uptime, fake incidents, or fake service metrics. Detailed service checks, upload health, dependency status, incident history, and maintenance windows will appear only after Admin System Health APIs are connected.