Environment separation
Local, staging, pilot and production are tracked as distinct operating modes with different risk and access posture.
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
The bridge from pilot file-backed product to production-grade GCCAP infrastructure.
Internal system phase creates the infrastructure control layer needed before GCCAP can safely connect real sensor/gateway feeds, onboard new clients, and operate toward global scale. It defines environment separation, deployment readiness, database migration discipline, object storage, queues, backups, observability, secrets, and production blockers.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
Environmentslocal + staging + production plan
Readiness gatessecrets + backup + monitoring + migration blockers
Commercial outcomesafer path to real clients and live telemetry
Operational layer
What Build 15 controls
The production foundation does not pretend the platform is cloud-ready today. It creates the control plane that decides when GCCAP is allowed to move from controlled pilot to production operation.
Deployment readiness
Each deployment target carries status, blockers, owner, rollback and validation requirements.
Secrets discipline
Admin, ingest, portal, webhook, database and storage secrets are tracked as requirements, not shipped in the ZIP.
Backup and recovery
Backup policies, restore targets and recovery drills become explicit production gates.
Operational layer
Why this matters before clients scale
Airline and caterer clients will not trust GCCAP if the platform cannot show how data is protected, backed up, monitored, migrated, and restored. Build 15 turns that into an operating register.
Managed data path
Prepares migration away from local files into managed database, object storage, queues and time-series infrastructure.
Observability
Defines health checks for website, intake, pipeline, portal, reports, alerts, command, agents, Watchdog and admin layers.
Production blockers
Stops premature go-live when HTTPS, secrets, backups, monitoring or migration readiness are missing.
Global runway
Creates the basis for Build 16+ infrastructure expansion and post-30 cloud hardening.