Every new customer is a custom pipeline.
Each new payer, plan, or employer customer arrives with its own feeds, and someone has to build the pipeline to bring them in. The cost shows up as engineering time, not storage.
Common triggers
- Hiring another data or integration engineer to keep up with onboarding.
- A new enterprise customer whose data doesn’t fit the last pipeline.
- A SOC 2 or HIPAA push that asks where every field came from.
Map → Govern → Agent Views.
Dagen is the data control plane for AI. It runs in your AWS account, under your IAM.
Map the estate
Connect to the sources and runtimes you already run. Dagen reads tables, views, and pipelines and builds live lineage.
Govern access
Policy travels with the data. Row- and column-level permissions apply before an app or agent ever sees a record.
Serve Agent Views
Governed, machine-readable views with definitions, access, and lineage, served over MCP to the apps and agents that use them.
Deeper product: data control plane · MCP.
Security reviews and audits get an answer.
Claims and eligibility sources are tracked end to end, from each customer’s feed to the view your product reads. When a SOC 2 audit or a HIPAA review asks where a field came from and who can see it, the lineage and access policy are already there.
Lineage helps you answer the review. It does not replace your own compliance program.
Iceberg on S3. Your account. Your engines.
Dagen deploys in your AWS account under your IAM and networking. Data stays in your S3, Glue, EMR, and Athena.
- Iceberg on S3: open table format on object storage you already pay for.
- Glue / EMR / Athena: pipelines and queries on the AWS compute you already run.
- Your account: data does not leave your estate to “get AI.”
More on Dagen for AWS.
Healthcare on AWS, answered.
Does data leave our AWS account?+
No. Dagen deploys in your AWS account under your IAM and networking. Data stays in your S3, Glue, EMR, and Athena, and it does not leave your estate to “get AI.”
Do we need to replace Redshift?+
No. Iceberg on S3 is the open destination layer on AWS, not a rip-and-replace warehouse move. Warehouses can stay for the workloads that belong there. Dagen maps the estate you already run and lands pipelines on engines you already own.
What does a first workload look like?+
Start with a single warehouse path to Iceberg on S3. Dagen’s agents read the pipelines and logic you already have, carry them forward, and land Iceberg-native jobs on the AWS engines you run, so you get a migrated pipeline, not a restaffed rebuild.
See your next customer onboard on AWS.
We’ll walk through one customer path to Iceberg on S3, on the AWS account you already run.