Skip to main content
Modulo

Frequently Asked Questions

What is Modulo?

Modulo is the self-hosted AI-control system of record for agentic Software Development Lifecycle (SDLC) pipelines. You define the pipelines and policies; Modulo handles pipeline execution, immutable audit, and human-in-the-loop (HITL) governance, proving who approved what agent change across every tool. See What is Modulo?.

Is it self-hosted?

Modulo runs on your infrastructure via Docker Compose. It sends no telemetry and no data has to leave your network, so it is air-gap capable.

Which tiers are there, and what does each include?

The Community tier (Personal) is free and self-hosted: unlimited pipelines, team collaboration, per-agent token budgets, a pipeline spend circuit breaker, an org-wide pause (kill switch), community support. Team is a paid feature-gate add-on ($6,000/yr pre-GA founding price, rising to $12,000/yr at v1.0; existing subscriptions keep the $6,000 price) that adds single sign-on (SSO), Security Assertion Markup Language (SAML), role-based access control (RBAC), audit exports, organization and team spend limits, a budget overview, and a cost breakdown. Team is a self-hosted feature unlock, separate from any Enterprise agreement, and it comes with no uptime service-level agreement (SLA) and no contractual SLA.

What support is included?

A Team subscription includes direct, asynchronous support from the team, with a response within 24 hours, seven days a week. There are no sales calls and no account managers. Product-side defects (bugs in Modulo itself) are fixed and shipped in a release. There is no uptime SLA and no contractual SLA: Modulo is self-hosted and you operate the infrastructure. Self-hosting and third-party issues are covered by documentation and the community.

How are credentials handled?

Modulo encrypts connector credentials at rest with Fernet and scopes them per run. See Connectors.

Which large language model (LLM) providers are supported?

Anthropic (Claude), OpenAI (GPT-4o, o-series), and any OpenAI-compatible local endpoint (Ollama, vLLM, LocalAI). You can mix providers within the same pipeline. See Model Backends.

Which tools can I connect?

Modulo ships 43 connector types covering source control, CI/CD, ticket tracking, messaging, monitoring, security scanning, and more, including GitHub, GitLab, Notion, filesystem, and any REST API. See Connectors.

Can I require human approval before agents act?

Yes. HITL checkpoints pause pipeline execution for human review. See Human-in-the-Loop.

Is there an audit trail?

Modulo keeps a tamper-evident log of every governance event: run start, agent dispatch, human decision, gate outcome, plus a full record of every agent run’s reported output. Export for compliance reviews or replay for debugging. See Architecture for the audit logger layer.

What stage is this?

Pre-release alpha. The platform is functional and being used in development, and breaking changes may occur. The Community tier is free; the Team tier is available as a paid, self-hosted feature add-on.

How do I get started?

See the Installation guide. Clone the repo and run docker compose up -d to start everything: Postgres, Redis, the API, the frontend, and the queue workers. The first run builds the Docker images.

Can I use my existing agents?

Yes. A node in a Modulo pipeline can declare a typed input and output schema (schemas are opt-in), and where one is declared, any runtime that honors that contract can fill the node. Modulo ships CI-runner connectors for the continuous integration (CI) system that already runs your agents, including CircleCI, GitHub Actions, GitLab CI, Buildkite, Jenkins, TeamCity, and Azure Pipelines, and wiring a pipeline node to dispatch to them is in development. Your service can hand work back through a webhook trigger. The code runs in your infrastructure; Modulo governs each handoff and records the result. See Modulo with your existing agent runtimes and Connectors.

Can I drive Modulo from a Model Context Protocol (MCP) client such as Claude Desktop or Cursor?

Yes. Modulo runs a Remote MCP server. Add it to your client using the URL and configuration snippet shown at Settings > MCP, and authenticate with an MCP API key or an OAuth client application. From MCP you can list pipelines, trigger runs, read run output, browse the library, and act on human-in-the-loop gates. Gates marked human-only require a credential linked to a human account: a browser sign-in, or a local MCP client holding a consent-derived OAuth token for a human member. An MCP API key or a service-account credential cannot decide one. MCP is included in the free Community tier. See MCP and Human-in-the-Loop.

Do I have to replace my CI/CD tooling?

No. Modulo governs the agent steps and leaves your build and test tooling in place. CI-runner connectors for CircleCI, GitHub Actions, GitLab CI, Buildkite, Jenkins, TeamCity, and Azure Pipelines are in place today; wiring a pipeline node to dispatch to one, wait for it, and fold the outcome into the same governed run is in development. See Connectors.

Where does agent code actually run, and who controls it?

You choose per environment profile. The local provider runs agent commands as subprocesses on the Modulo host with no sandboxing, which suits evaluation and solo development. The runner_docker provider gives each workspace an ephemeral hardened container, and you can point it at a Docker engine you own, including a remote host on your network. The e2b provider gives each run an isolated sandbox. The kubernetes provider runs each workspace as a long-lived pod in your cluster, hardened with a non-root user, a read-only root filesystem and dropped capabilities, and registered when MODULO_KUBERNETES_ENABLED is set. Pipelines are portable across providers. See Execution Environments.

How do I control agent spend?

Community includes per-agent token budgets that hard-stop an overspending run, a per-pipeline monthly spend circuit breaker that pauses that pipeline’s triggers when it trips, and an org-wide pause that stops all new trigger-initiated runs. Team adds organization-level and team-level daily spend limits, a budget overview with alert thresholds, a monthly cost breakdown, and spend-anomaly detection. See Cost Management.

What happens when an agent fails or produces bad output?

Where a schema is declared, output is validated against it before anything downstream sees it, and evals can score or block it. A failing eval can route the run to human review rather than failing outright. When a reviewer rejects an output, Modulo records a Feedback Record, can spawn a correction run with the original context and the rejection reason, and flags the rejection as an eval gap when no existing eval caught it. See Evals, Feedback System, and Pipelines.

Can I produce audit evidence for SOC 2, ISO 42001, or the EU AI Act?

Modulo records every governance event, including run start, agent dispatch, human decision, and gate outcome, in a hash-chained, append-only log inside your own instance, and it captures the reported output of every agent run. That record is always written. The tamper-evident audit log viewer and the compliance exports are part of the Team tier. See Architecture for the audit logger layer.

What infrastructure does Modulo need?

Modulo v1 targets Linux server hosts. The supported way to run Modulo is Docker Compose, which is distribution-agnostic apart from Docker itself: any Linux distribution that can run Docker 24+ and Docker Compose v2.20 or later works, and the production configuration brings up the API, the frontend, queue workers, PostgreSQL 16, and Redis. On Linux, a native install is also supported (Debian 13+ or Ubuntu 26.04+, glibc 2.41 or newer). macOS and Windows are out of scope for v1 server hosts. See Installation for the full platform support matrix.

Does any data leave my network?

Modulo sends no telemetry, and it is air-gap capable. Model calls go only to the providers you configure, so pointing a model backend at a local endpoint such as Ollama, vLLM, or LocalAI keeps inference inside your network. Connectors call the tools you connect, so those calls leave your network when the tool is external. See Model Backends.

Does Modulo support SSO, SCIM, and role-based access control?

Yes, in the Team tier. Modulo supports OpenID Connect (OIDC) and SAML 2.0 single sign-on with just-in-time provisioning, System for Cross-domain Identity Management (SCIM) 2.0 user and group provisioning from providers such as Microsoft Entra ID (formerly Azure AD), Okta, and OneLogin, and team-scoped role-based access control (RBAC) with admin, operator, and runner roles. The Community tier includes basic user management without these. See Single Sign-On and SCIM Provisioning.

Next: Variant Execution (A/B Testing)