Free tools for changing a live product
Free tools for product teams and for apps built with AI: analyse a landing page, check a site before launch, explain a pull request, write a PRD from your real codebase, and find out why an AI-built app broke. No signup.
For product and marketing teams
Read a page the way a visitor does, check a site before it goes live, understand a pull request before you approve it, and write the spec for a change from the real codebase.
Why isn't this page converting?
Landing page analyzer. Loads the page on a phone and a desktop, checks what a visitor sees first, and returns prioritised findings with the evidence and A/B tests worth running.
Loads the public page · nothing is clicked or changed
Open the toolWhat exactly should we build?
PRD generator. Turns a change you want into a PRD with scope, acceptance criteria and edge cases — and, from a public repo, the files it will actually touch.
Reads your description and a public repo's file list
Open the toolIs this site ready to launch?
Launch checklist. Runs the pre-launch checklist against the live or staging address — indexing, metadata, mobile, forms, analytics, legal pages — and gives a go or no-go.
Reads the public site · nothing is submitted
Open the toolWhat does this pull request actually change?
Pull request explainer. Explains a public GitHub pull request in plain English: what users will notice, what is risky, and what to test before you approve it.
Reads a public pull request · nothing is posted
Open the tool
For apps built with AI builders
For apps made with Lovable, Bolt, v0 or Replit: find out why one broke, whether a key is safe to expose, which tables anyone can read, which variables reach the browser, and what to tell a coding agent about the repository.
Why is my app broken?
Broken-app check. Reads your published app the way a visitor would and names the most likely cause, with the evidence behind it.
Reads your published app · no access to your code
Open the toolWhat does this error mean?
Error lookup. Paste the error your app is showing and get it in plain English, with what usually causes it in an AI-built app.
Runs in your browser · nothing is sent anywhere
Open the toolIs this key safe to expose?
Key checker. Tells you whether a key is meant to be public or must never leave your server. Decoded in your browser.
Runs in your browser · nothing is sent anywhere
Open the toolCan anyone read my Supabase tables?
RLS checker. Asks your Supabase project, with its public key, which tables return rows to someone who never signed in.
Read-only, from your browser · row counts only, no row values
Open the toolWhat should my AGENTS.md say?
AGENTS.md generator. Reads a public repository and drafts a short AGENTS.md from its real commands, checks and variables, plus a CLAUDE.md that imports it.
Reads a public repo's file list and manifests · nothing is written
Open the toolWhich variables reach the browser?
Variable checker. Shows which of your environment variables your framework bakes into the public bundle, and which stay server-side.
Runs in your browser · nothing is sent anywhere
Open the tool
Finding it is the easy half
Plenty of tools will tell you what is wrong with a page, a launch or an app. Almost none of them will change it — you are handed a report and left to find someone who can act on it: a ticket that waits for next sprint, an agency’s week, a couple of thousand dollars.
These tools are free and need no account because the answer is not the valuable part. Refinar is what happens next: it reads your repository, makes the change in a live preview, and says out loud which changes a person should approve before they ship.
App built with Lovable, Bolt or v0 and not sure what broke? Start from the symptom.