ServiceRadar

ServiceRadar

Developer Portal

V1

ServiceRadar V1 developer documentation

Version 1 focuses on the WebAssembly plugin contract, SDK quickstarts, trusted plugin distribution, and the metadata required to publish entries into the public registry.

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.

  • 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 V1 plugin contract.

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

Architecture

Operators

Cross-cutting documentation about the system model behind the developer portal.

The developer portal is more than a docs site.

  • Plugin metadata, signatures, and release links are surfaced directly in the UI.
  • The portal is deployed through Kubernetes with GitOps-managed overlays.
  • Authentication boundaries are designed around Authentik and GitHub-backed identity.