Browser automation as data. Compose, schedule, audit.

Selenium IDE is record-and-replay. Playwright in a repo wants a CI pipeline. PilotStudio puts pilots in MongoDB and runs them on a managed Playwright service — credentials vaulted, runs streamed, schedules quota-enforced.

See features

Browser automation today forces a bad choice.

Option A: code in a repo. Use Playwright/Selenium, run in CI, log to artifacts. Scripts share nothing — every team rebuilds the same login flow. Credentials rotate independently from scripts.

Option B: record-replay tools. Selenium IDE, BrowserStack recorder. Easy to start, impossible to maintain. The recorded XPath breaks on the next layout tweak.

Key features

A web-based authoring environment Playwright deserves.

Lifecycle phases (setup / verify / cleanup / on_failure).

Each phase references a saved Script Runner script. Cleanup runs always in finally{}. On Failure runs only on prior failure for diagnostics. Per-phase status persists to the run document with precedence-aware coloring.

Pilot lifecycle — setup / verify / cleanup / on_failure

Credential vault entry — four-identity audit (Internal User / Run As / Username / Email)

Credential vault with delegation.

AES-256 encrypted at rest. Scripts call getCredentials('vendor-portal-prod') and receive a decrypted object. Pilot authors never touch passwords. Rotate the credential; every pilot picks it up. Each vault entry carries four identities: internal user, run-as user, carrier login, MFA contact.

Compose pilots via shared fragments.

Share a login fragment across 50 pilots. Edit it once; every pilot picks up the new behavior. The run-detail panel shows the resolved script after include expansion — no guessing what the pilot executed.

Scheduled runs with tenant quota.

Cron-driven schedules respect tenant monthly quotas. Hit the cap and the next fire marks last_status as quota_denied — logs the denial, skips dispatch, doesn't inflate failure_count. GitHub Actions has nothing equivalent.

Run history inline. No CI dashboard hop.

Every run produces a _web_pilot_run document with phases, logs, warnings, errors, screenshots, and the resolved script. The detail panel renders it all inline. Switch between recent runs via the dropdown.

Run detail — logs / errors / source / screenshots

What only PilotStudio offers

What Selenium IDE, BrowserStack, and UiPath cannot do.

Credentials vault with delegation. Pilot authors never touch passwords. Audit chain links internal user → run-as user → carrier credential.

Lifecycle phases as Script Runner references. Share setup logic across many pilots. Edit one place; everyone picks it up.

Composition via shared fragments. Fragments shared across 50 pilots, edit one place.

Run-detail panel inline. Same workspace as your DataStudio queries. No CI hop.

Tenant-level quota enforcement. Scheduled runs that exceed cap bounce cleanly with last_status=quota_denied.

Pilots are MongoDB records. Queryable, syncable, comparable across envs via Bulk Compare.

Use cases

What teams build with PilotStudio.

Customer-portal scraping

Carrier portals, vendor dashboards, regulatory sites. Authenticate via vault, navigate, extract.

Carrier integrations without an API

Submit quotes, fetch policy documents, download forms. The pilot is the integration when the vendor refuses to offer an API.

Doc screenshot pipelines

Daily pilots take screenshots of public-facing screens, upload to R2. Schedules keep docs visually current.

Scheduled monitoring

Critical user flows fire every morning. Failed runs page on-call. Quota-denied runs flag plan-limit issues.

Automate the browser. Skip the CI dance.

PilotStudio is included in every Solo and Team subscription. Vault, schedules, run history, lifecycle hooks. Start a 30-day free trial.

View pricing