Skip to content

[Browser Run] Add FAQ: why run browsers in the cloud instead of locally#31384

Open
kathayl wants to merge 1 commit into
productionfrom
browser-run-faq-cloud-vs-local-v2
Open

[Browser Run] Add FAQ: why run browsers in the cloud instead of locally#31384
kathayl wants to merge 1 commit into
productionfrom
browser-run-faq-cloud-vs-local-v2

Conversation

@kathayl

@kathayl kathayl commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Adds a new FAQ entry to the Getting started & Development section explaining the benefits of cloud-hosted browsers over running locally.

@cloudflare-docs-bot

Copy link
Copy Markdown
Contributor

Review

Review in progress for commit 4f3e671

@github-actions

Copy link
Copy Markdown
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/browser-run/ @mchenco, @cloudflare/product-owners, @celso, @kathayl, @dcpena, @meddulla, @simonabadoiu, @jonnyparris, @ruifigueira, @Refaerds, @omarmosid

@ask-bonk

ask-bonk Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

PR Summary

This PR adds a new FAQ entry (### Why run browsers in the cloud instead of locally?) under the Getting started & Development section of src/content/docs/browser-run/faq.mdx. The entry explains the operational benefits of cloud-hosted browsers over local execution, including on-demand sessions, no local Chrome/VM maintenance, integration with Cloudflare Queues for scale, and proximity to target sites via Cloudflare's network. It also cross-links to the Queues web crawler tutorial, Wrangler bindings reference, and Durable Objects how-to guide.

Labels

The existing labels (size/s, product:browser-run) are appropriate. No additional labels are needed.

Issues Flagged

I found two minor style/grammar issues in the new content that should be addressed before merge:

  1. Heading punctuation & phrasing
    The new H3 heading is a question ending with ?. While this matches the existing convention used throughout this FAQ page, the style guide states: "Subtitles/subheadings must be verb or noun phrases — never a question" and "Do not end headings with punctuation." Since every other FAQ heading on this page also uses a question, I am not blocking on this, but maintainers should be aware that the page as a whole diverges from the global heading policy.

  2. Grammar: "a queue infrastructure"
    "Infrastructure" is uncountable in this context. The phrase "without managing a queue infrastructure yourself" should be revised.

  3. Style: wordy phrasing
    "your automation keeps running without a local machine" can be tightened.

Suggested Changes (Inline Review)

On line 88 of src/content/docs/browser-run/faq.mdx:

With Browser Run, browser sessions run on Cloudflare's infrastructure, so your automation keeps running without a local machine.

Suggestion: Simplify to improve clarity.

With Browser Run, browser sessions run on Cloudflare's infrastructure, so your automation runs without a local machine.

On line 90 of src/content/docs/browser-run/faq.mdx:

allowing you to crawl at scale without managing a queue infrastructure yourself.

Suggestion: Remove the article before the uncountable noun.

allowing you to crawl at scale without managing queue infrastructure yourself.

(Alternatively: "without managing your own queue infrastructure.")

Validation Notes

  • Links: All three links (/queues/tutorials/web-crawler-with-browser-run/, /browser-run/reference/wrangler/#bindings, /browser-run/how-to/browser-run-with-do/) resolve correctly.
  • Frontmatter: Unchanged and remains valid.
  • MDX syntax: No unescaped {, }, <, or > characters. No new component imports required.
  • Style guide: No contractions, no LLM-filler phrases, active voice used, proper nouns capitalized.

Verdict

Approve with minor suggestions. The content is accurate and well-placed. If the author accepts the two wording suggestions above, this is ready to merge.

github run

@github-actions

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants