Know what to build next
Stop guessing. Every proposal comes with the number or the line of code that shows why it matters.
For products built with v0
v0 got your idea live. Tracks keeps it getting better: it finds what holds your users back, proposes the fix with the numbers behind it, and builds what you approve.
Works with the GitHub repository your app already has. No code to write.
Stop guessing. Every proposal comes with the number or the line of code that shows why it matters.
Approve a card and it comes back as a change you can try, explained in plain words, ready to merge.
After a change ships, the number it was meant to move is read again. Improved, unchanged or worse: the card says which.
Why they fit
v0 can keep your project in a GitHub repository. Connect that repository, and Tracks reads the same code you see in v0.
If your app keeps its data in a Supabase project of your own, or another Postgres database you can give a read-only address for, Tracks reads it with single read-only queries, to see where people stop and whether a change worked. It cannot change a row. With the builder's built-in database, proposals rest on your code alone.
Every change is a pull request on your repository, described for people who do not read code. Once you merge it, you pull it into v0 from GitHub.
How to start
In v0, connect the project to GitHub and choose the account that will own the repository. In Tracks, choose that repository. Tracks can reach nothing else on your account.
If your data is in a Supabase project of your own or a Postgres database you can give a read-only address for, connect it, so proposals rest on what your users do and each change is measured afterwards. You can skip this and add it later.
A few minutes later, teams have formed around your product and the first cards are on the board, each with the number or the line of code behind it. Approve, ask, or reject.
What stays yours
Tracks works on the repository, beside you. Prompt as before; Tracks builds each change on the latest code.
Unless you turn that on. How much it may do alone is your setting: nothing, small low-risk fixes only, or everything that passes its critic.
Single queries in a read-only session, 100 rows at most, with a time limit. It has no way to change a row.
Every run records what it cost, and work stops at the daily budget you set.
Good to know. Tracks does not run inside v0. It runs as its own installation, set up by you or for you, and it sees what is in the GitHub repository: what v0 has not yet put there, it cannot read.
Questions people ask
Connect the repository, and the first proposals arrive a few minutes later.
v0 is a product of its own company. Tracks is not made by it or affiliated with it.