Fly.io

Create a dedicated documentation page or section on 'System Limits and Maximums' that specifies kernel-level constraints (file descriptors, ephemeral ports), proxy-level connection limits per Machine, and any hard ceilings that apply regardless of fly.toml configuration. Include WebSocket-specific guidance given the 50k concurrent connection use case.

Add documentation about WireGuard logging and audit capabilities, including: whether connection attempts are logged, what metadata is captured (timestamps, source IPs, peer identities), if commands over the tunnel are logged, how long logs are retained, and how customers can access these logs for compliance auditing. This could be added to the Private Networking or Security documentation sections.

Create a dedicated pricing section for log retention that clarifies: (1) whether extended retention beyond 2/30 days is available as a paid feature, (2) if so, whether pricing is flat-rate or volume-based, and (3) pricing tiers for common retention periods like 90 days.

Add a dedicated documentation page or FAQ entry specifically addressing organization-level machine limits, including: the default numeric limit per organization, whether it can be raised via support ticket, and guidance on when to use multiple organizations vs. requesting a limit increase.

Add explicit mention of ISO 27001 status (yes/no) and provide a self-service portal or clear instructions for downloading SOC 2 Type 2 and any other compliance reports, rather than requiring email contact.

Add specific cold start latency benchmarks broken down by image size (e.g., 500MB, 2GB, 5GB) and region, or at least clarify whether image size significantly impacts the "~2+ seconds" baseline.