# Overview

DevOps teams today are drowning in complexity — too many tools, too much context-switching, and not enough time to focus on what matters. The DuploCloud Platform changes that by making AI a first-class participant in your operations: triaging incidents, tracking work, connecting systems, and helping teams ship faster. It's designed so any team can adopt it incrementally, from a single use case to a fully AI-native Ops practice.

The DuploCloud Platform is organised into three-layers for building and running AI-native DevOps applications at scale.

At the foundation is **ARMOR (Agent Runtime for Multiplayer Operations)** — Layer 1. ARMOR is a Multiplayer Claude-as-a-Service runtime that brings together ticketing, connections, intelligence, workspaces, RBAC, projects, analytics, and cost management into a unified core. Business users — whether accessing through a web browser, REST API, Claude Code plugin, or Slack/Teams — interact with a shared Workspace that enforces role-based access control and scoped project context, while an underlying CaaS agent (built on the Agent SDK) handles ingestion, moderation, and communication with the LLM layer beneath it.

<figure><img src="/files/ap3BB3RoWkRZkquNsjoc" alt=""><figcaption></figcaption></figure>

Building on that foundation, the **Extension Framework** (Layer 2) lets teams define policy models, build skills, and compose full Ops applications with forms, APIs, and lifecycle management — turning the runtime's capabilities into governed, repeatable workflows.

On top of that sits the **Developer Experience & Hosting** layer (Layer 3), which allows teams to build and ship Ops applications in days using either a web interface or Claude Code, with flexible hosting options (managed or self-hosted). Together, these layers give developers and operators a path from prototype to production without building infrastructure from scratch.

Continue reading for an in-depth look at the problem the DuploCloud platform was built to solve, and a detailed walkthrough of each of the three layers — what they do, how they fit together, and what they unlock.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.duplocloud.com/docs/introduction/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.