---
title: blossom database_instance:create
url: "/docs/reference/cli/database_instance/create/"
canonical_url: https://docs.blossom88.com/docs/reference/cli/database_instance/create/
markdown_url: https://docs.blossom88.com/docs/reference/cli/database_instance/create.md
summary: Create a Dedicated or Shared Database instance with its storage
categories:
- cli
- reference
---

# blossom database_instance:create

Create a Dedicated or Shared Database instance with its storage

## Usage

    blossom database_instance:create [--location LOCATION] [--data DATA] [--follow] [--timestamps]

## Flags

| Flag | Description |
| --- | --- |
| `--location` | Location id (defaults to profile or Account default) |
| `--data, -d` | YAML or JSON data, a path to a data file, or an HTTP(S) URL |
| `--follow, -f` | Follow database instance create logs |
| `--timestamps` | Show log timestamps. Default: true. |

Create a Database instance: PostgreSQL, MySQL, MariaDB, or MongoDB.

Choose the availability. A Dedicated Database instance runs as one node on its own
Server. A Shared Database instance runs on your own Data Capacity with your other
Shared Database and Cache instances; if the Capacity fails, Blossom recovers
them together and connections pause briefly. Both keep the data on storage
that follows the node when the Server is replaced. You choose the engine, the
Location, and the storage size; Blossom provisions the compute, attaches the
storage, starts the engine, and reports readiness in Activity.

A Dedicated PostgreSQL Database instance can also take `standby: true`: Blossom starts
a standby on another Server once the primary is ready and fails over to it
automatically. The standby doubles the node and storage charge and needs
Backup Storage. Turn it on or off later with `database_instance:update`, and move the
writer with `database_instance:switchover`. Read replicas are separate: add them after
creation with `database_instance:replica:create`.

A Shared Database instance takes `small` (0.5 vCPU / 875 MB, the default),
`medium` (1 vCPU / 1.75 GB), or `large` (2 vCPU / 3.5 GB). A 2 vCPU / 4 GB unit fits 4, 2, or 1 respectively.
Memory uses decimal MB/GB. Exact allocations are 875,000,000, 1,750,000,000
and 3,500,000,000 bytes.
Presets start at Small; MongoDB starts at Medium, its default. Custom `{cpu_vcpus, memory_gb}` accepts decimal GB with whole-byte precision,
above the engine floor: 536.87 MB for PostgreSQL/MySQL/MariaDB,
1.07 GB for MongoDB. For Dedicated, use `dedicated_size`: `2vcpu-4gb`
(the default), `4vcpu-8gb`, or `8vcpu-16gb`, where available. The `size`
field is for Shared instances; `dedicated_size` is selected at creation.

    blossom database_instance:init
    blossom database_instance:create --data database_instance.yml --follow

For PostgreSQL, link a Database on the instance to an Environment to inject
its connection URL. Other engines link the Database instance itself. Only
linked Environments can reach the private endpoint.

Choose a saved destination with `--location location-...` or
`location_id` in the payload. Otherwise the profile's `location_id`, then
the Account default applies. Use `blossom location:list` to see destinations.
An explicit payload and `--location` must agree.