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

go-gitea/gitea

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

2,414 open issues

#38523 The warehouse does not act as the main body. Create a project first, and build a warehouse under the project.
type/proposal
#38519 ACME renewal failure at startup closes the listener even when the cached certificate is still valid
type/bug
#38515 Release Gitea 1.27.1
#38513 Add tag prefix filtering to /repos/{owner}/{repo}/releases API
type/proposal
topic/api
#38507 Maintain issue column when moved between projects
type/proposal
#38504 Allow configuring a default external issue tracker for newly created repositories
type/proposal
topic/issues
#38496 Regression: jobs with needs remain blocked on Microsoft SQL Server in Gitea 1.27.0
type/bug
#38494 Seven repo-keyed tables are not cleaned up by DeleteRepositoryDirectly
#38488 The committer should not be displayed as the Gitea server itself
type/bug
#38466 Potential actions bugs in Gitea 1.27.0
type/bug
topic/gitea-actions
#38463 Add REST API endpoints for webhook delivery history (Recent Deliveries)
type/proposal
#38458 upgrade to 1.27.0 fail
issue/needs-feedback
#38450 Heatmap Enhancements
type/proposal
#38447 tmp/git-repo-content full of bundle files
type/bug
#38444 The API in CI processing when the branch repository submits PR to the main repository returns 404
type/bug
topic/api
#38438 Create webhook event is not triggered when creating tags via `git push`
type/bug
#38424 LFS: failed concurrent upload deletes the MetaObject created by a successful retry, silently orphaning content (404 despite content in store)
#38414 Gitea as OIDC provider won't not return an id_token
type/bug
topic/authentication
#38408 LFS objects aren't named correctly
type/bug
topic/lfs
#38395 Error when creating a new pull request (error 500 in browser)
type/bug
#38393 Modify the current Feishu notification method of the webhook to notify participants via direct messages.
type/proposal
#38376 Allow admin to set default SSH certificate principal(s)
type/proposal
#38364 Some checks are pending even when all checks passed
type/bug
#38359 Repository broken with "500 Internal Server Error" after git push: "packfile not found" due to missing .idx files
type/bug
#38358 Add polling-friendly activity/events API with cursor filters
#38338 MatchHostName not allow Docker container hostnames
type/bug
#38306 SSH push fails when the user has no active web session
type/bug
issue/needs-feedback
#38305 Show all users when mentioning
type/proposal
#38301 Storages directory structures improvements
type/proposal
#38300 Create Webhook for Workflow Failures
type/proposal
topic/webhooks