Support

Support Center for Deployments, Enrollment, and Runtime Operations

If you're deploying CyberArmor, enrolling agents, validating a demo, or troubleshooting a public route, start here. The fastest support path is to identify the affected surface, collect the request details, and separate service health from routing or tenant configuration.

Technical docs

Deployment, endpoint-agent, bootstrap, and routing guidance live in the technical docs.

Open docs

Support runbooks

Use support runbooks for fast triage on 302, 404, 500, 502, bootstrap, endpoint-agent, detection, and secrets-path issues.

Open support home

Contact the team

For product, deployment, or account support, include the environment, tenant ID, affected URL, timestamp, and request ID if available.

hello@cyberarmor.ai

Open Support Ticket

Submit a support request and attach logs securely. Uploads are validated server-side, sent through the configured TLS mail transport, and are not written to marketing server disk.

Allowed: .log, .txt, .json, .har, .yaml, .zip, .gz, and .tgz. Up to 3 files, 5.0 MB each and 8.0 MB total.

No files selected

Deployment and routing

Use this path for DNS, TLS, Caddy, docs, app, admin, support, or public route issues.

  • Confirm the public hostname
  • Compare local service health to public status
  • Capture the exact failing URL and status code

Bootstrap and enrollment

Use this path when endpoint agents, SDKs, browser extensions, or onboarding packages cannot redeem or register.

  • Record tenant ID and package key
  • Check bootstrap token expiry
  • Verify control-plane URL and /pki/public-key

Runtime and evidence

Use this path when policy decisions, detection results, incidents, audit logs, or evidence records are missing or inconsistent.

  • Capture request ID or trace ID
  • Check policy and detection health
  • Attach audit/evidence timestamps

What to collect before escalation

  • Environment name and public hostname involved
  • Exact URL, API path, or portal view that failed
  • Timestamp, tenant ID, user email, request ID, or trace ID
  • Whether the same path works locally on the server
  • Relevant service logs from control-plane, policy, detection, audit, or Caddy
  • Whether the issue is stable, intermittent, or tied to one tenant/package

Severity guide

S1Production outage or security-critical exposure

Customer-facing service unavailable, active data exposure, or evidence/audit integrity risk.

S2Major workflow blocked

Tenant onboarding, policy enforcement, endpoint enrollment, or demo validation cannot proceed.

S3Degraded or isolated issue

A workaround exists, or the issue affects one environment, tenant, package, or integration.

Need a guided walkthrough instead of break/fix support? Request a working session with the CyberArmor team.