redevops-io/agentic-os

**The control plane for the redevops.io Agentic Business OS.**
*Run your whole business as a fleet of agents — on hardware you own, with the cheapest model that's good enough for each task.*
 ·  self-hosted  ·  no lock-in  ·  source-available
> **🚀 NVIDIA Inception Program Member** — ReDevOps is a member of the NVIDIA Inception Program, supporting startups advancing AI and accelerated computing. Membership provides access to NVIDIA technology, technical resources, and the startup ecosystem. It does not imply product endorsement by NVIDIA.
---
What this is
The reference apps each solve one business pain — payments,
support, books, compliance,
analytics, marketing, social,
competitive intel, security — and more under apps/.
**agentic-os is the layer that runs them all as one coordinated fleet.** It is the *operating system* of the
business: a registry of modules, an orchestrator that gives each one its own agents, a cost-aware LLM router, a
shared business context, and a single control plane with human-in-the-loop approval for anything that moves money,
touches compliance, or changes infrastructure.
> **control-tower is the dashboard you look at. agentic-os is the kernel that runs underneath it.**
It's also how redevops.io runs *itself* — headcount-light, agent-heavy — which is the proof that it scales.
Why it exists
A small company today glues together five disconnected AI SaaS tools, each a silo with its own data and its own
premium API bill. agentic-os replaces that with **one fleet, your data, your hardware**:
- **One control plane** — deploy, start, stop, and observe every module from one place.
- **Cost-aware routing** — every agent task is sent to the cheapest model that can do it well: a local
llama.cpp/ollama model on hardware you own for the bulk of the work, a premium API only for the
hard 5%. That per-task routing *is* the product.
- **Cross-module workflows** — a new signup isn't five disconnected events; it's one workflow where billing sets up
the subscription, support sends onboarding, books records the entry, and compliance files the consent record.
- **Human-in-the-loop where it matters** — money, compliance, and infra actions pause for one-click approval.
- **Fine-grained access control** — a permissions plane grants each app/role/user read/write on a database, table
or corpus, sliced by **row scope** and **column mask**; set it up and preview it live at /permissions (grants
AES-GCM–encrypted at rest, gated write API). See docs/permissions.md.
Beyond the fleet: Projects, Integrations, Sidekick & the Agent Gateway
The fleet/router/control-plane above is the kernel. On top of it the current product surface adds:
- **Projects + Sidekick** — a self-host web app (agentic_os/projects_api.py
serves the UI + API on one origin). **Projects** is the control plane (missions · workflows · attention ·
approvals · audit); **Sidekick** is the conversational Mission Supervisor *and* an in-product Q&A expert that
answers, from a curated + sourced knowledge base with a grounded local-model fallback, how credentials are
handled, where data is processed, how execution is governed, and how the components work
(sidekick_assistant.py ·
stack_knowledge.py; GET /api/sidekick/help). A deployment can offer just a
subset of apps via $PROJECTS_APPS.
- **Integration Plane + Connect Compiler** — describe an integration in plain language; the wizard interprets, you
confirm, the runtime compiles it into a governed connector (agentic_os/integrations/).
Connector adapters live in redevops-connectors (HubSpot,
Stripe, Polar, Gmail, Google Calendar, Slack, WhatsApp Business, Klaviyo, Postiz, Ayrshare, Blotato). Credentials