ServiceRadar

ServiceRadar

Developer Portal

ServiceRadar V2 documentation

API references, SDK guides, plugin packages, and the files needed to build and install ServiceRadar extensions.

API Reference Go SDK Repo Rust SDK Repo Contribution Guide

Getting Started

All developers

An orientation path for developers building their first ServiceRadar extension.

Start here if you are building your first ServiceRadar extension.

  • Understand the WebAssembly execution model and plugin packaging expectations.
  • Choose the Go or Rust SDK track that matches your team.
  • Prepare metadata required for registry submission and artifact signing.

Go SDK

Go

Go-focused SDK guidance for teams already building ServiceRadar integrations in Go.

Use serviceradar-sdk-go when you want the shortest path from plugin idea to a compiled WASM artifact.

Repository: https://github.com/carverauto/serviceradar-sdk-go

  • Scaffold the plugin with the official Go SDK.
  • Compile to WASM and package release artifacts for distribution.
  • Document installation and runtime requirements for operators.

Rust SDK

Rust

Rust-focused implementation guidance for plugin developers who want stronger low-level control.

Use serviceradar-sdk-rust when you want a Rust-native path to the same V2 plugin contract.

Repository: https://code.carverauto.dev/carverauto/serviceradar-sdk-rust

  • Build the plugin against the official Rust SDK.
  • Target the same V2 interface while using Rust-native tooling.
  • Publish source, release artifacts, and trust metadata together.

Plugin packages

Operators

What users can expect to find on plugin pages and download before installation.

Each plugin page should give you the files and details needed to evaluate and install the package.

  • Installation steps should be easy to copy into your own workflow.
  • Package files should include the manifest, schema, and artifact downloads when available.
  • Signature status should be visible so you can quickly tell whether a package is signed.
  • Official and community plugins should be clearly labeled.