A pilot for your team
The pilot is the shortest path to a decision: one team, one repository, five bounded tasks from your own backlog. You get back a draft pull request per task with commits per step and a check report, plus the numbers that matter for the decision: review effort and cost per task.
One repository with a reproducible build and five small tasks that have a clear finish: a maintenance change, a regression test, a bounded bug fix. For each task, one sentence on what done looks like and how your team would handle it today.
If your stack is not Java with Spring Boot yet, we check together before the start whether the verification environment has the tools your project needs. A task whose tests cannot run would only produce an unverified result, and that is not a fair pilot.
Per task a draft pull request in your repository: one commit per work step, each naming the task it came from, plus the run report with the checks that ran. Review effort and cost per task come from the cockpit, not from a slide.
Failed attempts stay in the comparison. The pilot is meant to make a decision possible: continue, close a prerequisite first, or stop. All three are good outcomes.
Before the start we agree on repository access, the model provider that may process your source code, who reviews and who pays what. Scope and dates are fixed before the first task runs.
Hosted in Switzerland on the Infomaniak Public Cloud. Source code in model requests goes to the provider you choose, with your own key if you want. The data route is one page of the agreement, not a surprise afterwards.