Web4 turns one persistent browser-environment foundation into six operating modes. Start with the relationship that must stay coherent, then continue to category and platform context.
Persistent browser environment Operating mode Workflow relationship Platform context
Each route begins with a different operating relationship. The six routes share one Web4 product foundation; they are not separate products or availability tiers.
A category organizes browser work. External platforms retain control of their policies, account decisions, service state, and outcomes.
Every mode composes the same connected layers. Read the owner page when you need mechanism detail; this hub keeps the dependencies visible without reproducing the Features architecture.
Cookies, storage, login state, and environment context stay isolated by saved profile.
Understand saved browser identity and profile contextHTTP, HTTPS, or SOCKS5 route configuration remains associated with the profile as a distinct environment layer.
Understand per-profile route contextNatural-language and programmatic execution surfaces reuse saved profile context instead of rebuilding it for every run.
Repeatable browser steps and approved tool connections can be organized around the same profile context.
Organize repeatable browser work with Skills and MCPRoles and projects organize access while activity and execution records support review, troubleshooting, and handoff.
Review access, activity, records, and handoffThe field changes structure from one mode to the next. Four secondary workflows cross modes where browser work needs team support, handoff, or diagnostics.
Keep each account’s saved environment, responsibility, and route relationship legible across the portfolio.
Explore the portfolio operating model| Store / Market | Market context | Profile context |
|---|---|---|
| Store context | Operator assignment | Saved profile |
| Recurring work | Market route | Profile continuity |
Map Store and Market before assigning the Operator and saved Profile that carry the work.
Explore the store and market operating modelKeep account identity distinct from content work, then connect both to assignment and handoff.
Explore the identity and content operating modelSeparate client and ad-account contexts, connect market and profile ownership, and converge on review.
Explore the client and ad-account hierarchyDefine the brief and authorized scope before browser work, then preserve evidence for review.
Explore the authorized research workflowSeparate persistent account readiness from event-specific, route-specific, and time-sensitive run state.
Explore the readiness and live-run lifecycleChoose the operating relationship first, then recognize the relevant platforms at a glance.
Platform names identify workflow context only. They do not imply affiliation, endorsement, or control of platform decisions.
Web4 organizes its browser-environment and workflow surfaces. The user defines the objective and authorized scope. External services retain their own rules, decisions, state, and outcomes.
Saved profile; supported route/profile configuration; execution surfaces; reusable workflow structure; reviewable records.
Scenario choice; task objective; authorized scope; account and project labels; responsible owner.
Platform policy; account decisions; provider reputation; external service state; final outcome.
Choose one of the six category routes for scenario detail. Return to Features only when you still need product-mechanism detail.
Create a free account, then apply for Windows trial access when you are ready to test Web4 Browser. Trial access is by approval.
