Support

Reach Wardex support directly.

For integrations, deployment help, operator questions, licensing, or release troubleshooting, use email. Support requests for the website and product go to mip@gmx.biz.

Email Support Support Paths Commercial licensing →

Support Paths

Pick the right mailbox on the first try.

Keep support simple: email first, include enough context, and use a clear subject so the request lands in the right queue immediately.

Primary Channel

General Product Support

Email

Use this for deployment help, integrations, rules questions, release regressions, documentation gaps, or general operator feedback.

  • Best for evaluation, rollout, and admin-console questions
  • Useful for "how should I integrate this?" discussions
  • Include version, environment, and exact failure mode
Email mip@gmx.biz

Commercial & Licensing

Contact

For production deployments, commercial licensing, rollout planning, or contract questions, start here instead of using a generic support mail.

  • Production licensing under BSL terms
  • Rollout, hardening, and operating-model discussions
  • Faster routing for buyer and stakeholder questions
Request Commercial Terms

Security & Responsible Disclosure

Sensitive

For security reports or sensitive issues, email first and use GitHub Security Advisories when you need a private disclosure trail.

  • Email the issue summary and affected version
  • Use private disclosure for proof-of-concept material
  • Coordinated response with a 90-day default window
Send a Security Report

Support requests on the website and product go to mip@gmx.biz. Include the version, deployment model, affected page or endpoint, and what you already tried.

What To Send

Make the first reply useful.

01

Version & Deployment Model

State the Wardex version, platform, how many agents are involved, and whether you run standalone, control-plane + fleet, or an air-gapped deployment.

02

Exact Failure Mode

Describe what you expected, what actually happened, the affected integration or screen, and whether the issue is reproducible or intermittent.

03

Logs, Payloads, Screenshots

Attach the relevant API error, log excerpt, screenshot, or sample payload. Sanitised real examples are more useful than generic summaries.

04

Desired Outcome

Say whether you need a workaround, root-cause analysis, rollout guidance, or a product/documentation change so the reply can be scoped correctly.

Self-Service First

Use the docs before you email.

The fastest support loop is often a doc page, runbook, or release note you can open immediately. These are the first references to check before sending mail.

Read the Runbooks

Deployment, agent operations, troubleshooting, and SIEM guidance already live in the repo and answer most first-run questions.

Open Resources

Check the API Contract

For API or integration issues, compare the live behavior against the versioned OpenAPI definition before escalating.

API Reference

Review Integration Notes

The integrations page now documents delivery semantics, payload mapping, and the recommended dry-run procedure.

Integration Docs

Escalate by Email

If the docs stop being sufficient, send the collected context directly to the support mailbox and reference the exact page or integration.

Send Support Email