Slack is where ewake works. Dashboard is where you configure it. The Dashboard is your central configuration interface, where everything is set up before it flows into Slack.Everything below is a top-level item in the dashboard sidebar.
Integrations
Connect and manage all your data sources, Datadog, GitHub, Incident.io, and every other integration. Each integration has its own configuration dialog where you paste credentials and test the connection before saving.Browse all integrations →
On-Call Agent
Configure which Slack channels ewake monitors for alerts, which alert bots it listens to, and what prompt it follows when responding. Each trigger is scoped to one channel and one alert source. You can have multiple triggers across different channels.Set up the On-Call Agent →
Scheduled Tasks
Create and manage scheduled analysis runs. Each task has a name, a prompt, a frequency, a look-back window, and a delivery channel.Set up Scheduled Tasks →
Skills
Write team playbooks that ewake applies automatically when investigating. Each skill is a title, a description (used for retrieval), and a body (injected into the agent’s context). Only active skills are used.Set up Skills →
API Keys
Create and revoke the keys that authenticate machine access to your workspace, deployment events and the MCP server. A key is shown once at creation and starts withew_.
Deployment Tracking
Report deploys to ewake from any CI/CD pipeline.
MCP Server
Query ewake from Claude Code, Cursor, or any MCP client.
The sidebar holds more than the sections above, and some items are visible only to workspace admins. New workspaces also start in a learning period, during which parts of the dashboard are greyed out with the tooltip “Ewake is still learning…” while ewake builds your production map. They switch on by themselves.