Opportunities › Unified test automation across web, mobile, and APIs › Proposed app
Tracewright
One test language for web, mobile, API and LLM checks, run on your own servers
- Score
- 35
- confidence 45
- Evidence
- 4
- items on the page
- Rivals
- 1
- named in sources
- First version
- 70 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2004
- Mature market · AI estimate
ScreensConcept
Desktop app: QA teams write and review complex multi-layer test scenarios, manage repositories, and analyze detailed run history—development and analysis work done at a workstation. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Suite overview
Last run 12 min ago94%
About this appAI proposal
Tracewright lets QA and development teams write API, web, mobile, messaging, data and LLM tests in one plain scenario format, kept in one repository. A checkout flow can call an API, drive a browser, confirm a message arrived and check a database row in a single scenario.
It is built for teams that keep separate tools and languages for each layer and lose time to context-switching and duplicate upkeep. Runners can be hosted on your own infrastructure, so test data and credentials stay where your compliance rules need them.
The web app is the control room: browse scenarios, start runs, read results and share a failing run with a link. Runners do the work on your machines.
- Tagline
- Write the test once. Run it across every layer, on your own ground.
- Voice
- PlainPreciseCalm
- Why this name
- A wright builds things; a trace is the path a test follows. Together: one builder of tests that follow a user path through every layer.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
One scenario format for every layer
Write API, browser, mobile, message, data and LLM steps in the same file and syntax. No second language to learn.
No member yet
Mixed-layer scenarios
Chain steps across layers: create an order by API, confirm it in the web UI, then check the database row and the email sent.
No member yet
Self-hosted runners
Run tests on your own servers or CI machines. Only results go to the control room, and you choose which fields.
No member yet
LLM checks beside normal tests
Assert on model answers with rules such as must-contain, must-not-contain, format, and a pass rate over several runs.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#1F6F5CPine · primary#F6F3ECPaper · surface#1F2A2EInk · text#E0A030Amber · accent#3B5B92Slate blue · data#B5483ABrick · failure status
Typography
Aa
Tracewright
PricingAI proposal
The material gives no competitor prices. It only suggests per-seat or volume licences, a free tier and an enterprise self-hosted licence. These tiers are a starting point to test.
Solo
Free
- 1 user
- 2 self-hosted runners
- 7 days of run history
- All test layers
Team
$39 a month
- Up to 10 users
- 10 self-hosted runners
- 90 days of run history
- Shareable reports
- Suite import
Business
$149 a month
- Up to 50 users
- Unlimited runners
- 1 year of run history
- Single sign-on
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Shared outputs. Failed-run reports open by link for developers, product managers and contractors who do not use Tracewright. Each report shows the product name and a link to the scenario file.
- Do they become customers?
- Report readers are often developers on the same team who could become seat holders, but they may only look once. Test whether shared reports lead to new sign-ups inside the same company.
- First customers
- QA leads at companies of 20 to 200 engineers that test API, web and mobile with separate tools and need self-hosting for compliance, such as fintech or health software.
- Where to reach them
- Open-source communities: Post worked examples of mixed-layer scenarios on GitHub discussions, testing forums and QA meetups.
- Direct outreach to QA leads: Message QA leads on LinkedIn who list several test tools, and offer to port one flaky suite.
- Technical blog: Publish guides on testing LLM features and self-hosting test infrastructure.
- First milestone
- Five teams in one vertical each move a real suite onto Tracewright and three agree to pay for the Team tier.
Why people already pay for this
- VerifiedGitHub repository gained 1773 stars in 667 days
- Public claimPlatform supports testing across multiple layers with a single test language
- Public claimSelf-hostable architecture is available, addressing infrastructure control and compliance concerns
- AI inferenceProject has active community engagement and sustained development
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Test runner agentSelf-hosted runner service in a containerTests execute on customer machines and report results back to the control room.
- This app · Browser and device automationOpen-source browser and mobile driversScenarios need to drive web pages and mobile apps from the runner.
RisksAI inference
- TechnicalCovering API, web, mobile, messaging, data and LLM in one format is a large surface. A first version may need to ship API plus web and add other layers one at a time.
- CommercialTeams have working suites and may resist migrating. The material shows interest in a similar open project but gives no proof that teams pay for it.
- Intellectual propertyThe signal names an existing project with a single test language. The scenario format and name must stay clearly different, and any reused open-source code needs licence review.
- PlatformMobile testing depends on emulators, real devices and OS-vendor tooling that change often, which raises upkeep for runners.
- AILLM outputs vary between runs, so pass-rate checks can be noisy or costly. Users may not trust them without clear guidance.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.