Provider register
Owns account, region, service and owner evidence for each external provider.
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 accessInternal GCCAP surface
Track provider accounts, managed service bindings, health evidence and production cutover blockers.
The lab is the internal operating surface for P19. It keeps staging and production blocked until real provider accounts, service bindings and readiness evidence are approved.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
APIs/api/provider-setup/*
PurposeExternal provider binding
StatusBlocked until provider evidence exists
Risk reducedUncontrolled cutover
Operational layer
Lab controls
Use these APIs to maintain provider binding readiness.
Managed services
Tracks database, storage and queue provider setup status.
Operational providers
Tracks monitoring, notification, billing and deployment provider setup.
Binding gates
Blocks production until health checks, secret references and rollback boundaries are verified.
Governance
Binding boundary
P19 stores setup evidence and references only; it does not store credentials.
- Use external secret references for all provider credentials.
- Run provider health checks in staging first.
- Keep manual invoicing fallback available for the first paid pilot.
- Do not enable production provider cutover without rollback evidence.