How it works

One card, from a first look at your product to a measured result

Tracks reads your product, proposes what to build with the evidence behind it, builds what you approve, and checks afterwards whether it worked. Here is that loop, step by step.

  1. 1

    It reads your product

    It reads your repository, through the GitHub connection you make or a token you give it. If you connect your database, it reads it through single read-only queries, with a limit on rows and on time. It writes down what the product is, who uses it and where it stands.

  2. 2

    It forms teams

    Each team owns one area of the product and is judged on KPIs measured from your own data, each with a target. You can rename a team, redirect it, switch it off or add your own.

  3. 3

    A team proposes, with the evidence

    Every card says what is wrong, what to build, and the number or the line of code behind it. A critic checks each one against the evidence and drops what does not hold up before it reaches you.

  4. 4

    You decide

    Approve it, ask the team a question, or reject it and say why; the team remembers the reason. How much it may do without you is your setting, per product and per team: nothing, small low-risk fixes only, or everything that passes the critic.

  5. 5

    It builds, and opens a pull request

    An approved card becomes a pull request on your repository. The change is described for people who do not read code: what is different for someone using your product, and how to try it. When a check fails, the builder reads why and fixes it. Nothing is merged without you unless you turn that on.

  6. 6

    It measures

    After a change ships, the KPI it was meant to move is read again and the card says what happened: improved, unchanged or worse. A change that did not help is recorded too, and a shipped change can be taken out again.

Safety

What it cannot do

Your code and data

What leaves your systems

To the AI provider

The parts of the code the agents read, the results of their queries, feedback you paste in, the text of cards, and the end of a failed check's log. It is sent with your own key, under your own agreement with that provider. The results of queries can include your users' personal data.

To GitHub, and to you

Branches, pull requests and merges on the repository you connected. If you set a chat webhook or a mail server, the titles of cards, counts and spend go there to tell your team.

Nowhere else

Tracks runs as your own installation. It has no analytics and no connection to whoever wrote it. What it keeps (the board, the runs, credentials in encrypted form, a checkout of your repository) stays on the volume you attached.

Put a product team on your product

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