Internal GCCAP operating surface

This page is retained behind the public client website.

GCCAP does not delete operating records, trial packs, hardware activation surfaces or evidence automation layers. They are preserved for authorised client portal, command-centre and internal operating use while the public website stays clean for airline first impressions.

Open portal access

Internal GCCAP surface

Prepare every new client like a controlled aviation deployment.

The onboarding lab is the internal Internal system phase surface for managing client readiness before a pilot or rollout. It prevents GCCAP from connecting devices, exposing portal users or issuing reports before the client, site, devices, training, support and acceptance gates are ready.

Return to public platform Open portal access

StatusInternal / restricted surface. Not part of the public client walkthrough.

GCCAP

Sensor

Gateway

Evidence

Watchdog

Journey intelligenceRepresentative demo

AccessAdmin APIs

ControlsClient setup

ReadinessBlocked until go-live gates

UsePilot deployment

Operational layer

Onboarding lab controls

Use this page as the internal reference for Build 22. APIs are admin-gated under /api/onboarding.

Client intake

Tracks commercial, technical and operational ownership before pilot setup.

Site setup

Records facility maps, zones, geofences and gateway placement assumptions.

Pilot acceptance

Confirms payload, journey, rules, alerts, reports and portal acceptance.

Expansion review

Turns pilot evidence into a site or network rollout decision.

Decision clarity

Build 22 API surface

The onboarding APIs are built for internal control and later production implementation workflows.

StatsGET /api/onboarding/stats

Client intakeGET/POST /api/onboarding/client-intake

Site setupGET/POST /api/onboarding/site-setup

Device assignmentsGET/POST /api/onboarding/device-assignments

Go-liveGET/POST /api/onboarding/go-live

ReadinessGET/POST /api/onboarding/readiness