Operate is a self-hosted AI SRE: an AI agent platform that detects, investigates, and resolves production issues. It runs a four-agent pipeline (Context, Root Cause, Verification, and Resolution) that connects to your logs, database, and codebase, then produces an evidence-backed root cause and a draft pull request for human review.

An AI SRE is an AI system that does the work of a site reliability engineer: watching production for errors and regressions, investigating alerts, finding root causes, and proposing fixes. Operate is a self-hosted AI SRE, so it runs inside your own infrastructure with read-only access and a mandatory human approval gate.

How does Operate find the root cause of a production issue?

When triggered from chat (Slack, MS Teams, and other tools) or by an automated alert, Operate pulls traces from log providers like Datadog, CloudWatch, GCP Cloud Logging, and SolarWinds, queries your MongoDB, PostgreSQL, or MySQL database in read-only mode, and reads your codebase via git including blame and diff. A Context Agent gathers signals, a Root Cause Agent proposes a cause with a confidence score, a Verification Agent independently checks the reasoning with a different model, and a Resolution Agent drafts a fix as a pull request.

Does Operate ship code automatically without a human?

No. Operate stops at a draft pull request. A human engineer must review and merge; nothing ships without approval. Every agent step is auditable so reviewers can see the evidence and reasoning behind each finding.

How is Operate deployed?

Operate is deployed as a Docker image into your existing infrastructure with no new cloud accounts. It runs on port 8080 under the /operate path, requires MongoDB and Redis, and uses an App ID from operate.bettrsw.com. It connects via read-only adapters to logs, databases, and observability stacks, and clones your repo at startup via an init container so agents have full git history.

Which integrations does Operate support?

Operate's context layer spans 60+ integrations across 14 categories: source control (GitHub, GitLab), logs (Datadog, CloudWatch, GCP Cloud Logging, SolarWinds), databases (MongoDB, PostgreSQL, MySQL, read-only), error tracking (Sentry, Rollbar), APM (New Relic, Grafana, OpenTelemetry), CI/CD (GitHub Actions, Jenkins, Vercel), feature flags (LaunchDarkly, Statsig), cloud infrastructure (AWS, GCP, Azure, Kubernetes), queues (Kafka, SQS, RabbitMQ), incident management (PagerDuty, incident.io), issue tracking (Jira, Linear, Asana), support (Zendesk, Intercom), status pages, and docs (Confluence, Notion). Triggers: Slack, MS Teams, and other chat tools for on-demand RCA, plus the observability stack for proactive monitoring. AI providers: Anthropic Claude, OpenAI/Azure Codex, enterprise models, or self-hosted open-source LLMs.

How does Operate avoid hallucinated root causes?

Operate uses a two-model verification step. The Root Cause Agent proposes a cause with specific evidence; the Verification Agent, running on a different model to avoid correlated errors, independently evaluates the reasoning. Speculative or unsupported conclusions are rejected before reaching the team.

Why not just point an LLM at our logs ourselves?

An LLM has no inherent knowledge of your logs, schemas, services, or known-bad patterns. Operate provides the connectors, permissions, query layer, repo context, multi-agent verification, and operational runtime that turn a generic model into a reliable production-investigation system.

Engineering teams that lose 30–40% of capacity to unplanned investigation: support escalations, error alerts, performance regressions. With Operate, support and product teams can trigger an RCA from Slack, MS Teams, or whatever chat tool they use, and only loop in engineers when a decision needs to be made.

← All repos

github

nextcloud/server

Pick an open issue and Operate will investigate its root cause.

2,619 open issues

#62330 [Bug]: "Get your own free account" link leads to "Not Found" page, could be removed?
bug
0. Needs triage
32-feedback
#62328 Feature Request: First-class Named Version References and Published Version API
enhancement
0. Needs triage
feature: versions
#62327 [Bug]: OAuth grant page (LoginFlowGrant.vue) broken in Chrome (works in Firefox) — double form submission invalidates state token, regression of #33164
bug
0. Needs triage
feature: authentication
regression
feature: vue apps
34-feedback
#62325 [Bug]: files:scan creates oversized files_metadata DELETE query and causes severe resource usage
bug
0. Needs triage
34-feedback
#62324 [Bug]: CleanupBackgroundJobsJob stuck in infinite loop due to integer overflow on oc_job_runs.duration
bug
0. Needs triage
34-feedback
#62321 [Bug]: Interrupted non-chunked WebDAV PUT returns 400 but keeps the truncated body as live file content (data corruption)
bug
feature: dav
0. Needs triage
hotspot: file transfer performance
32-feedback
#62318 [Bug]: List of missing files does not always show correct file path
bug
0. Needs triage
34-feedback
#62285 [tests] Analysis of potential flaky e2e tests (AI generated)
2. developing
tests
#62278 Do not delete current folder when using delete hotkey in files and no files are selected
enhancement
design
0. Needs triage
feature: files
#62277 [Bug]: After restore, opening file navigates to Deleted files (file not in trash)
bug
0. Needs triage
feature: files
feature: trashbin
33-feedback
#62264 Offer to open a link via client
enhancement
0. Needs triage
#62250 [accessibility] files: cannot select multiple files with keyboard only
1. to develop
feature: files
accessibility
team: Files
#62248 [accessibility] files: invisible but focusable element between "new"-button and "switch to grid view"-button
1. to develop
feature: files
accessibility
team: Files
#62245 [accessibility] public share: cannot use "download" button with keyboard only
1. to develop
feature: sharing
accessibility
#62233 [Bug]: Changed access rights after deleting and restoring
bug
0. Needs triage
feature: trashbin
34-feedback
#62193 Define a Centralized Model for Encrypted File and Folder Actions
enhancement
0. Needs triage
feature: encryption (client-side)
#62190 [Bug]: Creating and deleting App Tokens runs into error
bug
0. Needs triage
feature: authentication
feature: settings
33-feedback
#62105 [Bug]: can not select custom background
bug
medium
0. Needs triage
feature: theming
34-feedback
#62087 Use static code analysis to ensure database portability
enhancement
1. to develop
developer experience
CI
feature: database
#62086 [Bug]: appsallowlist silently strands enabled apps as "incompatible" during major upgrades — updater's post-disable re-fetch is gated by the allowlist
bug
0. Needs triage
feature: install and update
feature: apps management
#62037 [Bug]: The external storage set up via WebDAV, and then the newly created markdown share links or favorites often stop working.
bug
feature: external storage
0. Needs triage
34-feedback
#62031 Allow administrators to disable editable public links while keeping read-only public links enabled
enhancement
0. Needs triage
#62029 [Bug]: Setting locale failed.
bug
needs info
1. to develop
35-feedback
View investigation
#62028 Error while expiring trashbin
#62026 external storage: Show each share as a separate entry in the sidebar
enhancement
0. Needs triage
#62023 store the latest N file versions
enhancement
0. Needs triage
feature: versions
#61979 Add a GUI for setting the value of dav.invitation_link_recipients, needed by non-public nextcloud servers
enhancement
0. Needs triage
#61964 Index content of files (fulltextsearch indexing)
enhancement
0. Needs triage
feature: search
#61955 [Bug]: Errors when changing login password in a server with SSE user encryption
bug
1. to develop
feature: encryption (server-side)
34-feedback
#61949 [Bug]: occ share:list aborts with "Node for share not found" if any orphaned share exists
bug
0. Needs triage
32-feedback