> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/extension-framework/building-an-ops-app.md).

# Building an Ops Application

This guide walks through five steps to define, build, and ship a domain-specific Ops application on the Extension Framework. By the end you will have a fully operational application built on the CaaS platform — with forms, status tracking, AI-powered execution, RBAC, cost management, and audit trails all inherited from the framework. The only work unique to your domain is defining your resource taxonomy and writing the skills that encode your operational expertise.

## What You'll End Up With

A running Ops application where users interact through structured forms and status views rather than freeform conversation. When a user submits a request, the framework creates a provisioning ticket, dispatches it to the AI agent, and tracks the resource through its full lifecycle — from `New` through `Provisioning` to `Ready`. Every operation is multiplayer (colleagues can observe and continue any session), auditable (every agent action is recorded), and cost-tracked (token consumption is attributed per ticket, per workspace). Dependency rules are enforced automatically: a Cluster cannot be created without a Network; an Engagement cannot begin without a completed Qualification. REST APIs for every resource type are generated from your policy model, so programmatic access requires no additional work. The only things you bring are the resource definitions specific to your domain and the skill instructions that tell the agent how to operate on them.

## Prerequisites

* DuploCloud account with the Extension Framework enabled.
* Domain expertise sufficient to define a resource taxonomy and write skill instructions for each resource type.
* Provider credentials for the IT systems your application will orchestrate (cloud accounts, CRM systems, observability platforms, etc.).

## The Five Steps

1. [Define Your Policy Model](/docs/extension-framework/building-an-ops-app/step-1-policy-model.md) — declare your resource types, specs, results, and dependencies.
2. [Write Your Skills](/docs/extension-framework/building-an-ops-app/step-2-skills.md) — encode your domain expertise as skill instructions for each resource type.
3. [Connect Providers](/docs/extension-framework/building-an-ops-app/step-3-providers.md) — register the IT systems your application will orchestrate.
4. [Configure Workspaces](/docs/extension-framework/building-an-ops-app/step-4-workspaces.md) — create workspaces, assign scopes and personas, invite users.
5. [Deploy](/docs/extension-framework/building-an-ops-app/step-5-deploy.md) — choose hosted by DuploCloud or self-hosted in your own infrastructure.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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/extension-framework/building-an-ops-app.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.