# Opsphere > Operational intelligence platform for DevOps, SRE, and cloud operations teams. ## Discovery - [llms-full.txt](https://opsphere.io/llms-full.txt): Extended English descriptions (2–4 sentences per page) for retrieval and citation. - [Product Facts](https://opsphere.io/en/product-facts): Canonical machine-readable definition, capabilities, and boundaries. - [Sitemap](https://opsphere.io/sitemap.xml): Full URL index for all locales. - [News hub](https://opsphere.io/en/news): Product updates and integration announcements. - [Blog](https://opsphere.io/en/blog): Engineering and operations articles. - [humans.txt](https://opsphere.io/humans.txt): Team and site contacts. ## Core product - [Platform](https://opsphere.io/en/platform): The operational intelligence layer — connect existing systems through MCP, investigate with evidence, and retain reusable operational context. Parent hub for Operational Investigations and Operational Context. - [Operational Investigations](https://opsphere.io/en/platform/investigations): First-party platform capability — evidence-backed operational investigations with parallel hypotheses, real operational evidence, calculated confidence, timelines and explicit verification, read-only across your existing stack. - [Operational Context](https://opsphere.io/en/platform/operational-context): First-party platform capability — a scoped operational knowledge graph and investigation memory so relevant relationships and previous investigations inform the next one, while logs, metrics, traces, code and infrastructure remain in the systems that own them. - [MCP Operational Gateway](https://opsphere.io/en/platform/mcp-operational-gateway): First-party platform reference — how Opsphere exposes the operational intelligence layer through MCP: atomic tools for direct queries, high-level workflows for structured investigations, shared Operational Context, machine-readable output, read-only by default. Not a generic MCP server. - [Cursor Integration](https://opsphere.io/en/cursor-integration): Cursor as an operational intelligence interface — atomic tools and high-level evidence-backed investigations reach the Opsphere operational layer through MCP. - [Codex Integration](https://opsphere.io/en/codex-integration): Operational intelligence in OpenAI Codex through MCP — atomic tools for direct queries and high-level, evidence-backed investigations (hypotheses, evidence, confidence, timeline, verification) with reusable Operational Context. Read-only by default; source systems remain authoritative. - [Claude Integration](https://opsphere.io/en/claude-integration): Operational intelligence in Claude Code through MCP — atomic tools for direct queries and evidence-backed investigations, with reusable Operational Context. Read-only by default; source systems remain authoritative. - [Copilot Integration](https://opsphere.io/en/copilot-integration): Operational intelligence in local GitHub Copilot CLI through MCP — atomic tools for direct queries and evidence-backed investigations, with reusable Operational Context. Read-only by default; source systems remain authoritative. - [Antigravity Integration](https://opsphere.io/en/antigravity-integration): Operational intelligence in the local Antigravity CLI through MCP — atomic tools for direct queries and evidence-backed investigations, with reusable Operational Context. Read-only by default; source systems remain authoritative. - [Warp Integration](https://opsphere.io/en/warp-integration): Operational intelligence in Warp local through MCP — atomic tools for direct queries and evidence-backed investigations, with reusable Operational Context. Read-only by default; source systems remain authoritative. - [OpenCode Integration](https://opsphere.io/en/opencode-integration): Operational intelligence in local OpenCode through MCP — atomic tools for direct queries and evidence-backed investigations, with reusable Operational Context. Read-only by default; source systems remain authoritative. - [AI Engine Compatibility](https://opsphere.io/en/ai-engine-compatibility): Model-agnostic operational intelligence grounded in evidence — Opsphere separates the operational layer from the AI model, keeping evidence, Operational Context and read-only guardrails independent of provider (OpenAI, Mistral, Anthropic / Claude) and client. - [Web Client](https://opsphere.io/en/web-client): Opsphere's browser interface to the operational intelligence layer — run operational queries and work with structured investigations (hypotheses, evidence, calculated confidence, timeline, verification) and reusable context, no local IDE or MCP client needed. - [Admin Panel](https://opsphere.io/en/admin-panel): Configure Cloud Catalog, tools and credentials, invite users, manage API keys, and review usage and activity. - [Pricing](https://opsphere.io/en/pricing): Simple, transparent pricing — Community free tier, Professional, Team, and Enterprise. - [Product Facts](https://opsphere.io/en/product-facts): Canonical, machine-readable "What is Opsphere?" reference — definition, core capabilities, what Opsphere is not, audience, systems, AI compatibility and data ownership. - [About](https://opsphere.io/en/about): Company story and the team behind the operational intelligence platform. - [Customers](https://opsphere.io/en/customers): Organizations using Opsphere to bring operational intelligence to their engineering environments. - [Security](https://opsphere.io/en/security): Opsphere security posture, operational boundaries, continuous assurance and responsible vulnerability disclosure. - [Contact](https://opsphere.io/en/contact): Get in touch — demos, trials, pricing, and enterprise inquiries. - [Support](https://opsphere.io/en/support): Opsphere for Slack installation, MCP reconnection, permissions, troubleshooting, and links to privacy and terms. ## Integrations - [Integrations](https://opsphere.io/en/integrations): Browse the complete integration catalog — cloud, CI/CD, monitoring, and more. - [aws](https://opsphere.io/en/integrations/aws): Correlate EC2, ECS, Lambda, RDS, and S3 signals with AI-driven incident detection. - [terraform](https://opsphere.io/en/integrations/terraform): Detect IaC drift, Terraform plan failures, and correlate them with runtime incidents. - [kubernetes](https://opsphere.io/en/integrations/kubernetes): Correlate pod restarts, deployment rollouts, and namespace pressure with infra signals. - [vercel](https://opsphere.io/en/integrations/vercel): Link Vercel edge deployment events to backend incidents and infrastructure signals. - [railway](https://opsphere.io/en/integrations/railway): Read-only Railway project status, deployments, logs, and incident diagnosis alongside Vercel and Kubernetes. - [github](https://opsphere.io/en/integrations/github): Correlate GitHub Actions failures, deployments, and pull requests with infrastructure events. - [gitlab](https://opsphere.io/en/integrations/gitlab): Operational intelligence integration. - [bitbucket](https://opsphere.io/en/integrations/bitbucket): Link Bitbucket Pipelines to infrastructure incidents with full deployment traceability. - [datadog](https://opsphere.io/en/integrations/datadog): Surface Datadog metrics inside Opsphere to correlate alerts with infrastructure context. - [contentful](https://opsphere.io/en/integrations/contentful): Monitor CMS delivery health and content release events alongside infrastructure data. - [cloudflare](https://opsphere.io/en/integrations/cloudflare): Monitor edge health, Workers failures, DNS changes, and DDoS event correlation. - [akamai](https://opsphere.io/en/integrations/akamai): Detect CDN edge failures, delivery anomalies, and traffic spikes with origin correlation. - [azure](https://opsphere.io/en/integrations/azure): Correlate AKS, Azure DevOps, App Service, and resource health in a unified view. - [jira](https://opsphere.io/en/integrations/jira): Auto-link infrastructure incidents to Jira tickets and track resolution velocity. - [trello](https://opsphere.io/en/integrations/trello): Operational intelligence integration. - [argocd](https://opsphere.io/en/integrations/argocd): Track GitOps sync status, rollback events, and deployment health. - [sentry](https://opsphere.io/en/integrations/sentry): Correlate Sentry error spikes with infrastructure signals and deploy events. - [pagerduty](https://opsphere.io/en/integrations/pagerduty): Operational intelligence integration. - [slack](https://opsphere.io/en/integrations/slack): Operational intelligence integration. - [prometheus](https://opsphere.io/en/integrations/prometheus): Operational intelligence integration. - [sonarqube](https://opsphere.io/en/integrations/sonarqube): Operational intelligence integration. - [algolia](https://opsphere.io/en/integrations/algolia): Correlate Algolia index inventory, search reproduction, and object lookups with deploys and storefront signals. - [supabase](https://opsphere.io/en/integrations/supabase): Read-only Supabase Management API tools for project status, logs, database capacity, advisors, and service health. - [ecommerce-observability](https://opsphere.io/en/integrations/ecommerce-observability): Correlate Noibu checkout errors and session signals with Google Analytics 4 traffic and conversions, Search Console visibility, and Tag Manager container configuration. Connect each source with its separate authorization; access is read-only and does not include Noibu session replay, heatmaps, raw personal data, or proof that a tag fired. - [network-health](https://opsphere.io/en/integrations/network-health): Monitor network health, BGP events, and latency anomalies with cross-layer correlation. - [custom-integrations](https://opsphere.io/en/integrations/custom-integrations): Build custom connectors via REST API, webhooks, or the Opsphere SDK. ## Use Cases - [small-sre-teams](https://opsphere.io/en/use-cases/small-sre-teams): AI-driven observability and root cause analysis without enterprise tooling overhead. - [aws-vercel-startups](https://opsphere.io/en/use-cases/aws-vercel-startups): Unify AWS and Vercel operations to reduce alert noise and incident response time. - [ecommerce-microservices](https://opsphere.io/en/use-cases/ecommerce-microservices): Correlate distributed services and protect revenue-critical paths in e-commerce. - [terraform-native-teams](https://opsphere.io/en/use-cases/terraform-native-teams): Align Terraform-native teams with live production context and actionable runbooks. - [reduce-tool-sprawl](https://opsphere.io/en/use-cases/reduce-tool-sprawl): Consolidate operational signals — Opsphere as the unified intelligence layer. - [platform-engineering-teams](https://opsphere.io/en/use-cases/platform-engineering-teams): Enable developer self-service and standardize environments for platform teams. - [ai-native-engineering-teams](https://opsphere.io/en/use-cases/ai-native-engineering-teams): Grounded production context for AI-native teams investigating live incidents. ## Comparisons - [AI SRE & Operational Intelligence Platforms](https://opsphere.io/en/compare/ai-sre-platforms): Neutral, educational category page — the four product models grouped under "AI SRE" (incident-management AI, telemetry-native AI SRE, agent-driven production operations, source-system operational intelligence), ten platform-agnostic evaluation questions and a no-winner category matrix. - [Opsphere vs Resolve AI](https://opsphere.io/en/compare/resolve-ai): Neutral, attributed comparison — Opsphere's read-only Operational Intelligence Layer versus Resolve AI's publicly documented agent-driven production operations and governed actions. Strong overlap in cross-system investigation and persistent production context. - [Opsphere vs Rootly](https://opsphere.io/en/compare/rootly): Neutral, attributed comparison — Opsphere's Operational Intelligence Layer versus Rootly's incident-management, on-call and AI SRE platform. Overlap in evidence-backed investigation; different center of gravity (operational stack vs incident lifecycle). - [Opsphere vs Edge Delta](https://opsphere.io/en/compare/edge-delta): Neutral, attributed comparison — Opsphere keeps source systems authoritative and queries them; Edge Delta publicly describes a telemetry-native AI SRE built on a telemetry pipeline architecture. Overlap in investigation lifecycle and recommended actions. ## Core concepts - Evidence-backed Operational Investigations - Operational Context - Operational Knowledge Graph - Investigation Memory - MCP Operational Gateway - Read-only by default ## Important Opsphere does not replace the systems that own underlying telemetry, infrastructure, code or deployment data. It queries and correlates them, and retains operational knowledge — not raw data. ## Locales All locales use a URL prefix: /en/$PATH (English), /es/$PATH (Spanish), /fr/$PATH (French), /de/$PATH (German), /it/$PATH (Italian), /pt/$PATH (Portuguese), /nl/$PATH (Dutch). Bare paths redirect to the detected locale.