Service boundaries from console to endpoint.
ZENQIX separates the public website, control plane, operational data, remote support and endpoint agent paths.
Authenticated administration. Outbound endpoints.
Administrator requests pass through the product control plane and authorization checks. Routine endpoint communication originates from the agent toward the approved service.
Product information and public documentation only.
Identity, RBAC, tenant scope, jobs and API operations.
Endpoint state, inventory, job records and evidence.
Heartbeat, inventory and capability-scoped authorized work.
Controls tied to endpoint risk.
Routine management does not require a general inbound management port on every endpoint.
Known operations use structured parameters instead of concatenated shell commands.
Provider result and post-action endpoint observation are separate states.
Website, Endpoint services, remote support and data stores remain separate operational responsibilities.
Match the architecture to your environment.
Document network, data ownership, backup and access requirements before the pilot.