# An open Iceberg lakehouse: plan tables, access and migration

Openhouse combines Iceberg, Trino and dbt on your own object storage. Make table ownership, interoperability and workload fit explicit before migrating an existing lake.

## Relevant capabilities

- Iceberg tables on customer object storage
- Trino, dbt modeling and a semantic layer
- Dashboards and data monitors behind LakeGate

## How to compare

- Which engines must read the same tables?
- Who owns schemas, compaction and data quality?
- How will existing warehouse jobs coexist during transition?

## Bring these inputs

- Table inventory and storage layout
- Transformation jobs and consumer engines
- Access and data-quality requirements

## A practical first workflow

- Select one dataset with known consumers and acceptance checks.
- Build the table and transformation path alongside the current system.
- Check interoperability and operations before retiring the old path.

## Check before expanding

- Validate schema and data reconciliation.
- Test reads from each required engine.
- Review lifecycle, recovery and storage charges.

## Economics
Compare the cloud bill, platform charges, operating effort and migration work for the same workload. Cloud capacity is not free. Charges and scope need agreement before paid deployment.

## Switching considerations
AWS and Google Cloud are available today; other deployment environments are roadmap. Preserve the existing workload and access path until compatibility, recovery and cutover checks pass.

## Free next step
Get a free deployment checklist, then create your workspace. Free expert help with your use case is also available through our contact form.

[Create your HyperLake workspace](https://app.hyperlake.cloud/users/sign_in?intent=open-iceberg-lakehouse&offer_id=starter-checklist-v1&utm_source=hyperlake&utm_medium=owned&utm_campaign=signup-journey&utm_content=landing_hero)

[Download the free checklist](https://hyperlake.cloud/solutions/open-iceberg-lakehouse.txt)

No free cloud capacity is promised. Deployment scope and charges are agreed separately; AWS and Google Cloud are available today.

## Sources
- https://hyperlake.cloud/stacks
- https://hyperlake.cloud/faq
- https://hyperlake.cloud/get-started

[Discuss this workload](https://hyperlake.cloud/contact)