Database cutover
Provider, DATABASE_URL reference, migrations and Timescale extension evidence.
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
Control managed database, evidence storage, queue, secrets, health checks and rollback before provider cutover.
The lab is the internal operating surface for P16. It keeps managed service provider readiness blocked until the required database, storage, queue, credential, staging, production and rollback evidence is retained.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
APIs/api/managed-services/*
PurposeProvider cutover
StatusBlocked until validated
Risk reducedLocal/file-backed dependency
Operational layer
Lab controls
Use these APIs to maintain provider cutover evidence.
Object storage
Evidence bucket, ACL tests, retention policy and versioning evidence.
Queue cutover
Queue provider, workers, retry, idempotency and DLQ monitoring evidence.
Rollback and credentials
Rollback readiness plus secret references without raw secrets in the ZIP.
Governance
Cutover rule
No production cutover until provider readiness is green.
- All production secrets must be external secret references only.
- Staging cutover must be rehearsed before production cutover.
- Provider health checks must run for database, storage, queue, auth and monitoring.
- Rollback must be approved before any live cutover.