Skip to main content

Setup

Go to the channel → channel settingsIntegrationsAdd apps → search for ewake and click Add.

Full guide →

Use the manifest install instead. You create your own internal Slack app from a manifest Ewake provides, then paste the bot token back into Ewake. Functionally identical to the standard OAuth install.

Manifest install guide →

The GitHub integration has two separate steps: OAuth authorization and GitHub App installation. Both are required. Missing the App installation is the most common cause.

GitHub setup guide →

Ewake requires an Application Key with six read-only scopes: apm_read, dashboards_read, logs_read_data, metrics_read, monitors_read and timeseries_query. It never writes to your Datadog account.

Full scope list →

Slack is required. An observability integration and a source control integration are strongly recommended, without both, investigations are less precise. Source control can be GitHub or GitLab, and can be added later.
Yes. Deployment tracking is a single authenticated POST to the ewake API, so any CI/CD system or deploy script that can make an HTTPS request works. The GitHub Action is a thin convenience wrapper around exactly the same request, not a requirement.

Add deployment tracking to your pipeline →


Features

Datadog, Grafana, Prometheus, Thanos, VictoriaMetrics, Loki, Tempo, ClickHouse, Amazon CloudWatch, Elasticsearch, and GCP Cloud Logging. You can also point ewake at your own tool surface with a Custom MCP server.

Browse all integrations →

Yes, via the Initial Prompt on each On-Call Agent trigger. Use it to control tone, depth, and focus of ewake’s responses.

Configure the On-Call Agent →


Security

Investigation is read-only. The one exception is Actions, an optional follow-up you attach to an On-Call Agent trigger yourself, for example “create a Linear ticket describing the root cause”. Actions only do what you typed, only use integrations you’ve connected, and are bounded by the access those credentials already grant. Ewake still cannot restart a service, change a monitor, or push code.

How Actions fit the security model →

No. Ewake does not use customer data to train or fine-tune any model.
Ewake reads from your connected integrations via API: metrics, logs, traces, commits, and incident data. It does not install agents on your infrastructure. Raw telemetry is queried live and not retained.

Permissions overview →

Ewake is actively preparing for SOC 2 Type II certification through Sprinto. Contact us for the current status and timeline.

Contact support →

Yes. Ewake supports EU data residency. Contact us for details on your region and deployment options.

Contact support →


Pricing

Pricing is tailored to your team’s size and usage. Contact us for details.

Contact support →


Support

Email us at support@ewake.ai. Include the Slack channel, approximate time of the event, and what you observed vs. expected.

Contact support →