Skip to main content
Every Biomni Lab deployment has the same parts: the app and agent, the sandboxes where the agent runs code, your data, and the models the agent calls. The three deployment options differ in where those parts run and who operates them.

Choose a deployment option

Start with Phylo Cloud, the shared platform. Move to Phylo Hosted when your organization needs an environment of its own, single sign-on (SSO), and control over what sandboxes can reach on the internet. Choose Enterprise Hosted when policy requires the app and your data to stay in your own AWS account.
Before you choose
  • A Phylo Hosted environment is reached over the internet, behind a web application firewall. If the app must stay off the internet, choose Enterprise Hosted.
  • An Enterprise Hosted deployment is not air-gapped. It needs outbound access to Phylo’s release service, a sign-in service, and your model endpoint.
  • The models, tools, and connectors available can differ between deployments.

Phylo Cloud

Phylo Cloud is the shared platform at biomni.phylo.bio, where the self-serve plans run. Sign up and start a task. Phylo runs everything: the app, the compute, the storage, and the updates.
You and other users reach one Biomni Lab service on a shared platform run by Phylo. Inside it, your workspace holds your sandboxes and your data, apart from other workspaces. The service calls models run by model providers.You and other users reach one Biomni Lab service on a shared platform run by Phylo. Inside it, your workspace holds your sandboxes and your data, apart from other workspaces. The service calls models run by model providers.

Everyone uses the same platform. Your sandboxes and data belong to your workspace.

Your personal workspace is private. In a Team workspace, project roles decide who can open each project’s tasks, files, and results. For plans and limits, see the Pricing FAQ.

Phylo Hosted

Phylo creates an environment for your organization alone and operates it for you.
Your organization signs in with SSO to its own environment, hosted by Phylo. The environment is a dedicated AWS account that holds the Biomni Lab app, the sandboxes, your data, and model access through Amazon Bedrock. Other customers have separate environments.Your organization signs in with SSO to its own environment, hosted by Phylo. The environment is a dedicated AWS account that holds the Biomni Lab app, the sandboxes, your data, and model access through Amazon Bedrock. Other customers have separate environments.

Your environment is separate from every other customer's, and Phylo operates it.

  • Dedicated infrastructure. The environment has its own AWS account, network, compute cluster, database, and file storage, in an AWS Region chosen with you.
  • Controlled access. Researchers sign in through your identity provider, and your administrators decide which internet domains sandboxes can reach.
  • Models through Amazon Bedrock. Model requests go through your environment’s AWS account, not to a model provider’s public API.

Enterprise Hosted

Your organization hosts Biomni Lab in its own AWS account, in a VPC and private subnets that you provide. No part of the app runs on Phylo’s infrastructure.
Your organization reaches Biomni Lab over your private network. The app, the sandboxes, your data, and model access through Amazon Bedrock or your own gateway are inside your AWS account and VPC. The deployment pulls releases from Phylo, which is outside the account, over an outbound-only connection.Your organization reaches Biomni Lab over your private network. The app, the sandboxes, your data, and model access through Amazon Bedrock or your own gateway are inside your AWS account and VPC. The deployment pulls releases from Phylo, which is outside the account, over an outbound-only connection.

The app, the sandboxes, and your data are in your account. The deployment connects out to Phylo for releases.

  • In your account. The app, the agent, and the sandboxes run on Amazon EKS. Task history is stored in Amazon DocumentDB and files in Amazon S3.
  • Updates are pulled. Phylo supplies the infrastructure definition and each release. A pipeline in your account applies infrastructure changes, and the deployment pulls each release. Phylo never connects in.
  • Phylo access is opt-in. By default, Phylo has no access to your AWS account. If you turn on support access, Phylo engineers can open read-only sessions that last up to one hour and are recorded in your AWS CloudTrail.

What you provide

Next steps

Start on Phylo Cloud

Create a task and work with its results.

Talk to Phylo

Plan a Phylo Hosted or Enterprise Hosted deployment.
For security certifications and policies, see the Phylo Trust Center.