---
title: blossom database_instance:dedicate
url: "/docs/reference/cli/database_instance/dedicate/"
canonical_url: https://docs.blossom88.com/docs/reference/cli/database_instance/dedicate/
markdown_url: https://docs.blossom88.com/docs/reference/cli/database_instance/dedicate.md
summary: Move a Shared PostgreSQL instance to Dedicated compute
categories:
- cli
- reference
---

# blossom database_instance:dedicate

Move a Shared PostgreSQL instance to Dedicated compute

## Usage

    blossom database_instance:dedicate --id ID [--dedicated-size DEDICATED_SIZE] [--yes] [--follow] [--timestamps]

## Flags

| Flag | Description |
| --- | --- |
| `--id (required)` | Database instance id |
| `--dedicated-size` | Dedicated compute: 2vcpu-4gb, 4vcpu-8gb, or 8vcpu-16gb |
| `--yes, -y` | Confirm the migration operation |
| `--follow, -f` | Follow the migration Activity |
| `--timestamps` | Show log timestamps. Default: true. |

Move a standalone Shared PostgreSQL instance to its own Dedicated compute.
Preview capacity and pricing first:

    blossom database_instance:dedication:show --id database_instance-123 --dedicated-size 4vcpu-8gb
    blossom database_instance:dedicate --id database_instance-123 --dedicated-size 4vcpu-8gb --yes --follow

Shared keeps serving while the Dedicated copy catches up. At cutover,
connections briefly disconnect; reconnect using the same URLs. All logical
databases, credentials, links and endpoint names are kept. This does not upgrade
PostgreSQL or raise its connection limit.

The copy uses an additional disk until cleanup; its storage is prorated.
Existing Shared Data Capacity remains billable while other resources use it.
An empty pool retires after cleanup. Normal billing and Location limits apply.

Cancel before cutover with `database_instance:dedication:cancel`. After cutover
starts, retries continue toward Dedicated and never reopen the old writer.