# Gaia Pricing

> Gaia commercial packaging is structured around platform access, onboarding posture, and support model. Package selection is driven primarily by deployment and control needs, not by a one-size-fits-all price list.

## Start with deployment and control requirements.

The right package follows from where Gaia must run, how much operational separation you need, and what enablement model your teams require.

## What is scoped separately

Packages cover the platform, onboarding posture, and support model. Variable commercial elements are scoped only where they are needed.

## A short process before onboarding begins.

We keep commercial scoping lightweight, but explicit enough to align package, governance, architecture, and rollout expectations.

## Deployment models explained

Each package is anchored in a deployment model that matches your control and isolation requirements.

## Infrastructure coverage

Enterprise deployment planning can align to the major cloud environments you already operate, including organization-hosted and on-premises options.

## Governance proof stays available later in the buying flow.

If governance matters in your evaluation, you can inspect the documented module after you understand the package, deployment model, and rollout shape.

## Markdown access

- Canonical page: /pricing
- Markdown page: /pricing.md