Docs / Service catalog

Service catalog

A reference for every native service that ships with Wylde. Every service exposes a Windows named pipe and an HTTP fallback on the listed port.

Core

Service	Port	Pipe	What it does
`security-api`	5000	`wylde-security-api`	Unified gateway — TLS, IP whitelist, rate-limit, proxy to tool-registry.
`tool-registry`	8004	`wylde-tool-registry`	Service discovery, health checks, execution routing.
`tool-runner`	8001	`wylde-tool-runner`	Sandboxed Python / bash executor and file I/O (6 tools).
`wylde-launcher`	8012	`wylde-launcher`	Native process manager — spawns every service on startup.
`wylde-sysmon`	9100	`wylde-sysmon`	System metrics (CPU / RAM / GPU / disk) plus diagnostics & backup.
`device-gate`	7000	`wylde-device-gate`	Per-device approval flow for remote access.

Data

Service	Port	Pipe	What it does
`wylde-rag`	8008	`wylde-rag`	Hybrid vector + full-text RAG with HyDE, citation, and graph-enhanced retrieval.
`wylde-voice`	8009	`wylde-voice`	STT (Whisper) + TTS (Kokoro-ONNX), NPU runtime, VAD.
`wylde-caption`	8015	`wylde-caption`	LoRA dataset captioner — Florence-2 (default) and Qwen2.5-VL backends, image & video.

Orchestration

Service	Port	Pipe	What it does
`wylde-orchestrator`	8010	`wylde-orchestrator`	Graph engine, checkpointing, SSE, gates, budgets, model registry. Hosts Agent Orchestra.
`wylde-trainer`	8013	`wylde-trainer`	LLM fine-tuning via LLaMA-Factory; 19 tools, cooperative VRAM scheduling.
`wylde-improve`	8016	`wylde-improve`	Self-improvement loop: scoring, daily consolidation, weekly SFT/DPO curation, skill A/B testing.

Network

Service	Port	Pipe	What it does
`n8n-service`	5679	`wylde-n8n-service`	Flask adapter over the n8n REST API (6 tools).
`webcrawler-service`	8003	`wylde-webcrawler-service`	HTTP fetch, scrape, DOM extract (3 tools).
`wylde-vpn`	8020	`wylde-vpn`	WireGuard peer management, WyldeLink, STUN / TURN, DNS stub.
`fletch-web`	3000	—	nginx serving the Svelte SPA; LAN / WyldeLink gateway (only on when Remote Access is enabled).

Graph

Service	Port	Pipe	What it does
`wylde-graph`	7687 (Bolt)	`wylde-graph`	Neo4j-compatible graph; named pipe primary, Bolt fallback. Drop-in Memgraph option.

Third-party (native)

Service	Port	What it does
`Ollama`	11434	Inference engine; managed externally, accessed by the orchestrator.
`n8n`	5678	Workflow engine; only accessed via the `n8n-service` adapter.

Docker (optional profiles)

Service	Profile	What it does
`Memgraph`	`--profile graph`	Optional drop-in graph backend; Bolt + Cypher compatible.
`coturn`	`--profile relay`	TURN relay for `wylde-vpn` WyldeLink remote peers.

All host bindings are loopback-only (127.0.0.1) except fletch-web, which binds 0.0.0.0:3000 intentionally — it is only started when Remote Access is enabled and WyldeLink gates network reach. Mobile clients connect through the WyldeLink WireGuard tunnel; the gateway binds to the tunnel IP only, with per-peer bearer auth on top. Routes are documented openly — see the security model.

Adding a service

A new service needs to provide three endpoints:

GET  /health         → {"status": "healthy"}
GET  /api/tools      → tool definitions
POST /api/<tool_id>  → executes the tool, returns the result

Then register the named pipe at startup:

from shared.ipc import register_pipe
register_pipe("wylde-my-service")

Add the service to tool-registry's discovery list and to wylde-launcher's process manifest, drop a docs/_data/components/my-service.yaml entry, and run python docs/generate.py. That's the full loop.