Why This Search Exists
Teams get into trouble when they treat public retrieval, session-aware automation, and browser debugging as one class of product. That blurs the trust boundary and complicates the operating model.
The architecture question is really about where browser state lives and which tasks are safe to expose remotely.
Recommended Approach
Use a local runtime for workflows that depend on a person’s real browser session, and use a hosted layer only for narrow public retrieval or remote-safe adapters.
iatlas-browser already follows this split with the local core product and the hosted `miaoda.vip` subset.
Key Takeaways
- State location should drive architecture decisions.
- Local runtime is for browser-session-dependent work.
- Hosted APIs are for public or remote-safe retrieval.
- A clear boundary improves reliability and product clarity.
Fast Start
- Classify workflows by whether they depend on active browser state.
- Route public read-only tasks to the hosted layer.
- Keep session-aware tasks on the local runtime.
- Document the boundary for builders and users.
Next Action
Explore architecture docs
Move from research to implementation by choosing the correct boundary: local runtime for real-session work, hosted API for public-safe retrieval.