Skip to main content

Integrations

Roboticks plugs into the parts of your toolchain that need to participate in the V-model: the SCM that hosts your code, the requirements-management tool that owns the spec, the static-analysis tools you’ve already licensed, and the notification surfaces your team watches.

Inventory

GitHub App

The #1 integration. Webhook-driven test runs, Check Runs on every PR, OIDC for the CLI. Free across tiers.

BYO test-result ingest

Post JUnit-with-confirms XML, MCAP bags, and SARIF 2.1.0 reports straight from your own CI. Free on every tier — no per-connector fee.

Requirements (ReqIF)

Jama, Polarion, codeBeamer, DOORS. Round-trip via the OMG ReqIF standard. $149 / connector / month — this is the paid wedge.

BYO static-analysis

LDRA, Polyspace, Coverity. $149/connector/month — you bring the license, we ingest the findings.

Bundled OSS scanners

cppcheck, clang-tidy, Bandit, Semgrep, trivy, syft. Included in paid tiers, no extra charge.

Notifications

SBOM ingest

SPDX and CycloneDX SBOMs land in evidence packs.
The paid wedge is the requirements side, not the test-result side. Posting JUnit / MCAP / SARIF from your own CI is free; the BYO connector fee covers the vendor catalog (Jama, Polarion, codeBeamer, DOORS, LDRA, Polyspace, Coverity) where Roboticks maintains the parser and the round-trip.

How integrations relate to the platform

What each category is for

GitHub App

Your developers push code; the GitHub App posts a Roboticks Check Run on every PR with the coverage delta. Required for the smooth GitHub-native experience. Cross-link: GitHub App overview.

Requirements connectors (ReqIF)

The OMG ReqIF standard is the lingua franca for requirements interchange. Roboticks reads and writes ReqIF, so requirements authored in Jama, Polarion, codeBeamer, or DOORS round-trip without lock-in.
ToolPage
Jama ConnectJama
Polarion ALMPolarion
codeBeamercodeBeamer
IBM DOORS (Classic and Next)DOORS
A generic ReqIF guide covers the format details.

BYO static-analysis tool connectors

If your team has licensed LDRA, Polyspace, or Coverity, Roboticks ingests their reports and surfaces findings in the traceability matrix and evidence pack. $149 / connector / month. You keep your tool license — we link the findings.
ToolPage
LDRA Testbed (MISRA, coverage)LDRA
MathWorks Polyspace (Code Prover, Bug Finder)Polyspace
Black Duck CoverityCoverity
For any tool that emits SARIF 2.1.0 (Bandit, Semgrep, CodeQL, Snyk, etc.), use the generic SARIF ingest guide.

Bundled OSS scanners

Paid tiers ship with these scanners pre-wired. Enable them per-project; output lands in the matrix and evidence pack at no extra charge.
ScannerDomain
cppcheckC/C++ static analysis
clang-tidyC/C++ lint
BanditPython security
SemgrepMulti-language patterns
trivyContainer/image vuln scanning
syftSBOM generation (CycloneDX, SPDX)
Full list and per-tool config at OSS scanners.

Notification connectors

When something interesting happens — test failure, requirement gap appears, evidence pack ready, pinned standard amended — these route the event to your team’s preferred surface.
ChannelTrigger types it shines forPage
SlackAll — real-time visibilitySlack
PagerDutyCritical-only — on-call escalationPagerDuty
EmailDigests, off-hours notificationsEmail
WebhooksCustom routing into your own systemsWebhooks

SBOM ingest

Software Bills of Material in SPDX or CycloneDX land in evidence packs to satisfy supply-chain requirements (CRA, EU MR Annex IV.6). See SBOM and the OpenSSF SBOM reference.

The SARIF lingua franca for findings

Roboticks ingests SARIF 2.1.0 for any tool that emits it — that’s the path for arbitrary security and static-analysis tools beyond the named connectors. See SARIF ingest.

Setup pattern

Most integrations follow the same shape:
  1. Settings → Integrations in the dashboard.
  2. Pick the integration, click Add.
  3. For OAuth (Slack, GitHub) — approve in the third-party UI.
  4. For credential-based (PagerDuty key, Webhook URL) — paste and save.
  5. For BYO connectors (LDRA, Polyspace, Coverity) — also confirm the $149/connector line on your plan.
  6. Pick which event types route to this connector.
  7. Hit Test to send a sample.

Event types

These are the events that integrations can subscribe to:
EventFires when
test_run.completedA test run reaches a terminal state (pass or fail)
requirement.gap_openedA requirement transitions from confirmed → uncovered or stale
evidence_pack.generatedAn evidence pack is sealed for a release
standard.amendment_publishedA pinned standard receives an amendment (Standards-feed subscription required)
runner_pool.offlineA self-hosted pool’s last ONLINE runner heartbeats out
Each connector page documents which events it supports and what the rendered notification looks like.

Tier matrix

FreeTeamEnterprise
GitHub App
Slack / Email / Webhooks
PagerDuty
ReqIF connectors (Jama / Polarion / codeBeamer / DOORS)3 included, $149/extraBundled
BYO static analysis (LDRA / Polyspace / Coverity)$149 / connector / monthBundled
OSS scanners (cppcheck, etc.)
SBOM ingest (SPDX / CycloneDX)
SARIF 2.1.0 ingest
See Pricing for the canonical rate card.