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 access

Internal GCCAP surface

Restricted GCCAP operating record retained behind the public website.

The Database Lab is the internal P2 control surface for schema groups, migration files, tenant constraints, file-backed import mappings, verification checks, migration packs and database readiness blockers.

Return to public platform Open portal access

StatusInternal / restricted surface. Not part of the public client walkthrough.

GCCAP

Sensor

Gateway

Evidence

Watchdog

Journey intelligenceRepresentative demo

ViewerAdmin APIs

PurposePost-30 database migration

BoundaryCutover blocked until configured

Operational layer

Lab controls

Use these controls to move toward a real managed PostgreSQL database safely.

Schema and migration inventory

Track table groups and SQL migration order.

Tenant controls

Keep client data boundaries explicit.

Import mapping

Map file-backed records into database tables and object-storage evidence.

Verification

Require proof before staging or production cutover.

Decision clarity

P2 API surface

The database APIs are admin-gated and designed for internal productionisation control.

StatsGET /api/database/stats

Schema groupsGET/POST /api/database/schema-groups

MigrationsGET/POST /api/database/migrations

Tenant constraintsGET/POST /api/database/tenant-constraints

Import mappingsGET/POST /api/database/import-mappings

VerificationGET/POST /api/database/verification-checks

Migration packsPOST /api/database/generate-migration-pack

ReadinessGET/POST /api/database/readiness