git-fabric builds composable fabric apps for Git-native infrastructure. Each app is a standalone, independently deployable module that handles one domain well and connects to everything else through the gateway. Every app exposes its capabilities as MCP tools, so Claude, git-steer, Cortex and GitHub Actions can all consume them the same way.
The twist is the routing. The fabric-sdk decides, BGP-style, whether the fabric already knows the answer, through its apps and a layer of small specialized local models, or whether it genuinely needs Claude.
| App | What it covers |
|---|---|
aiana |
Semantic memory, session context and cross-project recall |
chat |
AI conversation sessions, semantic history search and context threading |
cloudflare |
DNS, zones, cache and KV |
cve |
CVE detection to remediation: scan, enrich, triage, fix |
git |
Commit, push, branch, PR and repo management |
k8s |
Cluster, pods, deployments, services and logs |
proxmox |
VMs, containers, nodes, storage and snapshots |
sandfly |
Agentless Linux intrusion detection and incident response |
tailscale |
Devices, DNS, ACLs and auth keys |
unifi |
Hosts, sites and devices via the UI.com Cloud API |
| Repo | Role |
|---|---|
sdk |
BGP-style routing for fabric agents: route locally first, Claude only when nobody else can answer |
gateway |
Routes, connects and orchestrates fabric apps |
fabric-ctrl |
Zero-trust control plane: GitHub App identity, security automation, MCP org tooling |
fabric-review |
Automated PR review engine for the ecosystem |
fabric-forge |
k3s cluster + Helm charts for the Fabric-SDK runtime, one script |
pipelines |
Five scheduled pipelines composing gateway tools into homelab intelligence |
terminal |
Claude Code + tmux + kubectl in a persistent container |
yt-adr-feed |
YouTube transcripts into Qdrant and an ADR pipeline, deterministic |
adr |
Global Architecture Decision Records |
fabric-state |
CVE queue state and scan history for fabric-ctrl |
Fourteen Ollama models, each specialized for one API, answer locally before anything escalates to Claude.
| Repo | Model | Specialty |
|---|---|---|
| aiana-vllm | AIANA-Ops | semantic memory |
| cloudflare-vllm | Cloudflare-Ops | Cloudflare v4 API |
| cve-vllm | CVE-Ops | NVD / GHSA / CISA KEV |
| fabric-invoke-vllm | fabric-invoke | orchestration runtime |
| fabric-router-vllm | fabric-router | fabric-sdk meta-routing |
| git-steer-vllm | git-steer-Ops | git-steer internals |
| github-vllm | GitHub-Ops | GitHub REST API |
| k3s-vllm | k3s-Ops | k3s / Kubernetes API |
| n8n-vllm | n8n-Ops | n8n REST API v1 |
| proxmox-vllm | Proxmox-Ops | Proxmox VE API |
| qdrant-vllm | qdrant-fabric-Ops | Qdrant vector ops |
| sandfly-vllm | Sandfly-Ops | Sandfly Security v4 API |
| tailscale-vllm | Tailscale-Ops | Tailscale v2 API |
| unifi-vllm | UniFi-Ops | UniFi API |
- One app, one domain: each fabric app handles a single concern end to end.
- Adapter interfaces: apps define what they need (
GitHubAdapter,StateAdapter); consumers provide implementations. - Layers, not monoliths: every app is built from composable layers (detection, intelligence, decision, action, state).
- MCP-native: every app exposes its capabilities as MCP tools.
- CLI + Actions: every app has a CLI for local use and Actions workflows for automation.
Built by ry-ops · consumed by git-steer, Cortex, and whatever comes next