Guides

PostgreSQL Auto-Provisioning

Provision PostgreSQL databases on demand for full-stack web apps and automatically provide the connection details your deployed application needs.

Overview

ProductEcho can provision PostgreSQL infrastructure when an application needs a database, allowing your AI agent to handle backend infrastructure as part of the deployment workflow.

Instead of manually creating a database, copying credentials, and configuring environment variables, the database can be provisioned alongside the application.

How PostgreSQL provisioning works

Your agent identifies the database requirement

Your AI agent determines that the application needs PostgreSQL.

ProductEcho provisions PostgreSQL

ProductEcho creates the required database infrastructure.

Connection details are provided

The database connection details are made available to the deployment workflow.

Your application connects automatically

The application is deployed with the required database configuration in its environment.

What you see in the console

Databases your agent provisions appear under PostgreSQL in the ProductEcho console. From there you can check status, copy connection details, resize, pause, or delete a database.

ProductEcho console, PostgreSQL page. One database, xgos8u, is Running on PostgreSQL 17 with 0.1 vCPU, 256 Mi of memory and 1 GB of storage. A counter reads 1 of 5 databases. — The PostgreSQL page lists each database with its status, endpoint, capacity and storage.

Open a database to see its host, database name and user. Connections require TLS. The password, connection string and code examples are on the Connect tab.

ProductEcho console, database overview. The database xgos8u is Running. A Connection card marked TLS required shows the host, the database name feedback_board and the user feedback. A Resources card lists PostgreSQL 17, 0.1 vCPU, 256 Mi of memory and 1 GB of storage. — The Overview tab shows the connection endpoint and the compute and storage reserved for the database.

Resize a database

In Settings, choose a compute size and, separately, a larger storage size. Storage can be increased but not reduced. Raising storage does not take your application offline. Changing CPU and RAM restarts the database. The sizes available depend on your plan.

ProductEcho console, database settings. The compute dropdown is open and lists db.micro, db.1dcu, db.2dcu, db.4dcu and db.8dcu with their vCPU and memory. A separate Storage field shows 1 GB. — Compute sizes run from db.micro (0.1 vCPU, 256 Mi) to db.8dcu (2 vCPU, 8 Gi). Storage is set separately.

Provision from your agent

With the ProductEcho plugin installed in Claude Code, run the Postgres skill directly and say what you want. The storage size is optional; the minimum is 1 GB.

Claude Code

/productecho-plugin:productecho-postgres create a database with 1GB storage

In any other MCP client, ask in plain language. Your agent calls the same ProductEcho tools.

Any MCP client

Use ProductEcho to create a PostgreSQL database with 1GB storage.

Start deploying

Start Deploying Free