How BetaWindow Works

BetaWindow connects AI-built apps with real human testers who run live end-to-end test sessions — complete with network logs, console captures, and structured feedback — in under 4 hours.

Overview

When you ship an AI-built app, you need confidence that it actually works for a real person clicking through it, not just unit tests or synthetic checks. BetaWindow gives you that confidence at a fraction of the cost of a traditional QA team.

Step 1 — Create a job

Submit your app URL and pick a tier (Quick, Standard, or Deep). Write optional test instructions describing the flows you want covered — e.g. "sign up, create a project, invite a collaborator". Credits are held (not charged) when you publish the job.

Example job creation via API:

POST /api/jobs
{
  "title": "Test signup + onboarding flow",
  "url": "https://your-app.vercel.app",
  "tier": "standard",
  "instructions": "1. Sign up with a new email\n2. Complete onboarding\n3. Create your first project"
}

Step 2 — A tester claims your job

Human testers browse the marketplace and claim open jobs. Once claimed, the tester opens a dedicated testing session with your app loaded in an instrumented Chrome frame. All network requests, console logs, and errors are captured automatically.

Step 3 — Live testing session

The tester follows your instructions, exploring the app naturally and noting any unexpected behaviour, UI issues, broken flows, or errors. The platform records:

  • Every network request (method, URL, status, latency)
  • Browser console logs and errors
  • Annotated screenshots at each key step
  • A session timeline with timestamps

Step 4 — Feedback report

When the tester finishes, they submit structured feedback including:

  • Pass / fail verdict per flow
  • Bug reports with steps to reproduce and severity
  • Overall UX quality score (1–5)
  • Free-form comments

You receive the full report in your dashboard — with the raw network log and console capture attached — immediately after submission.

Step 5 — Credits settled

Credits on hold are converted to spent once the feedback is accepted. If no tester claims your job within 24 hours, the credits are fully refunded. If you reject a submission, it re-enters the queue for a new tester.

Who are the testers?

BetaWindow testers are vetted freelancers — designers, developers, and QA professionals — who have completed an onboarding qualification test. Each tester has a quality score based on accepted submissions. Low-quality submitters are automatically removed from the platform.

What kinds of apps can I test?

Any publicly accessible web app. The app must be reachable via HTTPS — staging environments, Vercel preview deployments, and production URLs all work. The platform does not support localhost URLs or apps behind VPN/basic-auth without a bypass token.

Ready to get started?

Create your first job in under 2 minutes. No SDK required.

Create a job →