Integrations

VEKTIS measures real-world impact, which means it needs two streams of input: events from the application your customers use, and work signals from the place your team commits code. This section covers both — start with the tracker if you haven’t sent any events yet, and reach for the code-repository integration when you want VEKTIS to suggest dev items based on what your team actually shipped.

Send events from your app

The VEKTIS tracker is a small browser SDK that streams events from your application to VEKTIS. Without it, post-release metrics can’t be calculated automatically. Most teams install it once on their main web frontend and let VEKTIS handle everything else.

VEKTIS Tracker

Framework-specific install guides covering the major web frontends and a vanilla / CDN drop-in. Includes Content Security Policy setup, logout handling, and troubleshooting. Tracker integration guide →

Connect your code repository

VEKTIS can also read merged pull requests from your code repository and turn them into dev item suggestions, so you don’t have to remember which features deserve to be measured. The classifier reads PR labels and conventional-commit prefixes, then surfaces the trackable types (features, improvements, bug fixes) for you to accept or skip.

GitHub

Connect a repository, choose your release branch, and review PR-based dev item suggestions. Includes setup, classification rules, and troubleshooting. GitHub integration guide →

Faster path: guided install

If you use Claude Code, the vektis-bootstrap skill walks you through tracker installation end-to-end — framework detection, authentication, env vars, and init code with diff confirmations. Run claude /vektis-bootstrap in your project, or read the skills install guide first.