Authorize a preview URL.
Find out what broke, and why.
Trialoom drives a real browser through your preview, then hands back what it observed step by step, the findings worth fixing, and a replay that opens at the first failure. No wallet, no deposit, nothing about crypto to learn.
Public signup is being prepared. The example workspace is open to everyone in the meantime, with real recorded evidence in it.
The check you skip when the release is rushed
A founder or a two-person team ships a web app with no QA. After every change the check is manual: open the preview, click through signup, click the invitation, click checkout, and hope nothing else moved. It costs twenty to forty minutes a release, and it gets skipped exactly when the release is hurried — which is when something breaks.
What comes back
What it observed
Every step in order, with the response codes, counts and navigation outcomes it actually checked. Not a pass-or-fail badge.
The findings
Each with steps to reproduce it, pinned to the exact build it was found on, and waiting for your review rather than filed on your behalf.
A replay
A recorded walkthrough that opens at the first failure, with page contents and private values removed before anything is stored.
Trialoom buys what it does not own
It runs no model of its own. When a test finishes, a narrow summary of what it observed goes to an inference service and is paid for per call in stablecoin over x402 on Celo, from Trialoom’s own wallet. You never meet a paywall and never hold a token. The payment path is built and verified against the live gateway, but this deployment has no sponsor wallet configured, so nothing is being bought yet.
What leaves your project
At most twelve closed observations per report: a status code, whether two counts agreed, whether a navigation arrived, how many requests were denied. No URL, no page text, no raw trace, no account, no credentials, no source. The input is hashed and the report is bound to that hash, so an explanation can always be traced back to the evidence it was bought for, and never to your data.
Where this is today
- Account signup
- Being prepared
- Automatic testing
- Not available in this deployment
- Paid explanations
- No wallet configured yet
Read from this deployment’s own configuration rather than written into the page.