Early Access
Request early access

Use cases

Where bugs hide when more than one person is involved.

Each case below shows the problem, the ghosts that take part and what the test proves. They are the kinds of checks the product runs today in its synthetic labs.

Example tests

  1. 01

    Authentication and sign-in

    Crowd, 2 ghosts

    The problem

    Two people sign in at nearly the same time and one of them lands in the other person's account or dashboard.

    Ghosts

    • Member A
    • Member B

    The test verifies

    • Each person reaches their own dashboard
    • The name and data on screen belong to the signed-in person
  2. 02

    Roles and permissions

    Crowd, 2 to 5 ghosts

    The problem

    The menu hides the admin page from editors, but typing the address or calling the API still works.

    Ghosts

    • Administrator
    • Editor
    • Anonymous

    The test verifies

    • The administrator can open the page
    • The editor is refused in the interface and by the server
    • An anonymous visitor is sent to sign in
  3. 03

    Forms and validation

    Single Ghost

    The problem

    A support request is sent without a required email. The validation message appears and every other answer is cleared.

    Ghosts

    • Visitor

    The test verifies

    • A clear message names the missing field
    • Other answers are kept
    • The completed form submits once
  4. 05

    Shared state and collaboration

    Crowd, coordinated

    The problem

    An administrator approves a document. The editor who submitted it opens the page again and still sees Submitted.

    Ghosts

    • Editor
    • Administrator

    The test verifies

    • Approval waits for the submission
    • The editor sees Approved after the approval
    • Both sessions agree on the status
  5. 06

    Multi-user workflows and revocation

    Company or crowd

    The problem

    An owner shares a record, then revokes access. The viewer, still signed in, opens the record and it loads.

    Ghosts

    • Owner
    • Viewer

    The test verifies

    • The viewer can read while shared
    • Access ends when revoked, in an open session too
    • The owner's dashboard reflects the change
  6. 07

    Regression after code changes

    Saved check

    The problem

    Your coding assistant refactors the data layer. A status bug you fixed last month quietly comes back.

    Ghosts

    • Editor
    • Administrator

    The test verifies

    • Every check that passed in the approved baseline still passes
    • A returning failure is reported as a new regression
    • The CLI exits 1 so CI can stop the release

Kinds of software

Any web app where people have different jobs.

Ghost Company is not tied to one industry. If your app has users, roles or shared data, there is a question the ghosts can ask.

Kinds of software and an example question for each
If you buildThe ghosts might ask
SaaS products and developer toolsDoes a new team member see only their own workspace?
Websites and portalsDoes a signed-out visitor stay out of account pages?
Internal business applicationsCan a request be approved by someone who also submitted it?
Dashboards and admin systemsDo filters and totals agree with the records behind them?
Collaborative and community appsDoes an edit by one member reach everyone else?
Booking and management softwareCan two people book the last slot at the same time?
Education and publishingDo students see grades only after a teacher publishes them?
Other interactive web experiencesDoes the journey survive back buttons and double clicks?

Browser tests target web applications. Native mobile and desktop apps are not supported.

Development situations

When to call the ghosts.

After an AI assistant changes code
Large generated diffs touch more than you read. A saved check covers the journeys you care about.
Before a release
Run the checks against the build you are about to ship and require the lab to report its revision.
After touching auth or roles
Permission bugs are rarely visible to the person who wrote the change. Ghosts with other roles see them.
On pull requests, in CI
Use the reusable GitHub Actions workflow on an isolated runner and fail the job on a regression.

Have a case we did not list?

Tell us about your app in the early access form. The kind of app and workflow you describe shapes who we invite first.