# Ace AI

> Ace is a team of AI agents built by Vratix, Inc. that investigates production incidents across infrastructure, telemetry and code, prepares fixes as reviewable pull requests, verifies recovery and remembers what it learned to prevent repeat failures. Investigation is read-only by default; changes follow the customer's approval policy.

Key facts:

- Agents: Telemetry, Infrastructure, Code and Recovery agents work the same case in parallel and share findings.
- Integrations available: AWS, Kubernetes, GitHub, Datadog, Sentry, New Relic, Honeycomb, Prometheus, Grafana, Vercel, Cloudflare, Supabase, Slack, PagerDuty, incident.io, PostHog, LaunchDarkly, Elasticsearch, Trigger.dev, Inngest, PlanetScale, Axiom, LangSmith, Logfire, LiteLLM, CloudWatch, CloudTrail, AWS X-Ray. Coming next: Azure, MS Teams.
- Triggers: CloudWatch alarms (polled or through Amazon SNS), Alertmanager alerts, Datadog monitors, New Relic workflows, Honeycomb trigger and SLO burn alerts, Sentry issues, Grafana and PostHog alerts, Cloudflare origin, edge and health alerts, Supabase project health, PagerDuty and incident.io incidents, failed Trigger.dev and Inngest runs, Ace HTTP health checks, or a request in the app or Slack. Only product reliability failures open incidents: CI runs, billing and budget alarms, feature flag changes and alerts marked ace:ignore are context. Signals from every source join the workload's open incident, so an alert storm opens one incident.
- Actions: fix pull requests (with regression tests when reproducible, reviewed for correctness, data safety and operations, and one follow-up fix if Ace's own pull request fails CI), exact revert pull requests, rollbacks through an administrator-confirmed GitHub Actions workflow, Kubernetes restarts, scaling, patches and revision rollbacks, Vercel rollback and promotion, staged Trigger.dev replays, staged Inngest reruns and Inngest function pauses (always human-approved), staged PostHog flag rollouts, a LaunchDarkly flag kill switch, and PlanetScale deploy requests and backfills (always human-approved). Observability housekeeping runs automatically with Undo: Grafana and Axiom annotations, Honeycomb markers, Datadog downtimes and New Relic muting of the paging condition while a fix rolls out, and resolving or assigning the Sentry issue. Humans merge and the customer's pipeline deploys. Ace has no AWS write actions.
- Autonomy: shadow mode by default, then per-plan approval. Production changes need an administrator or a granted approver. Automatic execution needs a confirmed workload scope, at least five verified recoveries with no worsened outcomes, a daily cap and a Slack cancellation countdown. Automatic merge of Ace's own pull requests is off by default and follows the same earned-autonomy rules.
- Kubernetes: an outbound, namespace-scoped connector for EKS, GKE, AKS and on-premises clusters, installed with a pinned Helm chart from the open-source vratix-dev/ace-kubernetes-connector repository (Kubernetes 1.29–1.37). Reads are scoped per cluster and namespace; changes use a separate identity and the same approvals.
- Memory: organization-wide search of past incidents by meaning, plus each workload's recent resolved incidents.
- Collaboration: agents post in the incident's Slack thread as their own teammate; approvals and questions can be given by message. Slack replies are redacted before storage. PagerDuty and incident.io are read-only: Ace never writes to them.
- MCP server: five read-only tools for coding agents (`get_incident_context`, `search_incidents`, `get_lessons`, `get_operating_rules`, `get_workload_context`), with organization-scoped, expiring, rate-limited tokens. See https://tryace.dev/docs/mcp.md.
- Cost scans: scheduled scans of Trigger.dev and LiteLLM spend, unqueried Datadog custom metrics, and AWS Cost Optimization Hub or Compute Optimizer recommendations and Cost Explorer anomalies, with a weekly Slack digest.
- Security: read-only investigation, least-privilege integration roles and tokens, signed or token-verified webhooks, log text scrubbed of literals, emails, IPs and credentials, separate permissions for changes. The AWS role denies secret values, decryption, sensitive data-plane reads and full SQL text. Ace is built and operated by Vratix, Inc., whose SOC 2 Type II report covers Ace (see https://trust.vratix.com).
- Pricing: annual agreement covering an environment, investigation capacity and approved-change capacity. No per-seat or per-token billing. Quote-based; see https://tryace.dev/pricing.md.
- In production with 7DIGIT, UNICEF and Warestack.
- Contact: founders@vratix.com. Demo: https://tryace.dev/book-demo.

Every page is available as Markdown at the same URL with `.md` appended (home: /index.md), or by requesting the page with `Accept: text/markdown`. The full site is in one file at https://tryace.dev/llms-full.txt.

## Product

- [Overview](https://tryace.dev/index.md): What Ace is, how its agents work together, and how teams adopt it.
- [Product](https://tryace.dev/product.md): System graph, parallel investigation, reviewed fixes, connector actions, recovery checks, system memory, earned autonomy, Slack and the Ace MCP server.
- [Investigations](https://tryace.dev/investigations.md): How an investigation runs from alert to evidence-backed cause and proposed fix.
- [Integrations](https://tryace.dev/integrations.md): Supported sources (AWS, Kubernetes, CloudWatch, X-Ray, Datadog, New Relic, Honeycomb, Prometheus, Elasticsearch, Sentry, Grafana, Axiom, Cloudflare, Supabase, GitHub, Vercel, Trigger.dev, Inngest, PostHog, LaunchDarkly, PlanetScale, Slack, PagerDuty, incident.io, LangSmith, Logfire, LiteLLM), what each reads and changes, and what is coming next.
- [Security](https://tryace.dev/security.md): Read-only investigation, what each integration can reach, verified webhooks, separate authority to act and SOC 2 Type II.
- [Pricing](https://tryace.dev/pricing.md): Annual agreement with coverage, investigation capacity and approved-change capacity. No per-seat or per-token billing.
- [Book a demo](https://tryace.dev/book-demo.md): What a demo covers and how to book one.

## Field guides

- [Field guides](https://tryace.dev/resources.md): Practical guides to evaluating incident agents, root cause analysis and reviewing agent changes.
- [Audit your alerts in one afternoon](https://tryace.dev/resources/audit-your-alerts.md): A short method for finding the alerts that wake people up for nothing, the ones that are missing, and the pages worth keeping.
- [A slow database, a waiting migration and the evidence between them](https://tryace.dev/resources/evidence-backed-root-cause-analysis.md): A worked PostgreSQL lock-queue investigation: follow blockers, test the explanation and check that the fix prevents a repeat.
- [What to review before an agent changes production](https://tryace.dev/resources/governed-remediation.md): A concrete change proposal, approval boundaries and six failure cases to exercise before delegating production actions.

## Docs

Developer documentation for engineers evaluating, using and integrating Ace. Start with [How memory works](https://tryace.dev/docs/concepts/memory.md) or the [Quickstart](https://tryace.dev/docs/quickstart.md).

- [Ace documentation](https://tryace.dev/docs.md): Ace is an AI incident response team for your production systems. It investigates incidents across your infrastructure, telemetry and code, proposes fixes under your approval policy, verifies recovery and remembers what it learned.
- [Quickstart](https://tryace.dev/docs/quickstart.md): Go from a new Ace workspace to your first investigation by connecting AWS, GitHub and Slack, adding a workload and inviting your team.
- [Concepts: How memory works](https://tryace.dev/docs/concepts/memory.md): What Ace remembers from your incidents, when it learns, how memory shapes an investigation or quiets a known-noisy signal, how it fades, and how it stays inside your organization.
- [Concepts: How Ace works](https://tryace.dev/docs/concepts/how-ace-works.md): What happens from the first signal to a closed incident, and how to read what Ace shows you on the incident page and in Slack.
- [Concepts: Proactive detection](https://tryace.dev/docs/concepts/proactive-detection.md): How Ace watches your workloads on its own with HTTP checks, metric watches and early warnings, how it learns what normal looks like, and how to tune it.
- [Concepts: Actions and approvals](https://tryace.dev/docs/concepts/actions-and-approvals.md): Every change Ace can make, how your action policy decides what needs a person, who can approve, how undo works, how Ace verifies recovery, and how earned autonomy lets an action run automatically.
- [Concepts: Operating rules](https://tryace.dev/docs/concepts/operating-rules.md): Write plain-language rules that tell Ace how your team wants incidents diagnosed and fixed, and understand exactly where Ace applies them and what they can't do.
- [Integrations: Integrations](https://tryace.dev/docs/integrations.md): Every tool Ace connects to, what Ace reads and can change in each, which ones open incidents, and how connecting a tool works.
- [Integrations: AWS](https://tryace.dev/docs/integrations/aws.md): Connect AWS so Ace can read CloudWatch, CloudTrail, X-Ray and your infrastructure during investigations, open incidents from CloudWatch alarms, scan for savings and, if you allow it, make approved changes.
- [Integrations: Kubernetes](https://tryace.dev/docs/integrations/kubernetes.md): Connect a Kubernetes cluster so Ace can read resources, events and logs in the namespaces you choose, open incidents from failing pods and nodes and, if you allow it, make approved changes.
- [Integrations: GitHub](https://tryace.dev/docs/integrations/github.md): Install the Ace GitHub App so Ace can read recent code changes, deploys and CI runs during investigations and, after approval, open fix and revert pull requests or roll back a deploy.
- [Integrations: Slack](https://tryace.dev/docs/integrations/slack.md): Install the Ace Slack app so your team can start investigations with @Ace, follow incidents in your channels and approve Ace's actions in Slack.
- [Integrations: Datadog](https://tryace.dev/docs/integrations/datadog.md): Connect Datadog so Ace can read metrics, logs, APM traces and monitors during investigations, open incidents from monitor alerts and mute the paging monitor while an approved fix rolls out.
- [Integrations: Prometheus](https://tryace.dev/docs/integrations/prometheus.md): Connect Amazon Managed Service for Prometheus or an in-cluster Prometheus on Amazon EKS so Ace can query metrics during investigations and open incidents from Alertmanager alerts.
- [Integrations: Grafana](https://tryace.dev/docs/integrations/grafana.md): Connect Grafana so Grafana alerts open incidents in Ace, and Ace investigates them with your alert rules, dashboards and datasources.
- [Integrations: New Relic](https://tryace.dev/docs/integrations/new-relic.md): Connect New Relic so alert issues open incidents in Ace, and Ace investigates them with your APM, OpenTelemetry, trace, error and NRQL data.
- [Integrations: Honeycomb](https://tryace.dev/docs/integrations/honeycomb.md): Connect Honeycomb so triggers and SLO burn alerts open incidents in Ace, and Ace investigates them by querying your traces and events.
- [Integrations: Elasticsearch](https://tryace.dev/docs/integrations/elasticsearch.md): Connect Elasticsearch so Ace can search your logs, metrics and traces during investigations.
- [Integrations: Axiom](https://tryace.dev/docs/integrations/axiom.md): Connect Axiom so monitor alerts open incidents in Ace, and Ace investigates them by querying your logs and events with APL.
- [Integrations: Logfire](https://tryace.dev/docs/integrations/logfire.md): Connect Pydantic Logfire so Ace can query your application logs, traces, exceptions and metrics during investigations.
- [Integrations: Sentry](https://tryace.dev/docs/integrations/sentry.md): Connect Sentry so issue and metric alerts open incidents in Ace, and Ace reads errors, releases, spans, logs and replays while it investigates.
- [Integrations: LangSmith](https://tryace.dev/docs/integrations/langsmith.md): Connect LangSmith so Ace can read your AI workflow runs and traces during investigations.
- [Integrations: LiteLLM](https://tryace.dev/docs/integrations/litellm.md): Connect your LiteLLM proxy so Ace reads model errors and spend during investigations, finds wasted model spend, and proposes fallback and budget changes for approval.
- [Integrations: Vercel](https://tryace.dev/docs/integrations/vercel.md): Connect Vercel so your deploys join the change ledger next to incidents, and Ace can propose rollbacks, promotions, redeploys and firewall changes.
- [Integrations: Cloudflare](https://tryace.dev/docs/integrations/cloudflare.md): Connect Cloudflare so Ace tells edge errors from origin errors, records DNS, rule and Worker changes next to your deploys, opens incidents from Cloudflare notifications, and proposes edge fixes for approval.
- [Integrations: Trigger.dev](https://tryace.dev/docs/integrations/trigger-dev.md): Connect Trigger.dev so failed production runs open incidents, deploys join the change ledger, and Ace can replay or cancel runs and pause queues after approval.
- [Integrations: Inngest](https://tryace.dev/docs/integrations/inngest.md): Connect Inngest so failed production runs open incidents, app syncs join the change ledger, and Ace can rerun, cancel or pause after approval.
- [Integrations: Supabase](https://tryace.dev/docs/integrations/supabase.md): Connect Supabase so unhealthy services, Supabase health checks, read-only mode and a full disk open incidents, and Ace can fix pool size, disk and read-only mode after approval.
- [Integrations: PlanetScale](https://tryace.dev/docs/integrations/planetscale.md): Connect PlanetScale so Ace reads your schema, deploy requests, Query Insights and bounded row counts, and can propose schema changes and backfills that a person approves.
- [Integrations: PostHog](https://tryace.dev/docs/integrations/posthog.md): Connect PostHog so insight alerts open incidents, Ace measures who is affected, and Ace can roll a feature flag out in stages or switch it off after approval.
- [Integrations: LaunchDarkly](https://tryace.dev/docs/integrations/launchdarkly.md): Connect LaunchDarkly so flag changes join the change ledger next to deploys, and Ace can propose a kill switch, a staged rollout or a version restore.
- [Integrations: PagerDuty](https://tryace.dev/docs/integrations/pagerduty.md): Connect PagerDuty so a page joins the Ace incident already open for the same workload, and Ace reads timelines, alerts, on-call and service context during investigations.
- [Integrations: incident.io](https://tryace.dev/docs/integrations/incident-io.md): Connect incident.io so a declared incident joins the Ace incident already open for the same workload, and Ace reads updates, alerts, on-call and your service catalog during investigations.
- [MCP server: Ace MCP server](https://tryace.dev/docs/mcp.md): Give coding agents, code reviewers and other MCP clients read-only access to Ace's incident context, lessons from past fixes, your operating rules and the current state of a workload.
- [Security and administration: Security and data](https://tryace.dev/docs/security/security-and-data.md): How Ace accesses your systems, what data it reads and keeps, how credentials and personal data are protected, and how your data stays inside your organization.
- [Security and administration: Roles and permissions](https://tryace.dev/docs/security/roles-and-permissions.md): The two workspace roles in Ace, what admins and members can each do, how approval permissions work, and how people sign in and join.

## Optional

- [Trust center](https://trust.vratix.com): SOC 2 Type II status, policies and subprocessors.
- [Privacy policy](https://vratix.com/legal/privacy-policy)
- [Terms of use](https://vratix.com/legal/terms-of-use)
- [RSS feed](https://tryace.dev/feed.xml)

Examples on this website, including the "orders stalled after a schema change" incident, are synthetic and are not customer outcomes.