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

temporalio/temporal

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

534 open issues

#11124 Migrate Cassandra driver from legacy gocql v1.7.0 to apache/cassandra-gocql-driver/v2
enhancement
#11108 Membership: provide an operator-facing way to evict a "gray-failed" host (SWIM-reachable but unable to serve) from the ring
enhancement
#11051 Matching: task queue partition managers leaked on concurrent load — losers of the getTaskQueuePartitionManager double-check race are abandoned without cleanup, pinning memory via dynamic config subscriptions
potential-bug
#11026 Feature request - Show the activity task STDOUT in the UI
enhancement
#11025 First-class durable subscription sets for scheduled Workflow fan-out
#10991 CountWorkflowExecutions GROUP BY ExecutionStatus unnecessarily JOINs custom_search_attributes and chasm_search_attributes — 8-16x slower than needed on MySQL
potential-bug
#10941 Suggest continue as new before hitting the maximumSignalsPerExecution limit
enhancement
#10902 Create native support for ECS logging format
enhancement
#10888 Add namespace.ActiveInCluster(clusterName) check in archival task executor
enhancement
#10886 Security: GHSA-xmrv-pmrh-hhx2 — aws-sdk-go-v2/service/lambda v1.88.0 DoS via malformed EventStream frame
View investigation
#10885 Security: CVE-2026-41178 — go.opentelemetry.io/otel/propagation v1.43.0 DoS via unbounded baggage header parsing
#10841 SignalWithStart hangs forever on an orphaned current-execution pointer
potential-bug
#10839 Allow configuring minTLSVersion (and optionally maxTLSVersion) in TLS config
enhancement
#10833 catchup_ready_shard_count metric missing namespace tag
enhancement
#10818 FoundationDB Backend
enhancement
#10775 Updater.addWorkflowTaskToMatching may be missing NotFound logging and build-ID assignment handling present in pushWorkflowTask
potential-bug
#10774 Consider caching parent-not-found results to avoid repeated cross-cluster RPCs in VerifyChildExecutionCompletionRecorded
#10737 Worker Deployment version GC does not reclaim eligible drained versions at maxVersionsInDeployment, wedging rollouts
#10730 serviceResolver: Lookup() routes to draining/stopping members during rolling restarts
potential-bug
#10719 Clarify intent: should taskEventID be removed or converted to interface method in tasks.Tags()
#10718 Status check: can the stale mutable state fallback logic in ndc_task_util.go be removed?
View investigation
#10716 Clarify scope of "redact certain errors" TODOs in history Nexus handler
#10663 Review/Improve Startup Config Template Rendering Code/Process using Sprig
enhancement
#10639 Workflow reset does not recover child completion if child completed after original parent failed
potential-bug
#10600 Add attestations to releases
enhancement
#10579 Schedule deadlocks after Workflow ID reuse when previous scheduled action has Workflow Retry chain
#10548 History service crash due to concurrent map access when history.cacheSizeBasedLimit is enabled
potential-bug
#10522 NewDataBlob silently swallows encoding type errors instead of returning them to callers
#10521 yaml_loader validation warnings should be raised to error level
#10520 SyncActivity replication returns nil instead of RetryReplication error when workflow not found — retry mechanism not triggered