Pre-release Paid design-partner programme

Support

Get help without exposing the site you are trying to protect.

Support is currently founder-led for paid design partners. Public Community and Pro channels, service levels, and response targets remain hypotheses until support volume and capacity are measured.

Apply as a design partner Explore the sample trace
Current channel

Email hello@wpflame.com with the subject “WP Flame design-partner support”. Do not attach raw trace exports, credentials, production database dumps, or customer data to an initial email.

Current support scope

Focused on safe diagnosis and pre-release evidence.

Included in the design-partner programme

  • Onboarding and capture-safety review.
  • Health, capability, storage, and retention triage.
  • Review of one agreed slow workflow and its supported findings.
  • Help preparing a redacted developer or vendor handoff.
  • Recording compatibility gaps and misleading conclusions against the release roadmap.

Outside the current product support scope

  • Emergency hosting, security, malware, backup, or disaster-recovery service.
  • Guaranteed remediation of third-party plugin, theme, host, or external-service defects.
  • Automatic optimization or unrestricted custom development.
  • General infrastructure, Core Web Vitals, SEO, conversion, or capacity consulting.
  • A fixed response-time SLA before beta support capacity has been measured.

Prepare the request

Send enough context, not sensitive payloads.

  1. Describe impact. Name the affected workflow, when it began, who is affected, and whether disabling WP Flame changes the behavior.
  2. Record environment. Include WordPress, PHP, database, host type, multisite, relevant plugin/theme, and WP Flame versions.
  3. Include capture state. Provide mode, capability statuses, health warnings, incomplete reasons, and capture-session policy.
  4. Write reproduction steps. Use a test account and synthetic values; identify the route/action without copying credentials or personal data.
  5. Wait for a secure handoff. If a diagnostic bundle or trace is necessary, use the agreed redacted export and approved transfer method.

Triage guide

Stop first when site safety changes.

Design-partner support priority guide
SituationImmediate actionWhat to report
Fatal error, request interference, or data lossStop capture, deactivate WP Flame if safe, preserve logs, and restore the site through normal operational procedures.Timestamp, affected request, environment, whether deactivation restored behavior, and redacted error details.
Unexpected overhead or storage growthStop broad capture, note mode/policy, check expiry and retention, and preserve health state.Mode, requested count, duration, storage growth, trace size, and reproduction.
Unavailable capabilityDo not force an unsupported instrumentor. Continue only if the degraded trace remains useful.Capability report, database/drop-in context, and health warning.
Questionable findingDo not act on a high-impact conclusion until supporting evidence and completeness are reviewed.Finding, related spans, evidence count, confidence, and incomplete reasons.

Responsible disclosure

Report vulnerabilities privately

Email hello@wpflame.com with the subject “WP Flame security report”. Describe the affected version, impact, prerequisites, and reproduction without placing exploit details in a public issue. Do not access data or systems beyond your authorization.

Public channels later

No promises before capacity evidence

The proposed Community model uses documentation and a public support channel. Proposed paid editions add ticket support and may add priority routing. Exact channels and targets will be published only after beta support demand is measured.

Review safe capture stepsCheck compatibility statusReview data handlingReview project status changes

Current route to release

Bring a real slow WordPress workflow.

The paid design-partner programme pairs controlled captures with founder-led review while the public release gates are completed.

See the programme