Site Adapter Architecture for Internal Platforms

Why This Search Exists

When teams share browser automation informally, execution mode tends to be implicit and inconsistent. That makes the system harder to trust and harder to operate at scale.

Internal platform work needs a clearer abstraction than copied scripts or undocumented browser habits.

Recommended Approach

A site adapter architecture gives repeated tasks stable names, arguments, and explicit execution mode. That improves discoverability and reduces confusion across teams.

iatlas-browser already provides a foundation for this with its site adapter model and hosted subset.

Key Takeaways

• Reusable browser commands need explicit execution boundaries.
• A catalog beats scattered scripts for internal platform work.
• Hosted-safe adapters should stay public and read-only.
• Stateful workflows should stay on the local runtime.

Fast Start

1. Inventory the repeated browser tasks used by internal teams.
2. Normalize names, arguments, and expected outputs.
3. Label hosted-safe versus local-only tasks clearly.
4. Publish the adapter catalog through the appropriate surfaces.