HyperLake — Agent sandboxes with governed data access: plan the boundaries
FREE PLANNING CHECKLIST

AgentBay provides isolated code and tool sandboxes with data access through LakeGate. Define what an agent may read, execute and change before giving it a real workflow.

Prepare these inputs
[ ] One agent workflow and its tools
[ ] Allowed data and action matrix
[ ] Identity, logging and approval requirements

Your first workflow
[ ] Choose a reversible task with explicit action limits.
[ ] Connect only the required tools and scoped data access.
[ ] Test failures and prohibited actions before expanding the agent’s remit.

Acceptance checks
[ ] Attempt disallowed queries and actions.
[ ] Check sandbox isolation and cleanup.
[ ] Trace outputs to the originating workflow and permission set.

Decision criteria
[ ] Which actions need approval or must be prohibited?
[ ] How are network, filesystem and data permissions separated?
[ ] How will your team investigate an incorrect action?

Cost and scope
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.

Before switching
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.

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

Next step
No free cloud capacity is promised. Deployment scope and charges are agreed separately; AWS and Google Cloud are available today.
https://hyperlake.cloud/solutions/governed-agent-sandboxes

This is a planning template, not a completed assessment or a quote. No personal data is required to download it.