Skip to main content
5 min read

What Is Aiden 2.0?

What Is Aiden 2.0?

Aiden 2.0 is an Agentic AI Operating System (OS) for DevOps and reliability. It actively investigates, automates, and acts across your stack. It is built for organizations that already run multiple DevOps tools and need one operating model for investigation, automation, governance, and action.

Aiden SRE

What Aiden Helps You Do​

You can use Aiden 2.0 for practical DevOps tasks across day-to-day operations:

  • Investigate production incidents and reduce mean time to resolution.
  • Analyze alerts from connected observability systems.
  • Guide CI or CD troubleshooting with context from your stack.
  • Support platform and reliability workflows with repeatable prompts.
  • Help teams apply governance controls without losing execution speed.

What's New in Aiden 2.0?​

Like Aiden 1.0, the goal is to let your engineers operate in natural language while Aiden handles context stitching across tools. If you used Aiden 1.0, the biggest change is structure, policy, and control:

  • Policy guardrails for integrations and tool access.
  • Workflows for deterministic execution.
  • Audit trails and logs.
  • Visibility into Agent executions.
  • Clear hierarchy for scope and ownership.
  • Reusable building blocks across teams.
  • Workspace-centric configuration and ownership model.
  • Explicit separation of reliability, automation, governance, and platform functions.
  • Clearer controls for integrations, approvals, and member access.
  • Better support for repeatable team workflows.

Core Model​

Aiden 2.0 has the following hierarchy: Organization > Workspace > Apps

Aiden Architechture

  • Organization: Your top-level organization boundary.
  • Workspace: Team or environment context where integrations, skills, policies, and workflows are managed.
  • Apps: Tools and capabilities added to a workspace based on use case.

This model helps you isolate context, control access, and scale operations safely.

How Aiden Works​

Behind the scenes, Aiden uses an agentic architecture where specialized agents and skills work together on scoped workspace data. In practice, this means:

  • Requests are interpreted in workspace context first.
  • Connected integrations provide operational evidence.
  • Skills and workflow logic shape execution behavior.
  • Governance and approval checkpoints control sensitive actions.

How Aiden works

This keeps results relevant to your environment and aligned with your operating model.

Last updated on