Traxiq

Documentation

Everything you need to ship faster with Traxiq: from first repo connection to team-wide traceability. Deep guides will expand here; app settings link to live configuration where appropriate.

Guides are versioned with product releases—see the Changelog for what changed.

View changelog →

Getting started

Connect GitHub, GitLab, or Bitbucket, run your first analysis, and review generated output.

Open →

PRD workspace

Drafts, approvals, drift detection, traceability matrices, and exports for compliance.

Open →

Test generation

How analysis maps requirements to suites, languages we support, and CI integration patterns.

Open →
In app

Git providers

OAuth scopes, webhook events, and organization-level installs for GitHub App users.

Open →
In app

API & keys

Authenticate programmatically, rotate keys, and respect rate limits.

Open →

Security & privacy

Data handling by plan, encryption, and subprocessors overview.

Open →

Getting started

  1. 1Create an account and sign in with your Git provider or email-based SSO where enabled.
  2. 2Install the integration at the organization or repository scope your policy allows.
  3. 3Trigger an analysis from the dashboard; review the structured PRD and linked test recommendations.
  4. 4Export or wire to CI using generated artifacts and API keys from Settings.

Tests & coverage

Traxiq detects frameworks and languages automatically for supported stacks (TypeScript, JavaScript, Python, Java, Go, and more). Generated suites aim for structural coverage and requirement traceability—use your review workflows before merging to main.

For enterprise VPC deployments, analysis stays inside your network; contact sales for architecture diagrams and compliance packets.

Need something not covered here?

Email support@traxiq.com with your stack and use case—we prioritize docs that unblock multiple teams.