Centralised logging
JSON logs across ingestion, workers, portal, command and security
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
Make GCCAP observable, recoverable and alertable before controlled paid pilot cutover.
P8 connects the productionisation path to monitoring, structured logs, backup plans, restore drills, health alert routing and disaster recovery controls. It prevents real telemetry, reports and clients from operating blind.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
ProvidersUptime, error tracking, metrics and logs
BackupsDB, evidence vault, config and audit
DRRunbooks, RPO/RTO and restore drills
Operational layer
P8 reliability controls
These controls turn GCCAP from a local release candidate into an operationally visible production system.
Backup jobs
Database, evidence vault, configuration and audit retention
Restore drills
Evidence that production data can be recovered
Health alerting
Gateway silence, queue failure, agent failure and backup failure routing
Decision clarity
Production blockers
GCCAP should not cut over real clients until these are satisfied.
Monitoring providerNot configured
Log sinkNot connected
Restore drillsNot run
Alert routesNot connected
DR runbooksNot approved