[P2] Audit: Pricing page states free/open source but does not capture sponsor or self-host interest

[baixiangcpp]

Imported from the byteflow.tools deep audit on 2026-06-22.

Problem: the Pricing page clearly states the product is free, open source, has no accounts, and has no premium tier. This supports trust, but it misses an opportunity to capture users who want to sponsor, self-host, or request enterprise/private deployment guidance.

Affected URL:

• https://byteflow.tools/en/pricing

Reproduction steps:

1. Open /en/pricing.
2. Review the free/open-source messaging.
3. Look for sponsor, GitHub Sponsors, self-hosting, enterprise support, or contact CTA.
4. Compare links to About, Contact, GitHub, and Trust Center.

Expected behavior: the page should preserve the no-paywall promise while offering non-invasive paths for sponsorship, self-hosting docs, or support inquiries.

Actual behavior: the page communicates free status but does not capture support or self-host demand.

Impact: missed funding and partnership opportunities without compromising privacy.

Proposed fix:

• Add “Support the project” CTA if sponsorship exists.
• Add “Self-host byteflow.tools” CTA linking to documentation.
• Add “Need internal deployment guidance?” contact CTA.
• State clearly that no hosted account or cloud payload storage is planned.

Acceptance criteria:

• Pricing page keeps free/no-account message.
• Sponsor/self-host/contact CTAs are visible but not pushy.
• No copy implies future paywalls for existing tools.
• CTAs are tracked with safe aggregate events.

[baixiangcpp]

Closed as completed by the canonical BF audit backlog work. This older non-BF audit issue duplicates work now merged through PRs #209-#219, with the BF issues closed and guard/test coverage in place. The remaining non-duplicate follow-up is #7, which stays open because the upstream Next/PostCSS advisory is not fixed yet.

[baixiangcpp]

Reopening after acceptance review on 2026-06-24. The Pricing page preserves the free/no-account positioning and links to GitHub plus self-hosting, but this older audit issue is not fully satisfied: it still lacks an explicit contact/internal deployment guidance CTA, and the current pricing-positioning guard even asserts the page must not route to /contact. Acceptance requires sponsor/self-host/contact CTAs that are visible but not pushy, without implying paywalls. Keep open until the Pricing page and guard align with that acceptance.