Agent successfully gathered enough information to explain NetBird's core offering, pricing, and competitive positioning, but hit friction when the site's own comparison articles returned server errors and several key pages (use cases, features, resources) were 404s. The agent filled gaps using web search results and external comparison sites rather than NetBird's own documentation.

• ›Homepage and pricing pages loaded cleanly and contained direct answers (steps [1], [2]), establishing what NetBird does and its pricing tiers without ambiguity.
• ›About page (step [8]) was accessible and mission-driven, clearly positioning NetBird for cost-conscious organizations wanting to democratize security—a key differentiator the agent correctly highlighted.
• ›Blog comparison articles mentioned in step [5] (Tailscale vs NetBird, ZeroTier vs NetBird, etc.) were listed but returned 502 errors when fetched (steps [6], [7]), forcing the agent to rely on external comparison sites and web search snippets for competitive positioning.
• ›Multiple site pages were 404s (features, use-cases, resources, comparison URLs typed from memory), suggesting either incomplete site architecture or reliance on search discovery; the agent worked around this by guessing URLs and using web search.
• ›Web search (step [11]) and the /compare page (step [12]) provided the bulk of competitive differentiation details, particularly technical architecture differences (Layer 2 vs Layer 3, self-hosting vs proprietary control planes), which came from external sources, not netbird.io's own documentation.