openops

Source#

• Repository: openops-cloud/openops
• Last source update: 2026-04-03
• Last verified: 2026-04-05

Tags#

Integration notes#

Repository is focused on tool/server interoperability; wrap in bounded worker contracts for production use.

worker.md example#

Starter worker.md contract mapped from this registry entry. Copy this file and adapt schemas, constraints, and statuses for your task.

---
id: openops-repo-derived-worker
name: openops Repo-Derived Worker
version: 1.0.0
source_registry_url: https://worker.md/registry/openops/
source_repository: https://github.com/openops-cloud/openops
repository_default_branch: main
repository_language: TypeScript
repository_license: NOASSERTION
repository_updated_at: 2026-04-03
worker_mode: workflow-automation-worker
derivation_method: github_repository_metadata_plus_raw_readme
derivation_confidence: 0.9
derived_on: 2026-04-05
tags:
  - ai-agent
  - ai-agents
  - cloud-governance
  - cloud-optimization
  - enterprise-automation
  - finops
---

# openops Repo-Derived Worker

## Repo-derived summary
- Registry summary: The batteries-included, No-Code FinOps automation platform, with the AI you trust.
- Repository description: The batteries-included, No-Code FinOps automation platform, with the AI you trust.
- Stars (snapshot): 1,011
- Primary language: TypeScript
- Worker mode classification: workflow-automation-worker

## Extracted from
- https://github.com/openops-cloud/openops
- https://github.com/openops-cloud/openops/blob/main/README.md
- https://img.shields.io/badge/Docs-Read%20Now-orange?logo=readthedocs&style=for-the-badge
- https://img.shields.io/badge/Github-Stars?style=for-the-badge&logo=github&label=Star%20OpenOps
- https://openops.com

## Evidence notes (from repository text)
- README summary paragraph: # **OpenOps** ![Welcome to OpenOps!](./static/OpenOps-GitHub-Cover.png)
- https://openops.com is a **No-Code FinOps automation platform** that helps organizations reduce cloud costs and streamline financial operations.
- It provides **customizable workflows** to automate key FinOps processes like allocation, unit economics, anomaly management, workload optimization, safe de-provisioning and much, much more.
- OpenOps **integrates seamlessly** with major cloud providers, many third-party FinOps tools, various communication platforms and a handful of project management tools.
- ![Safe De-provisioning of Idle RDS Instances](./static/rds-workflow.png)
- * **Pre-Built FinOps Workflows** – A library of best-practice workflows designed with input from FinOps leaders. Covers cost optimization, tagging, budgeting, allocation, and reporting.

## Installation hints found in README
- No explicit package installation command detected in README text.

## worker.md contract (derived starter)
Purpose: Execute one automation workflow step in a bounded worker run.

### Input schema
```json
{
  "type": "object",
  "additionalProperties": false,
  "required": [
    "run_id",
    "trigger",
    "step"
  ],
  "properties": {
    "run_id": {
      "type": "string"
    },
    "trigger": {
      "type": "object"
    },
    "step": {
      "type": "string"
    }
  }
}
```

### Output schema
```json
{
  "type": "object",
  "additionalProperties": false,
  "required": [
    "run_id",
    "step",
    "status",
    "artifacts"
  ],
  "properties": {
    "run_id": {
      "type": "string"
    },
    "step": {
      "type": "string"
    },
    "status": {
      "type": "string",
      "enum": [
        "ok",
        "retryable_error",
        "invalid_request",
        "invalid_output"
      ]
    },
    "artifacts": {
      "type": "array"
    }
  }
}
```

### Constraints
- timeout_seconds: 30
- max_attempts: 2
- idempotency_key: run_id
- status_enum: [ok, retryable_error, invalid_request, invalid_output]
- notes: adapt to concrete APIs/classes documented in this repository before production use

## How this should be used
1. Treat this file as a repo-derived starter profile, not a claim of an official repository API contract.
2. Replace schemas with exact interfaces from code/docs you adopt.
3. Keep execution bounded and auditable using worker protocol constraints.

How to use#

• Save this as a worker spec file (for example: openops-my-task.worker.md).
• Replace the input/output schemas and purpose with your real bounded task.
• Enforce schema validation + timeout + retry policy in your runtime before production use.

Citation#

Reference URL: https://worker.md/registry/openops/

Source URL: https://github.com/openops-cloud/openops