# Governed database access for people and agents

LakeGate places identity and policy in front of databases and data engines. Start by replacing one shared-credential workflow with scoped, reviewable access.

## Relevant capabilities

- Identity-provider sign-in and role-based access
- OPA policy decisions and query guardrails
- Query logging across integrated engines

## How to compare

- Which users and workload identities require which tables and columns?
- Does the existing client protocol and engine combination work in your deployment?
- How are query limits, audit retention and emergency access controlled?

## Bring these inputs

- Database engines and client tools
- Identity groups and access matrix
- Representative allowed and prohibited queries

## A practical first workflow

- Map one access path and remove ambiguity about the permission owner.
- Configure a pilot role and explicit allow/deny policies.
- Test legitimate queries, blocked queries and access revocation before expansion.

## Check before expanding

- Verify denials as carefully as successful queries.
- Reconcile query logs with the originating identity.
- Keep an emergency access and rollback procedure.

## 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=governed-database-access&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/governed-database-access.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)