Profiles
Isolated identities and persistent browser state
Project GHOST brings profiles, proxies, warmup, scheduling, and fleet control together for Yandex and Google tasks across mobile and desktop profiles.
Isolated identities and persistent browser state
Proxies, geography, and availability checks
Search, browse, warmup, and schedules
Status, logs, and emergency stop
Create a project, profiles, and connection rules.
Choose a search engine, form factor, and workflow.
Track sessions, logs, and risk signals.
Distribute work across your fleet and schedule.
Core capabilities share project state instead of drifting across separate utilities.
Cookies, browser storage, history, and profile lifecycle persist across sessions.
Learn moreAvailability checks, geo resolution, profile assignment, and fail-closed handling of invalid configuration.
Learn moreGradual warmup workflows, duration limits, and scheduled tasks.
Learn moreStructural search result parsing for mobile and desktop profiles.
Learn moreThe portal presents machines, licenses, status, and permission-scoped remote commands.
Learn moreLogs, progress, diagnostics, preview frames, and targeted session cancellation.
Learn moreWhen the structural path cannot complete an action, an optional VLM path can help locate it. Screenshot transfer requires explicit consent; input fields, private regions, and sensitive elements are masked before transmission.
Encrypted Chromium delivery, SHA-256 verification, signed release manifests, and license-bound update policies reduce substitution risk. Supported delivery targets are Windows x64 and Ubuntu deb or AppImage.
No. Core execution runs in the Desktop application on your machine; the portal handles access and control.
No. Public payments are currently unavailable. Access follows a workflow review and onboarding.
Working paths are available for Yandex and Google across mobile and desktop profiles.
Structural rules and action recovery run first. VLM is a bounded fallback when consent is enabled.
No. Search engines and sites change their policies and signals. Operators must respect platform limits and assess risk.
Tell us about your workflows, fleet size, and environment. We will review compatibility and propose an onboarding sequence.