Skip to content

Safer pipelines.
Less maintenance.

Embrasure is a proactive AI data engineer in Slack and CI/CD, with shared lineage and context for your existing agents.

Works across all your platforms.DatabricksSnowflakeBigQuery

Backed bya16z Speedrun
Built by engineers from
OpenAIPalantirUberLinkedIn

Change safety, incident response, and lineage

Check downstream changes before merging.

Embrasure uses lineage to find the tables a code change could affect, then compares their results before and after the change. Available in CICD or by CLI.

SQL builds, but three downstream consumers receive durations 1,000 times too low. Merge is blocked.

halden-data / analyticsExample pull request
Convert event durations to seconds #527

cayden-le wants to merge into main

embrasure[bot]Sep 4 · 10:42 UTC
Build passed. Duration checks failed.

Three consumers still expect milliseconds. Their durations would be 1,000× too low.

- duration_ms,
+ duration_ms / 1000.0 AS duration_ms
dbt Downstream modelOwnerDuration change
Data platform−99.9%
ML platform−99.9%
Backend−99.9%
PR vs main · Aug 28–Sep 3
Built in isolated schemas
3 models · passed
Existing fields compared
3.4M rows compared
Merge blocked

Compatibility patch drafted for Cayden Le to review.

Example PR #527 · halden-data / analyticsBuild passed. Duration checks failed.

duration_ms now returns seconds. Existing consumers still expect milliseconds.

session_daily
−99.9%
session_stats
−99.9%
session_activity
−99.9%

Against main · Aug 28–Sep 3
3 models built in isolated schemas.
3.4M rows compared. Durations 1,000× too low.

Merge blocked. Compatibility patch drafted.
“it feels like my team just instantly gained 10 genius data engineers.”
Kevin FarhatResearch Engineer

Investigate data issues across systems.

Embrasure traces related alerts across systems to a shared cause, reducing alert noise and investigation time. Shared lineage shows which downstream tables are affected, even when they belong to another tool.

EmbrasureAPP2:18 AM

3 alerts trace back to a partial load. raw.events, hour=01, is missing rows after a failed Fivetran sync.

Source: 12,480 rows. Warehouse: 9,216.
Fivetran run sync_8f24a1 failed.

Downstream of raw.events
  • marts.session_daily · Data platform
  • features.session_stats · ML platform
  • api.session_activity · Backend
Owner: Cayden Le · Data platform
EmbrasureAPP2:18 AM

Backfill hour=01 and rebuild the three affected models. Other partitions match the source.

Cayden Le2:20 AM

Backfill that hour. Open a PR for the completeness check.

EmbrasureAPP2:46 AM

Backfill complete. 3 downstream models rebuilt. Row counts match at the source cutoff.PR #419 awaits review.halden-data / ingestion

Backfill verification

12,480 source rows · 12,480 loaded.
No duplicate event_id values.

# data-incidents
EmbrasureAPP2:18 AM

Partial load in raw.events. hour=01 feeds three downstream models.

Source: 12,480 rows. Warehouse: 9,216.
Fivetran run sync_8f24a1 failed.

2 replies
Cayden Le2:20 AM

Backfill that hour. Open a PR for the completeness check.

EmbrasureAPP2:46 AM

Backfill complete. 3 downstream models rebuilt. Row counts match at the source cutoff.PR #419 awaits review.halden-data / ingestion

Backfill verification

12,480 source rows · 12,480 loaded.
No duplicate event_id values.

Your entire data stack. Lineage that stays current.

Lineage updates automatically across your tools, custom pipelines, and services. Every connection has source evidence you can inspect.

Lineage
Example lineage5 assets

Select a connection to inspect its source

eventsBigQuery
Currentduration_ms

Downstream of events.duration_ms · 2 models, 1 service
Activity API reports table reads. Column usage is not available.

LineageExample · 4 assets
  1. eventsPostgres
    duration_ms
    Fivetran column mapping
  2. eventsBigQuery
    duration_ms
    Spark · SUM(duration_ms)
  3. session_statsIceberg
    total_ms
    Service read event · table-level
  4. Activity APIService

    Reads session_stats

Activity API reports table reads.
Column usage is not available.

Security and compliance

SOC 2 Type II, currently under audit, and HIPAA, both through Vanta. Your data stays in your warehouse; Embrasure reads metadata, lineage, and the queries you allow.

SOC 2 Type II, powered by VantaHIPAA, powered by Vanta

Use your existing tools.

The same checks and lineage through the CLI, MCP, and API.

An AI data team for every platform you run.

Connect Databricks, Snowflake, or BigQuery. Embrasure starts on the pull requests and incidents you already have. Review the findings in GitHub and Slack.