/api/infrastructure/stats
Current Build 15 readiness summary and blockers.
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
Check infrastructure readiness before GCCAP moves beyond pilot mode.
The infrastructure lab is the internal control surface for production readiness. It helps GCCAP avoid connecting real clients or live sensor gateways before environment, secret, backup, migration, monitoring and deployment gates are green.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
Readinessproduction blockers visible
Registersenvironments + deployments + backups + monitoring
Next buildmanaged database/storage/queue foundations
Operational layer
Lab surfaces
Use admin-gated API endpoints to inspect infrastructure readiness.
/api/infrastructure/environments
Environment register for local, staging, pilot and production.
/api/infrastructure/deployments
Deployment targets, status, validation, rollback and owner tracking.
/api/infrastructure/readiness
Production gate assessment before real external use.
Operational layer
Controlled boundary
Build 15 is intentionally a foundation, not the final managed cloud stack.
No secrets in ZIP
Secrets remain environment variables or future managed secret-store entries.
No fake production
The lab reports missing production dependencies rather than hiding them.
Pilot safe
Local file-backed state remains acceptable for controlled pilot development only.
Cloud path
Build 16 onward moves toward database, object storage, queue and deployment hardening.