SDKs & Integrations ​

Obvyr provides helpers for common stacks so you can start collecting test execution data with minimal setup. For stacks not yet covered, the /collect API is always available for custom integrations.

Obvyr CLI ​

The primary SDK for most stacks. The CLI wraps any command — just prefix your existing test runner invocation with obvyr-cli and your data starts flowing immediately. No build system changes required.

  • Works with any test runner or command
  • Supports all major CI/CD platforms
  • Configurable via environment variables or .env file

→ CLI Reference · CLI Configuration

Gradle Plugin ​

The recommended integration for JVM/Gradle projects. The plugin hooks directly into your test tasks — no wrapper, no changes to how you invoke Gradle.

  • Automatic submission after every Test task
  • Full DSL configuration with environment variable fallbacks
  • Silent by default; never blocks your build

→ Gradle Plugin

Direct API ​

For custom integrations, unsupported stacks, or when you need full control over what is submitted. Build your own integration using the /collect endpoint directly.

  • Submit any command execution data
  • Full control over archive contents and metadata
  • Useful for build systems, language runtimes, or homegrown tooling

→ Collect API Reference

Using a stack we don't cover yet?

We want to support your tools. If you're on a stack without an Obvyr integration — .NET, Ruby, Rust, Bazel, or anything else — raise a request on our GitHub issue tracker or get in touch via the support link in your dashboard.