How ADOm8 Works

ADOm8 turns Azure DevOps stories into a managed AI delivery pipeline. A single AI Agent orchestration trigger starts the workflow, and Current AI Agent tracks active specialist ownership. The open-source flow runs in your own environment, and the managed SaaS provides hosted operations, multi-user controls, and faster onboarding.

ADOm8 means Automate + ADO + M8 — your mate for Azure DevOps delivery.

Orchestrated Agent Flow

1+

AI Orchestrator Trigger

A user story enters AI Agent (the single orchestration state), which triggers the webhook.

1. Trigger

2+

AI Orchestrator + Queue

The orchestrator validates input, enqueues work, and assigns the active specialist agent.

2. Orchestrate

3+

Specialist Agents Execute

Story Planner, Coding, Testing, Review, Documentation, and Deployment agents run in sequence.

3. Execute

4+

PR + Agent Ownership Updates

Branches, commits, pull requests, and Current AI Agent ownership updates are recorded automatically.

4. Deliver

5+

Dashboard + Telemetry

Current AI Agent ownership, activity logs, and health are visible across dashboard and telemetry.

5. Observe

Integrations & Add-ons

Extend ADOm8 across your stack

The orchestration pipeline plugs into your SDLC systems and security tooling so teams can automate work while keeping governance and visibility.

A+

Azure DevOps

Boards, work items, and service hooks trigger and track orchestration.

4.7K
G+

GitHub

Branches, pull requests, reviews, and checks are updated automatically.

4.4K
A+

Azure OpenAI

Planning, coding, testing, and documentation agents run through model endpoints.

4.9K
A+

App Insights

Operational traces and health telemetry feed dashboard and support workflows.

3.8K
K+

Key Vault

Secrets for webhook auth and provider keys are centralized for hardening.

3.2K

Autonomy Levels

  • Level 1Plan only
  • Level 2Generate code only
  • Level 3Pause for human review
  • Level 4Auto-merge on quality threshold
  • Level 5Full autonomy including deployment

Security Model

  • Webhook endpoint requires function key plus shared secret header.
  • Mutating operations are function-auth protected by default.
  • Production hardening adds Key Vault, managed identity, and tighter perimeter controls.