Central Management

Coordinate distributed protection through a self-hosted control plane. Organize applications into projects and manage the people, credentials, agents, and security policies attached to each project.

OperatorsProjects, rolesControl planePolicy, auditAgentsWAF and hostmTLS gRPCOperatorsProjectsControl planePolicy, auditAgentsWAF and host
  • Policy out
  • Events back

What it provides

  • Project membership with viewer, member, and owner roles.
  • Certificate-based agent enrollment and gRPC mutual TLS.
  • Configuration bundles delivered to connected WAF agents.
  • Light agent traffic: host telemetry is compressed and detailed status is sent only while someone views it.
  • Audit records for security-relevant administrative changes.

How to use it

  1. Deploy the control plane and initialize an administrator account.
  2. Create a project, assign appropriate membership, and provision agent credentials.
  3. Connect agents, verify their status, and apply project policies from the dashboard.
Deploy control planeCreate the administratorCreate a projectMembers, credentialsConnect agentsApply policiesDeploy control planeCreate the administratorCreate a projectMembers, credentialsConnect agentsApply policies
  • Order of the steps

Configuration and operation

System administrator access is separate from project roles. Provision credentials through the Credentials page and protect private keys. The certificate fingerprint identifies the agent’s project; provider Auth-Keys are separate credentials.

Limits

Agent connectivity and version compatibility affect update delivery. Self-hosting also means operating backups, upgrades, database retention, and access controls. Different data providers may require their own credentials and outbound connectivity.