What VESPA is
APEX VESPA is the sovereign cockpit app and extensible sandbox surface: sovereign use of VPS extensible cloud services, vendor-agnostic LLM use, always cross-platform. It is distinct from VESPER: VESPER is the internal infrastructure and governance truth-ledger that VESPA reads as a backend. VESPA never claims to be VESPER.
Capabilities (v1, from canon spec)
- Web Search and Browsing
- Code Interpreter and Data Analysis
- Generative AI (Text, Image, Video, Multimodal)
- Applications, Canvas, Connectors
- File Upload and Document Analysis
- Non-destructive middleware for license (shell) scaling
- Enterprise hyperscale operational readiness
- Self-healing, versioning, and rollback
- Model-agnostic usage (all models supported)
- User-selected model preference
- No forced tokenization; metering included
Model selection (model-agnostic, no forced tokenization)
Estate operations (reads VESPER backend)
/api/architecture-statusservice-bound; GET /ops/estate/api/app-catalogservice-bound; GET /ops/estate/api/apps-statusservice-bound; GET /ops/estate/api/action-busservice-bound; GET /ops/estate/api/activation-statusservice-bound; GET /ops/estate/api/alignment-statusservice-bound; GET /ops/estatePanels map to VESPER /api/* endpoints, proxied live via the VESPER service binding at GET /ops/estate (Access-gated). The status cells self-populate from /ops/estate on load. No metric is rendered inline; values come from VESPER, never fabricated.
Operator introspection
/__healthsurface + vesper_bound (JSON)/ops/estatelive VESPER panel data (JSON)/ops/selfcockpit manifest + governance anchors (JSON)Three internal JSON endpoints for operator introspection, all Access-gated. VESPA is the cockpit app; it reads VESPER, it is not VESPER.
Governance anchors
Chain 687e0c0f. Ruling 1: 16 filed / 73 specifications / 9 families. SOC 2 self-certified (no third-party audit claimed). Category positioning is architectural, not an achievement claim. Human sovereignty is supreme; AC-1 is the sole HITL authority.