Solutions / Dagen for AWS

The data control plane for AI

Move to Iceberg on AWS
without restaffing the rebuild.

Dagen maps the estate you already run, lands pipelines on Iceberg on S3 in your AWS account, and serves Agent Views over MCP — on Glue, EMR, Athena, and the engines you already own. Snowflake can stay for workloads that belong there.

Or Get Dagen on AWS Marketplace (BYOL in your account).

Who it’s for

Legacy source. AWS destination. Team too small for a hand rebuild.

Dagen for AWS fits buyers with an Oracle, SQL Server, Teradata, or warehouse estate headed to commercial AWS — and a data-engineering bench that cannot staff a from-scratch pipeline rebuild.

Banks & systems integrators

Warehouse or Exadata estates moving to Iceberg on S3; SI-led delivery with a thin customer DE bench.

Mid-market Oracle → AWS

Renewal or EDP pressure; need a production lakehouse path in weeks, not a platform program.

Vertical ISVs on AWS

Product data on commercial AWS; want governed, agent-ready surfaces without restaffing pipelines.

Aggregators on commercial AWS

Multi-source estates consolidating onto Iceberg on S3 under customer IAM and networking.

First workload

Migrate one path to Iceberg on S3.

Start with a single Oracle or warehouse path → 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.

How it works

Map → Govern → Serve Agent Views.

Dagen is the data control plane for AI. On AWS, the open destination is Iceberg on S3 — with jobs on engines you already own.

01 · Map

Map the estate

Connect to the catalogs and runtimes you already run. Dagen reads tables, views, pipelines, and legacy ETL; builds live lineage; and turns tribal knowledge into a shared map.

02 · Govern

Govern access

Policy travels with the data. Row- and column-level permissions apply before an agent ever sees a record. Every answer carries a receipt.

03 · Serve

Serve Agent Views over MCP

Governed, machine-readable surfaces with definitions, access, and lineage — exposed through the Dagen MCP server to Claude, Copilot, or any MCP client.

Jobs still land on Glue, EMR, Athena, Spark, DuckDB, Snowflake, Databricks — interchangeable behind the map. Deeper product: data control plane · MCP · MCP reference.

AWS-native

Iceberg on S3. Your account. Your engines.

Dagen deploys in the customer AWS account under your IAM and networking. Data stays in your S3, Glue, EMR, and Athena — not a rip-and-replace warehouse move.

  • 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.
  • Customer account — BYOL control plane; data does not leave your estate to “get AI.”
  • Snowflake can stay — for workloads that belong there; Iceberg is the shared open layer.
Proof

What Dagen did on a banking warehouse.

Anonymized under NDA.

Oracle Exadata → a hybrid topology of Iceberg on S3 with Glue and EMR, plus an on-premise Hadoop cluster. AWS-first. Snowflake can stay in the picture for consumption; the open Iceberg layer is what agents and engines share.

26,740
Tables inventoried
1,012
Mappings scored
7.85B+
Records reconciled
86%
Translated automatically
Metric Before After
Time per mapping 3 days, manual 3 hours, 86% automated
Team and timeline 6 months, 8 engineers 1.5 months, 4 engineers
Reconciled tables — 100% of migrated tables reconciled
AWS field & partners

Came from an AWS seller or partner?

If an AWS account team, SI, or partner referred you, book a technical demo and we’ll map a first workload — typically one Oracle or warehouse path to Iceberg on S3 — on the AWS you already run.

FAQ

Dagen on AWS, answered.

Is Iceberg on S3 a rip-and-replace of our warehouse?+

No. Iceberg on S3 is the open destination layer on AWS. Snowflake (and other warehouses) can stay for the workloads that belong there. Dagen maps the estate you already run and lands pipelines on engines you already own — reuse over rip-and-replace.

Can Snowflake stay if we adopt Iceberg on AWS?+

Yes. Many teams adopt Iceberg on S3 (AWS-first) while keeping Snowflake for consumption workloads that belong there. The open Iceberg layer is what agents and engines share; the warehouse is not a mandate to abandon.

Is a data control plane the same as a catalog or MCP gateway?+

No. A catalog describes assets for humans to browse. An MCP gateway brokers connectors. Dagen is the cross-estate plane: map + lineage + Agent Views over MCP, with pipelines on your engines. Control plane ≠ catalog / MCP gateway. See the data control plane and MCP pages.

Where can we get Dagen?+

Primary path: Book a technical demo. Secondary: Get Dagen on AWS Marketplace (BYOL AMI you run in your own AWS account). Enterprise deployment available.

Ready for a first workload on AWS?

We’ll map one Oracle or warehouse path to Iceberg on S3 — and book a technical demo on the AWS you already run.