> ## Documentation Index
> Fetch the complete documentation index at: https://docs.biomni.phylo.bio/llms.txt
> Use this file to discover all available pages before exploring further.

# Deployment options

> Run Biomni Lab on Phylo Cloud, in a Phylo Hosted environment of your own, or Enterprise Hosted in your own AWS account

Every Biomni Lab deployment has the same parts: the app and agent, the
[sandboxes](https://docs.biomni.phylo.bio/features/models-and-compute.md#computational-work) 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.

| | Phylo Cloud | Phylo Hosted | Enterprise Hosted |
| - | - | - | - |
| **Best for** | Individuals and small teams | Organizations that want an isolated environment without operating it | Organizations that must keep the app and their data in their own cloud |
| **App and agent** | Phylo's platform, shared by all workspaces | An AWS account that Phylo dedicates to your organization | Your AWS account, in a VPC you provide |
| **Sandboxes and data** | On the shared platform, with data access scoped to your workspace | On a cluster, database, and file storage only your organization uses | On a cluster, database, and file storage in your account |
| **Models** | Phylo's model providers | Amazon Bedrock, through your environment's AWS account | Amazon Bedrock in your account, or your own model gateway |
| **Sign-in** | A Biomni Lab account | SSO with your identity provider | SSO with your identity provider |
| **App access** | Internet | Internet, at an address of your own | Your private network only |
| **Operated by** | Phylo | Phylo | Your team owns the AWS account and network; Phylo supplies releases and support |

> [!NOTE]
>
> **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](https://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.](https://mintcdn.com/phylo/b988BF6A-WS9CSqG/images/deployment-options/phylo-cloud-light.svg?fit=max\&auto=format\&n=b988BF6A-WS9CSqG\&q=85\&s=2d2ff1a2c189b500348af3bce8c061ea)

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

Your personal workspace is private. In a Team workspace,
[project roles](https://docs.biomni.phylo.bio/features/collaboration.md) decide who can open each project's
tasks, files, and results. For plans and limits, see the
[Pricing FAQ](https://docs.biomni.phylo.bio/pricing-faq.md).

## 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.](https://mintcdn.com/phylo/b988BF6A-WS9CSqG/images/deployment-options/phylo-hosted-light.svg?fit=max\&auto=format\&n=b988BF6A-WS9CSqG\&q=85\&s=55b93972eb8d2448001c50b093e0d939)

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.](https://mintcdn.com/phylo/b988BF6A-WS9CSqG/images/deployment-options/enterprise-hosted-light.svg?fit=max\&auto=format\&n=b988BF6A-WS9CSqG\&q=85\&s=07d19f3363d7e3e1814867e45b994202)

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

| Requirement | Details |
| - | - |
| **AWS account** | Yours, in the Region you choose. Enterprise Hosted deployments run on AWS. |
| **Network** | A VPC with private subnets in at least two Availability Zones |
| **Address** | A hostname on your domain and an AWS Certificate Manager certificate for it. Researchers reach the app at this internal address. |
| **Sign-in** | Your identity provider, connected for SSO |
| **Models** | Amazon Bedrock access in the account, or your model gateway |
| **Outbound access** | HTTPS to Phylo's release service, the sign-in service, and your model endpoint. Phylo reviews the exact list with your network team. |
| **Inbound access** | None from Phylo |

## Next steps

> [card] [Start on Phylo Cloud](https://docs.biomni.phylo.bio/quickstart.md)
>
> Create a task and work with its results.

> [card] [Talk to Phylo](https://phylo.bio/enterprise)
>
> Plan a Phylo Hosted or Enterprise Hosted deployment.

For security certifications and policies, see the
[Phylo Trust Center](https://trust.phylo.bio).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.