Imbi¶

Imbi is a DevOps service management platform for large environments with many services and applications.

What is Imbi?¶

• A service catalog. Imbi records each project, its type, its owner team, its links, its dependencies, and its documents, in a graph.
• A delivery record. Imbi records the commits, pull requests, tags, releases, and deployments of each project, and shows which environments run different code.
• A quality check. Imbi scores each project, checks it for problems (the Doctor), and records the components that each release ships.
• An automation platform. Imbi runs AI agents, workflows, and scheduled tasks against your projects, and connects to the tools you already use through plugins and webhooks.

Key features¶

Catalog¶

• Projects: one record for each service or application, with fields that blueprints define for each project type
• Organizations and teams: own the projects, with roles for each organization
• Documents: versioned documents on projects, with read statistics
• Search and the assistant: search the catalog from the top bar (Cmd+K) and ask the AI assistant

Delivery¶

• Releases and deployments: deploy, promote a release to the next environment, block a release, and stop a deploy of a commit with failed CI
• Drift: see where environments run different code, and which commits are not released
• Pull requests and dependencies: pull request and commit history, and the software components of each release (SBOM)
• The data model is in Delivery

Quality¶

• Doctor: checks each project for problems and offers fixes
• Operations log and scoring: a record of changes, and a score for each project from scoring policies

AI and automation¶

• Agents and agent tasks: AI agents that do work against your projects, in runner pools that you deploy
• Workflows: deploy, rollback, agent, email, decision, and wait steps that start manually, on a schedule, or from a webhook
• Prompts, AI models, and secrets: versioned prompts, the model catalog of each organization, and short-lived secrets for agents
• Scheduler: cron, interval, and one-shot triggers that call the API or the gateway
• MCP server and Slack bot: use Imbi from MCP clients and from Slack

Platform¶

• Integrations and plugins: connect GitHub, PagerDuty, SonarQube, AWS, Logz.io, Google, and OIDC providers
• Webhook gateway: receive events and run actions from webhook rules
• Event pipeline: analytics rows go through Apache Iggy to ClickHouse
• Security and observability

Architecture¶

The services are in one container image:

Caddy is the only public port. imbi-slackbot connects out to Slack in socket mode, and imbi-workflows has no public route.

These parts are not in the image:

• imbi-harness, the agent runner, has its own image and Helm chart. See Agent Runners.
• iggy-connect runs from the Apache Iggy image as a separate container. It writes the analytics rows to ClickHouse.

See the architecture overview.

Data stores¶