> For the complete documentation index, see [llms.txt](https://docs.kosmoslabs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kosmoslabs.ai/getting-started.md).

# Getting Started

***

Welcome to Kosmos. This guide walks you through what to expect after connecting your systems.

### How Kosmos Works

Kosmos connects to your existing tools to analyze patterns across your delivery and support data. We identify correlations that identify and prevent recurring incidents before they impact your customers.

**Supported integrations:**

* **Project Management:** Jira, Linear, Azure DevOps
* **Source Control:** GitHub, Bitbucket, Azure DevOps
* **Support & ITSM:** Salesforce Service Cloud, ServiceNow, Zendesk, Pylon
* **Observability:** OpenTelemetry (Preview)
* **Notifications:** Slack, Microsoft Teams

**Our methodology:** INGEST → CORRELATE → SURFACE → ACT → LEARN

### What Happens After You Connect

#### 1. Initial Sync

Once your integrations are connected, Kosmos begins syncing data from your systems. This typically takes 10-30 minutes depending on data volume.

#### 2. Historical Baseline

Your Kosmos team triggers a 90-day historical analysis of your data to create a baseline. This baseline surfaces patterns your team may have been missing—recurring issues, deployment correlations, and systemic risks.

#### 3. Results Presentation

Within the first week, your Kosmos team will walk you through the findings, including:

* Identified Risk Events and their root causes
* Correlations between deployments and incidents
* Recommendations for prevention

#### 4. Ongoing Monitoring

After the initial analysis, Kosmos continuously monitors your connected systems to detect emerging risks and alert you before issues escalate. When a Risk Event is detected, you'll receive a notification in your configured Slack or Teams channel.

### Your Dashboard

After logging in at [app.kosmoslabs.ai](https://app.kosmoslabs.ai/), the home page is organized as an inbox-first view:

* **Risk Events inbox** — A hero card at the top shows how many Risk Events are waiting for review, with a breakdown by confidence level and how long the oldest one has been open. Click anywhere on the card to go directly to your Risk Events queue.
* **Recent activity** — A feed of the latest team actions on Risk Events: who promoted, dismissed, or acknowledged what, and when. AI-surfaced events are highlighted.
* **Background activity** — A summary card showing system stats: signals ingested in the last 24 hours, active clusters, connected systems, and when the engine last recomputed. This is informational — the engine manages this automatically.

The left navigation gives you access to:

* **Risk Events** — Your action queue. Review, promote to RCA, or dismiss.
* **RCA Reports** — Confirmed root cause analyses with correlated evidence
* **Correlation Library** — The research view of all clusters the engine has surfaced. Use for context and investigation, not as a starting point for action.
* **Integrations** — Status of your connected systems
* **Settings** — Field mappings, notification preferences, and configuration

### Notifications

Kosmos sends alerts to Slack or Teams when:

* A new Risk Event is detected
* An RCA is confirmed

Configure your notification channel in Settings → Integrations.

### Getting Help

During your trial, your dedicated Kosmos team is your first point of contact. Reach out anytime:

* **Email:** <support@kosmoslabs.ai>
* **Your Kosmos contact:** \[Provided during onboarding]

### Next Steps

1. Review your connected integrations in Settings
2. Await your Historical Baseline results (your team will schedule the review)
3. Explore initial Risk Events as they appear in your dashboard

***

**Questions?** Contact <support@kosmoslabs.ai> | [app.kosmoslabs.ai](https://app.kosmoslabs.ai/)

© 2026 Kosmos AI Labs, Inc.
