Waydev connects AI vendor billing data to commit outcomes, dependent on each vendor's API staying available. Becoming AI-native starts earlier than that: whether the prompt and the harness around it are visible enough for an engineer to get better at either. Tetriz reads the prompt directly, independent of that dependency, and turns it into a coaching signal the engineer sees immediately.
Waydev's per-commit 'AI Checkpoints' percentage comes from vendor billing and usage data stitched to commits, a join Waydev hasn't published the methodology for. The Tetriz Desktop App captures the session directly: the prompt text, the iterations, the context an engineer gave the model.
Waydev's data depth depends on continued access to each AI vendor's admin/usage API, a dependency outside its own control. Tetriz reads the IDE session directly, without depending on any AI vendor's billing or usage API staying available.
The Tetriz Desktop App reads the session directly: no personal access token per AI vendor to request and rotate.
Not necessarily. Waydev's board-ready view of AI spend against merged-PR output across every vendor is a real strength some teams keep, adding Tetriz for the session-quality layer underneath.
The Tetriz Desktop App on each engineer's machine, plus admin-authorized access to GitHub, GitLab, or Bitbucket for pull-request correlation: no per-vendor personal access token to request and rotate.
That percentage comes from vendor billing and usage data stitched to commits. Waydev hasn't published the exact join methodology. Tetriz's session data comes from the IDE directly, so the two numbers answer related but different questions.