scout is free and open source. Producing high-quality scenarios — identifying the right user flows, annotating bbox locators precisely, tuning diff_ignore.json so the report surfaces real drift — takes expertise and time. BoxProbe does that work as a service.
Your product has integrations, mobile apps, or third-party consumers that depend on stable response shapes. A green E2E suite isn't enough — one undocumented field added in a release breaks downstream.
Building UI-driven regression coverage from scratch — identifying flows, annotating elements, tuning noise rules — is multi-week work. You'd rather get scout-runnable scenarios in your repo and move on.
Accepting BoxProbe's scout-runnable test code into your repo is a runnable asset. BoxProbe-hosted analysis pages give your release notes external evidence without you building dashboards.
All modes deliver scout-runnable Python scenarios as a primary artifact. The difference is depth and continuity.
We scope a flow set, record scenarios against your application, produce scout-runnable test files, tune diff_ignore.json against a real baseline-vs-target pair, deliver the suite into your repo as a PR. You own it from there.
Typical fit: teams shipping a major release and wanting drift coverage in place beforehand.
Authoring + maintenance over time. New flows added each release, broken locators re-annotated, diff_ignore.json kept honest as your API evolves. We track your release cadence; scenarios stay green against intentional changes and red against real regressions.
Typical fit: products where API drift coverage is permanent, not a one-time push.
Same authoring + maintenance, plus we host the analytical surface on boxprobe.com/cases/<your-project> — release-to-release drift reports, scenario catalog, badge for your README, public HTML diff anyone can link from issues. Your repo gets the runnable asset; the public gets the release intelligence.
Typical fit: OSS projects where the audience cares about release stability and your changelog wants external evidence.
We don't meter per-test-run or per-credit. Engagements are scoped:
scout is the open-source executor — what runs scenarios and produces reports. Argus is the proprietary recording and annotation pipeline BoxProbe uses internally to produce scout-runnable scenarios efficiently. Argus is not sold as a product right now; it's how we deliver scenario authoring at scale. If you have a use case that needs Argus directly (rather than the scenarios it produces), email us — that's a different conversation.
Share a URL, a few user flows you care about, and your release cadence. We'll propose a scope and a quote within a few business days.
Email [email protected]