# Federated SQL across existing systems: plan a governed query

Unify uses managed Trino for queries across existing sources. Test one cross-system decision before deciding which copies or sync jobs you can retire.

## Relevant capabilities

- Trino federation over connected catalogs
- Row filters, column masks and a semantic layer
- Governed access through LakeGate

## How to compare

- Can each required source support the connector and query pattern?
- What latency and source load are acceptable?
- Which movements are still needed for performance, freshness or isolation?

## Bring these inputs

- Source systems and schemas
- One representative join and expected answer
- Freshness, permissions and latency requirements

## A practical first workflow

- Document the existing data movement and the decision it supports.
- Connect a limited source set and test the governed query.
- Compare correctness, source load and operating effort before replacing sync jobs.

## Check before expanding

- Reconcile row counts and join semantics.
- Check predicate pushdown and source impact.
- Test policy enforcement across the combined result.

## 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=federated-sql&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/federated-sql.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)