Early Access
Request early access

How it works

Six steps from a question to a verified fix.

Ghost Company is a loop, not a one-off scan. You decide what to check and who takes part, the ghosts run it in a browser, and the same check tells you later whether the fix still holds.

  1. Choose a testing objective

    Start with a question about your app, in plain words: "Can an editor reach the admin page?" or "Does the status update after approval?". Pick a ready-made test, or write your own idea and open it in Scenario Studio.

    When AI drafting is configured, it can turn the idea into a proposed scenario for you to review. Nothing runs until a person accepts and publishes it.

    What should the ghosts check?Illustration
    • AuthenticationTwo people sign in and reach their own dashboard.
    • Permissions and rolesAn administrator and an editor open the same admin page.
    • Forms and validationA request is sent without a required field, then completed.
    • Search and filteringSearch tasks for "report", then show open tasks only.
    • CollaborationAn editor submits, an administrator approves, the editor checks.
  2. Define the ghosts and their roles

    Each ghost combines a persona with an access profile and objectives. Choose a mode: one ghost, an independent crowd, or a company with reporting lines. In parallel scenarios, ghosts act in their own lanes and can wait for one another.

    Try the modes. The diagram changes; nothing is executed.

    EchoEditor
    LunaAdministrator
    PixelViewer

    Independent people at the same time. Dashed blocks wait for another ghost.

  3. Prepare an authorized environment

    Ghosts only act where they have been invited. A platform operator grants a workspace access to an exact origin. Before every attempt the lab is reset to known synthetic data and checked for readiness.

    Today that means operator-approved synthetic labs, including a ready-made demo app. Testing your own application is not open yet.

    Lab readinessIllustration
    • Operator grant for this workspace and exact origin
    • Synthetic accounts for each access profile
    • Verified reset to the initial fixture
    • Readiness check passed
    • Kill switches: not engaged
  4. Run the browser test

    Each run starts a fresh, isolated Chromium sandbox. Ghosts act in their own sessions, in order within their lane, and every action ends in an assertion on what the page or server returned.

    You can watch it live in the Ghost office. Authorization is checked again during the run, so revoking access stops the ghosts within seconds.

    Your workspace
    Queue and worker
    Chromium in a per-run sandbox
    Egress proxy, one origin
    Approved synthetic lab
  5. Investigate the result and evidence

    The result says what the ghosts tried, what they saw and what was expected. A failed setup or a timeout is reported as inconclusive, never as a bug in your app.

    Findings carry reproduction steps, the observing ghost and its role, an evidence timeline and available screenshots. Where to investigate is shown as a hypothesis.

    FindingIllustration

    The editor can open the admin user list

    Seen by
    Luna, as Editor
    Expected
    Editors are refused (403)
    Observed
    The page loaded (200)
    Hypothesis
    The route checks sign-in but not role. Not confirmed.
  6. Fix it and run it again

    Copy the fix prompt into your coding assistant, or fix it by hand. Then run the same check again. Approve a good result as a baseline, and later runs, from the app, the CLI or CI, tell you if anything regresses.

    Compared with the previous runIllustration
    CheckBeforeAfter
    Administrator opens user listpasspass
    Editor is refused in the menupasspass
    Editor is refused by the serverfailpass

    Issue confirmed resolved same version, lab and fixture

Ready when your app is.

Request early access and tell us how you build. We will follow up when there is a fit with the current lab boundary.