Customer cloud / private environment
Containerised VESA inside the customer-controlled environment.
SECURITY
Core decisioning, sensitive evidence and detailed audit remain inside the customer environment by default.
CUSTOMER-LOCAL PROCESSING
VESA — the customer-local VICTA data plane — performs data-security processing, enrichment, governed decisioning, authorised review and local audit. Customer-defined deterministic policy remains authoritative.
Future management functions are designed for configuration, version state and sanitised operational reporting. Raw operational evidence remains separate by default.
RESTRICTED-NETWORK ARCHITECTURE
VICTA separates customer-local event decisioning from planned management-plane functions so the operating pattern can match the organisation’s network boundary.
Containerised VESA inside the customer-controlled environment.
No open inbound access is required for normal operation. Customer-approved outbound connectivity only.
Core local processing can operate without per-event control-plane dependency. Control-plane communication can be delayed or disabled, and updates handled manually where required.
Connectivity to cloud-hosted source or workflow systems remains necessary where those integrations themselves depend on external APIs.
LOCAL EVIDENCE BOUNDARY
Core VICTA processing and detailed audit stay with VESA. Management-plane communication remains separate and is not a raw customer-evidence path.
Future management functions are designed for configuration, version state and sanitised operational reporting. Raw operational evidence remains separate by default.
AI advises selectively within governed boundaries. Customer policy and authorised analysts remain authoritative.
This marketing website is not intended to receive customer security evidence, event payloads, credentials or secrets.
Discuss how VICTA’s local-first operating model can fit your data-security environment.