koi-embedded

Embed local network discovery, DNS, health, and TLS directly in your Rust application.

Overview

koi-embedded lets you embed the full Koi stack — mDNS discovery, DNS resolution, health monitoring, TLS proxy, certmesh, and UDP bridging — inside your own Rust application. It provides a Builder for configuration and returns typed handles (MdnsHandle, DnsHandle, HealthHandle, etc.) for interacting with each capability, plus a KoiEvent broadcast stream for reacting to system-wide events.

Usage

use koi_embedded::{Builder, ServiceMode};

let koi = Builder::new()
    .mode(ServiceMode::Standalone)
    .build()
    .await?;

// Register a service
koi.mdns().register(payload).await?;

// Subscribe to events
let mut rx = koi.subscribe();
while let Ok(event) = rx.recv().await {
    println!("{event:?}");
}

Cargo features (lean builds)

Three heavy, version-locking backends are gated behind default-on features. A default dependency is unchanged; a lean consumer opts out, and re-arms à la carte:

Feature	Default	Compiles in	Off → fallback
`docker`	on	`bollard` Docker/Podman client (`=`-pinned stubs)	runtime backend → `BackendUnavailable`
`keyring`	on	OS keychain / Secret Service / D-Bus	vault uses its passphrase backend
`qr`	on	`qrcode` + `image` PNG codec	enrollment returns the `otpauth://` URI text

# default — everything
koi-embedded = "0.4"
# lean — no bollard, no OS-keychain/D-Bus, no image codec
koi-embedded = { version = "0.4", default-features = false }
# à la carte (also: features = ["full"])
koi-embedded = { version = "0.4", default-features = false, features = ["docker"] }

These are compile-time choices, distinct from the runtime capability toggles on Builder (which compile everything and just don't start it). See the embedded guide and ADR-014.

Part of Koi

This crate is part of the Koi workspace. See the main repository for architecture details and the full crate inventory.

License