# Deployment

> Start with Frontal Cloud or choose dedicated cloud or customer-hosted deployment to meet your isolation and compliance requirements.

## Choose a deployment model

Frontal Cloud is the default and the fastest way to get started. Frontal operates the infrastructure, while your team connects its systems and builds production workflows.

| Model | Where it runs | Who operates the infrastructure | Best fit |
| --- | --- | --- | --- |
| Frontal Cloud (recommended) | Frontal Cloud | Frontal | Fast onboarding with Frontal managing the infrastructure. |
| Dedicated / isolated cloud | Dedicated or isolated cloud infrastructure | Frontal | Stronger data-isolation or compliance requirements while Frontal continues to operate the infrastructure. Scope the environment, regions, connectivity, and controls with Enterprise. |
| Customer VPC / self-hosted | Inside the customer’s environment | Customer | Enterprises that require compute and data to remain entirely inside their environment. Confirm the supported architecture and responsibility split with Enterprise. |

“Entirely inside your environment” describes the deployment requirement. Confirm the specific boundaries—including control plane, telemetry, backups, model calls, support access, and updates—against the agreed architecture before production use.

Regardless of hosting model, separate development from production at the workspace and credential boundary. Promote the version that passed evaluation; do not treat a naming convention or a branch as an environment control.
