Architecture

Why a proprietary application protocol exists

PowerVest uses a defined application protocol so client operations—authentication, messaging, synchronization, files, licensing and updates—share a consistent request model instead of ad hoc APIs.

Public-safe protocol characteristics

• Structured operations for backend capabilities rather than arbitrary remote execution.
• Client identity and authorization handled separately from transport convenience.
• Protocol versioning managed as part of product compatibility planning.
• Layered AES-256-based protection using server-side, client-specific and per-communication elements.
• Operational security for keys, backups, monitoring and infrastructure remains a customer responsibility.

Four public-safe layers

1. Product-facing clients: desktop clients, web-facing application services, internal systems and administration tools.
2. SGClient integration layer: application-facing transport, response handling and client identity.
3. Protected PowerVest protocol: a defined application protocol for structured operations.
4. PowerVest Windows Service and protected data services: authentication, messaging, synchronization, files, licensing, updates, queues, quotas and encrypted storage.

Request sequence (high level)

A client prepares a structured operation through SGClient. The protected protocol carries the operation to the Windows Service, which applies authorization, executes the requested backend capability and returns a structured response.

Packet formats, command identifiers and implementation details are not published on this website.