You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Local-first homelab & developer tooling, built around orca — a single self-contained binary that orchestrates infrastructure, services, and AI agents, with everything else shipped as standalone orca plugins.
This page is generated by labs profile from each repo's own metadata (Cargo.toml description + [package.metadata.orca].category) and icon — never edit it by hand.
orca
orca — the core. A single Rust binary with an embedded web UI that acts as CLI, TUI, web server, and MCP server. It owns the domain model (containers, storage, namespaces, pods, notifications, models, agents) and loads plugins as ABI-stable cdylibs at runtime. Local models run by default; Claude is escalation-only.
Every plugin registers with orca through one generic surface — service.* (list, deploy, backup, restore, configure, status) — with rich, plugin-specific data returned in the typed service.status payload. Each repo below is also a standalone setup guide: you can deploy and operate the underlying service by hand, without orca.
Reproducible Linux gaming setup/restore: Steam, Heroic, Battle.net (NSL), gamescope, MangoHud, controller wake (Bazzite + CachyOS)
Developing a plugin
Each plugin is its own repo: a cdylib whose only orca dependency is plugin-toolkit, declaring its index metadata in Cargo.toml (description + [package.metadata.orca].category). See the orca plugin authoring guide, and docker or unraid as worked references.