# Batch and real-time analytics without competing for one engine

Velocity Lakehouse combines open tables with a ClickHouse hot tier and separate transformation capacity. Plan how batch, interactive and existing warehouse work will be divided.

## Relevant capabilities

- Iceberg, Trino and ClickHouse in one stack
- Separate transformation and interactive engines
- LakeGate policy and query routing

## How to compare

- Which data belongs in the hot tier versus open tables?
- What freshness and concurrency does each consumer need?
- Which warehouse workloads should remain where they are?

## Bring these inputs

- Batch and interactive query examples
- Freshness targets and data volumes
- Existing warehouse dependencies

## A practical first workflow

- Classify workloads by freshness, latency and retention.
- Pilot one dataset through batch and hot-tier paths.
- Validate routing, reconciliation and cost before consolidating systems.

## Check before expanding

- Reconcile hot-tier and table results.
- Check interactive latency while batch work runs.
- Document replay and recovery for each tier.

## 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=batch-realtime-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/batch-realtime-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)