Meridian hosting gives you fully managed cloud infrastructure for your Shopify app — no Kubernetes clusters, no container registries, no infra teams required. You connect a GitHub repository, configure your environments, and Meridian handles provisioning, scaling, and availability. Each app gets its own isolated set of environments, and you can attach database addons to any environment without leaving the dashboard.Documentation Index
Fetch the complete documentation index at: https://help.the-meridian.ai/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
Before you can use hosting features, your app must havedeploy_plane_access enabled. If you see hosting options grayed out or missing from your app’s settings, contact your organization admin or reach out to Meridian support to enable this for your app.
deploy_plane_access is required for all hosting APIs — environments, secrets, and deployments. Apps without it cannot access the Deploy section.What Meridian hosting provides
When your app has hosting enabled, Meridian gives you:Managed environments
Create isolated runtime contexts for production, staging, and preview. Each environment runs independently with its own config and secrets.
Git-based deployments
Deploy from any branch or commit SHA. Enable auto-deploy to ship every push to a target environment automatically.
Database addons
Attach a managed database to any environment in a few clicks. Meridian handles provisioning, backups, and connection management.
Regional deployments
Choose the cloud region closest to your merchants. The
default_region on your app sets the default for all new environments.Platform plan limits
Your platform plan controls how many environments you can create across your app. Thehosting_environments field in your plan’s limits object sets this cap.
hosting_environments usage reaches the limit, you won’t be able to create additional environments until you upgrade your plan or delete an existing environment.
Regions
Every app has adefault_region field that controls where new environments are provisioned by default. When you create an environment, you can override this per-environment using the region field on the CreateEnvironmentRequest.
Common region values follow cloud provider conventions (for example, us-central1, europe-west1). Contact support if you need a region not available in the dropdown.
Database addons
Meridian supports managed database addons of type"database". You can attach one database addon per environment. Meridian provisions, monitors, and backs up the database automatically.
Addon plans
Each addon plan has aspecs object that describes its capacity:
| Field | Type | Description |
|---|---|---|
storage_gb | number | Allocated storage in gigabytes |
instance_tier | string | Underlying compute tier (e.g., "shared", "standard", "performance") |
connections_max | number | Maximum concurrent database connections |
backup_retention_days | number | How many days of automatic backups are retained |
| Field | Type | Description |
|---|---|---|
price_cents_monthly | number | Monthly cost in cents (e.g., 2900 = $29.00/month) |
price_cents_yearly | number | Yearly cost in cents, billed annually |
How to add a database addon
Open the environment
In the Meridian dashboard, navigate to Hosting and select the environment where you want to add a database.
Select a database plan
Click Add database. A list of available addon plans appears, each showing the plan name, specs, and pricing. Choose the plan that matches your storage and connection requirements.
Confirm provisioning
Review the selected plan’s specs and monthly cost, then click Confirm. Meridian begins provisioning the database. The addon
status transitions from "pending" to "active" once ready.Addon object reference
AnAddon record represents an active database attached to an environment:
| Field | Type | Description |
|---|---|---|
uuid | string | Unique identifier for the addon |
addon_type | "database" | The addon type (currently "database") |
plan_slug | string | References the chosen AddonPlan |
status | string | Lifecycle status: "pending", "active", "error" |
environment_uuid | string | The environment this addon is attached to |
created_at | string | ISO 8601 creation timestamp |
AddonPlan describes the available database tiers you can select:
| Field | Type | Description |
|---|---|---|
uuid | string | Unique identifier for the plan |
slug | string | Plan identifier used when selecting a plan |
name | string | Human-readable plan name |
description | string | What the plan includes |
specs.storage_gb | number | Allocated storage in gigabytes |
specs.instance_tier | string | Compute tier (e.g., "shared", "standard", "performance") |
specs.connections_max | number | Maximum concurrent connections |
specs.backup_retention_days | number | Days of automatic backups retained |
price_cents_monthly | number | Monthly cost in cents |
price_cents_yearly | number | Annual cost in cents |
Next steps
- Create and manage environments to isolate your production and staging workloads
- Trigger your first deployment from a Git commit or branch