Marketing site now reflects Apache / Nginx ingestion
Homepage, comparison pages and help docs were still pitching LogLens as a Cloudflare / Vercel / CloudFront story. Updated everywhere to include the Apache / Nginx (Vector) path we shipped earlier today.
When we shipped Apache and Nginx ingestion this morning, the dashboard onboarding picked it up immediately — but the public-facing marketing copy still described LogLens as a CDN-only product. If you ran a plain VPS or dedicated box, the homepage didn't make it obvious that we now support you.
Updated copy across the marketing site so the Vector path appears wherever we list supported sources:
- Homepage — meta description, the "real-time logs from…" hero, the compatibility-check helper text, and the Stream from edge or origin comparison block all now name Apache and Nginx alongside the CDNs.
- Comparison pages (Botify, JetOctopus, Known Agents, Screaming Frog) — the feature lists and pitch paragraphs now read "Cloudflare, Vercel, CloudFront, Apache, or Nginx" instead of stopping at the CDNs.
- Help docs — Quick Start step 3 now includes Apache / Nginx as a first-class connection option, with a link to the setup walkthrough.
No product changes — only the messaging catching up to what already works.
← Recommendations exports now include the site domain in the filenameTrial onboarding: preserve Nginx / Apache detection from the homepage →
← All changelog entries