# Deployment (/docs/deployment)



Deployment [#deployment]

RawTree is the database. RawTree Cloud and RawTree BYOC are services that deploy
and operate it. The database supplies SQL execution, storage, access controls,
and workload scheduling. The service supplies APIs, provisioning, service
identities, and operational tools.

Examples use `https://api.rawtree.com` for RawTree Cloud and RawTree BYOC across regions.

RawTree Cloud [#rawtree-cloud]

RawTree Cloud hosts the database infrastructure. Administrators use the
service to create clusters, select capacity, and manage access.

RawTree BYOC [#rawtree-byoc]

RawTree BYOC means bring your own cloud. It deploys database infrastructure in
your cloud account. Your organization owns that account and supplies the
permissions and network access required by the deployment.

BYOC remains a service deployment. It does not imply that every service
component runs in your account or that every database operation is publicly
exposed. Use the integrations enabled for your deployment.

The service manages cluster lifecycle through the permissions granted during
onboarding. Your organization controls those grants and its cloud resources.
Server configuration belongs to the operators responsible for the deployment.

Shared database model and interface limits [#shared-database-model-and-interface-limits]

Both deployments use RawTree's SQL and database object model. Service versions,
configuration, enabled integrations, and available capacity can differ.
The [Query API](/docs/reference/api/query#post-v1query) exposes selected SQL operations.
Its restrictions are separate from the capabilities of the database.

Organizations, memberships, billing, and provisioning are service concerns.
SQL users, roles, policies, settings profiles, and workloads are database objects.
See [Resource model](/docs/concepts/resource-model) and
[Access control](/docs/concepts/access-control).

Customer-owned storage [#customer-owned-storage]

RawTree Cloud can use customer-owned S3 storage for a cluster or database.
Your organization supplies the buckets and an IAM role with the required access.
The service stores the configuration and verifies access.
See [Bring your own bucket](/docs/deployment/bring-your-own-bucket).

A customer-owned bucket changes storage ownership. It does not move database
compute into your account, so it is not equivalent to RawTree BYOC.

Placement and capacity [#placement-and-capacity]

Use `GET /v1/regions` to list available placements. Organization-scoped results
include eligible RawTree BYOC regions. Use the region's identifier when
selecting a placement, because deployments can share a cloud-region name.

Use `GET /v1/clusters/sizes` for available CPU, memory, and replica limits.
Those values can vary by environment. See the
[API reference](/docs/reference/api/regions) for access requirements and fields.