Skip to main content

Documentation Index

Fetch the complete documentation index at: https://webscraping.titannet.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

They serve the same broad purpose, but they differ significantly in runtime environment, orchestration style, and operational model.

​
Browser node workers

Browser nodes are standalone scraping workers that run outside the user’s browser. They are designed around:
  • Browser automation with Playwright and Puppeteer
  • Explicit node bootstrap and registration with the platform
  • Work delivery from Titan’s orchestration layer
  • Structured ingestion of results and media
This worker model fits the main modern Titan execution architecture.

​
Chrome extension workers

Chrome extension workers are browser extension agents that execute jobs inside a browser environment. They connect through Titan’s extension-oriented services. This model uses:
  • Bootstrap discovery
  • Harbor selection and authentication
  • WebSocket-based job delivery
  • Script injection into browser pages
  • Extension-driven result reporting
This worker model is operationally distinct from browser nodes and should be documented as its own execution path.

​
Why Titan documents both

From a user perspective, both worker models can support the same Titan tasks (extraction, navigation, and related automation). From an operator perspective, they are different systems with different lifecycle behavior and different control flows. That is why the documentation treats worker types as a first-class concept instead of hiding them behind a generic “worker” label.

​
Shared platform principles

Despite their differences, both worker models share the same high-level responsibilities:
  • Receive or request work
  • Execute scraping logic
  • Return structured output
  • Report status
  • Integrate with a broader platform lifecycle

​
Next steps