# Managed Postgres and MySQL: protect the app, separate reporting

Fusion combines application databases with reporting on ClickHouse. Start with availability and recovery needs, then assess which analytical work should leave the primary.

## Relevant capabilities

- Managed Postgres and MySQL
- High availability and point-in-time recovery
- ClickHouse reporting from Postgres, behind LakeGate

## How to compare

- What recovery point and recovery time can the application tolerate?
- Which reporting queries affect production performance?
- Which extensions, versions and client behaviors are required?

## Bring these inputs

- Database version, size and extension inventory
- Application and reporting query samples
- Recovery objectives and maintenance windows

## A practical first workflow

- Check compatibility and define a reversible migration.
- Pilot the application path and Postgres reporting feed.
- Exercise recovery and switchover before moving production traffic.

## Check before expanding

- Check transaction and reporting consistency.
- Measure primary database load.
- Complete restore and failover exercises.

## 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=managed-postgres-mysql&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/managed-postgres-mysql.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)