# Welcome to Woven.dev

Woven.dev monitors your application code for upcoming **schema and model changes**, so your team always knows **what’s going to change and why** — before it breaks dashboards, pipelines, or compliance guarantees.

> Your next data outage is already in a pull request — Woven catches it first.

### Why It Matters

Data breaks silently — new fields, renamed columns, or missing tags can cascade into hours of debugging or compliance risk. Woven brings visibility **upstream**, where changes start.

* 🔍 **Shift-left visibility** — see schema diffs before they’re merged
* 💬 **Collaborative alerts** — Slack threads bring engineers, data, and compliance teams together
* ⚙️ **Actionable context** — every alert links to impacted models, PRs, teams, and pipelines
* 🧩 **Extendable** — optional automation hooks handle post-merge updates and pre-merge policy checks

Unexpected schema and data changes are the leading cause for Data teams spending so much time firefighting — Woven.dev is here to change that and bring back trust to your data.

***

### What can Woven do?

Woven’s foundation is **Observability**, powered by GitHub + Slack.\
You can extend it with metadata automation and governance workflows — built around how your teams actually work.

#### 🟢 Core Superpower: Observability

**Goal:** Know what’s about to change, when, and why — instantly sent to your Slack channel.

<table><thead><tr><th width="213.91796875">Feature</th><th width="285.390625">Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>Schema Change Detection</strong></td><td>Watches every PR for schema changes</td><td>“<code>orders.amount</code> renamed to <code>order_total</code> in PR #42”</td></tr><tr><td><strong>Slack Alerts</strong></td><td>Sends context-rich messages to relevant channels</td><td>“Column added in <code>users</code> — possible <code>PII:email</code>”</td></tr><tr><td><strong>Lineage Awareness</strong></td><td>Highlights affected models or dashboards</td><td>“This change impacts 3 downstream dbt models”</td></tr></tbody></table>

**Integrations required:**

* GitHub → [setup guide](https://docs.woven.dev/docs/connections/github)
* Slack → [setup guide](https://docs.woven.dev/docs/connections/slack)
* \[Optional] Snowflake -> [setup guide](https://docs.woven.dev/docs/connections/snowflake)

***

#### 🟣 Extension 1: Post-Merge Automations

**Goal:** Eliminate manual updates after schema changes land — using metadata and ownership context.

<table><thead><tr><th width="198.63671875">Feature</th><th width="278.20703125">Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>Snowflake on autopilot</strong></td><td>Syncs metadata, tags, data masking, permissions to Snowflake</td><td>“New table detected -> horizon catalog + cortex AI refreshed and data masking updated”</td></tr><tr><td><strong>Replication Automation</strong></td><td>Auto-updates replication configs (e.g. Fivetran,)</td><td>“New column detected → Fivetran configuration updated”</td></tr><tr><td><strong>dbt Model Sync</strong></td><td>Updates dbt models, source layers, semantic models, and tags</td><td>“New column → dbt source + schema.yml refreshed”</td></tr></tbody></table>

**Additional Integrations required:**

* \[Optional] Snowflake -> [setup guide](https://docs.woven.dev/docs/connections/snowflake)
* \[Optional] Fivetran → [setup guide](https://docs.woven.dev/docs/connections/fivetran)
* \[Optional] dbt Cloud -> [setup guide](https://docs.woven.dev/docs/connections/dbt-cloud)

***

#### 🔒 Extension 2: Pre-Merge Controls

**Goal:** Capture metadata and ownership at the source — before a change merges.

When a developer opens a pull request, Woven intelligently interrupts the flow (in-PR comment or check) to collect:

* **Ownership** — who’s responsible for this model or table
* **Metadata** — purposes, data categories, sensitivity tags, retention, etc.

This keeps your catalog accurate *without separate onboarding steps*. Data models can also be onboarded **organically**, by service, repo, or team — no need for a big-bang migration.

<table><thead><tr><th width="214.6953125">Feature</th><th>Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>Compliance Checks</strong></td><td>Flags missing or incorrect data classifications</td><td>“Blocked: new table missing business purpose”</td></tr><tr><td><strong>Privacy Enforcement</strong></td><td>Ensures all fields are tagged and masked properly for GDPR</td><td>“<code>user_ssn</code> requires PII classification and TTL before merge”</td></tr><tr><td><strong>Policy Gates</strong></td><td>Integrates with CI (GitHub Actions) for merge blocking</td><td>“PR #84 failed — privacy policy check”</td></tr></tbody></table>

### Trust & Security

Woven is built with security and transparency at its core.\
We never access your raw data — only metadata. Your code will be accessed by Woven within your CI runners and only sends metadata over to Woven servers.

➡️ Learn more about our compliance, data handling, and SOC 2 controls at [**trust.woven.dev**](https://trust.woven.dev/?utm_source=chatgpt.com).

***

### Next Steps

Ready to see Woven in action?\
Start with **Observability** — install the GitHub App, connect Slack, and get your first schema alert in minutes.

[👉 **Get Started with Observability →**](https://docs.woven.dev/docs/getting-started/observability)