For products built with Lovable

You shipped it in a weekend. Now give it a product team.

Lovable 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.

Know what to build next

Stop guessing. Every proposal comes with the number or the line of code that shows why it matters.

Say yes, and it is built

Approve a card and it comes back as a change you can try, explained in plain words, ready to merge.

See whether it worked

After a change ships, the number it was meant to move is read again. Improved, unchanged or worse: the card says which.

  1. In LovableYou describe what you want, and it is built
  2. On GitHubLovable keeps your code in a repository
  3. TracksReads code and data, proposes what to build next. You approve.
  4. On GitHubA pull request, checked, for you to merge
  5. In LovableThe change is in your project the next time you open it

Why they fit

What Tracks needs, and what a Lovable project has

Your code, on GitHub

Lovable can keep your project in a GitHub repository. Connect that repository, and Tracks reads the same code you see in Lovable.

Your data, when it is yours to share

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.

Changes that come back to you

Every change is a pull request on your repository, described for people who do not read code. Once you merge it, Lovable picks it up from GitHub by itself.

How to start

Three steps, and no code to write

  1. 1

    Connect the repository Lovable made

    In Lovable, connect the project to GitHub. Lovable makes a new repository for it in your account. In Tracks, choose that repository. Tracks can reach nothing else on your account.

  2. 2

    Connect your data, read-only

    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.

  3. 3

    Read the first proposals

    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

You stay in charge, and you keep building in Lovable

You keep working in Lovable

Tracks works on the repository, beside you. Prompt as before; Tracks builds each change on the latest code.

Nothing is merged without you

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.

Your data is only read

Single queries in a read-only session, 100 rows at most, with a time limit. It has no way to change a row.

You set what it may spend

Every run records what it cost, and work stops at the daily budget you set.

Good to know. Tracks does not run inside Lovable. It runs as its own installation, set up by you or for you, and it sees what is in the GitHub repository: what Lovable has not yet put there, it cannot read. Lovable makes a new repository for a project and cannot be attached to one you already have, and it keeps one branch in step at a time.

Questions people ask

Before you try it

Do I have to leave Lovable?
No. You keep building there exactly as you do now. Tracks works beside you, on the same repository.
Can it break my app?
Every change is a pull request with its checks, and nothing is merged without you unless you turn that on. A shipped change can be taken out again in one step.
I do not read code. Is this for me?
Yes. Each card says what is wrong and what will change for your users, in plain words, with steps to try the change yourself.
Is this made by Lovable?
No. Tracks is its own product and works with Lovable through GitHub. See the other builders it works with.

Put a product team on what you built

Connect the repository, and the first proposals arrive a few minutes later.

Lovable is a product of its own company. Tracks is not made by it or affiliated with it.