You want to build your own tools on top of the platform. Maybe a custom connector that talks to your internal systems, maybe an integration that automates something we haven't thought of yet. Here's the plumbing.
SDK for Rust
The foundation. When you're building a new connector from scratch, this is where you start.
- Type-safe communication — gRPC client/server code generated from protobuf definitions, so you can't accidentally send the wrong message
- Async with Tokio — everything is async from the ground up, with automatic reconnection and backoff built in
- Trait-based API — implement
BaseConnectorand the SDK handles registration, health checks, and lifecycle management - Focus on your domain — the SDK deals with platform plumbing so you can write the code that actually matters
Connector Architecture
The protocol. How connectors talk to hubs, how tools register with the platform, and how everything stays isolated.
- Desktop mode — connectors communicate with StrikeHub over Unix domain sockets. No TCP ports exposed, full process isolation
- Platform mode — connectors register tools with Prospector Studio over gRPC bidirectional streaming
- Dual mode — a single connector binary can run in both modes, adapting to its environment
- Crash isolation — each connector is its own process. If yours crashes, nothing else goes down
Connector deep dive →
Platform architecture →
How these fit into the platform
Everything you build with the SDK becomes a first-class citizen on the platform — your connector's tools show up in Prospector Studio where AI agents can call them, and in StrikeHub where users can interact with them directly. For the full picture, see How It All Fits Together.