pgmi

PostgreSQL-native deployment

pgmi

An execution fabric for teams that want PostgreSQL to drive deployment logic, not a migration framework that hides it.

Start with Quickstart Why pgmi

Execution model

pgmi prepares the session. Your SQL decides the deployment.

Load

Project files, metadata, tests, and parameters become session-scoped temporary tables and stable views.

Hand off

deploy.sql queries those views and chooses ordering, filtering, transactions, idempotency, and rollback.

Execute

The generated plan runs in the same PostgreSQL session, with notices and errors coming directly from PostgreSQL.

Where it fits

For database work that needs real control.

Use pgmi when deployment logic belongs close to the database: environment-aware changes, test gates, data loads, generated APIs, or application behavior expressed in SQL.

  • CLI flags stay focused on infrastructure: connections, parameters, compatibility, observability.
  • Deployment behavior stays in deploy.sql, where it can be reviewed and tested with the rest of the database code.
  • The advanced template can expose PostgreSQL-backed REST, RPC, and MCP APIs without changing the core model.

Choose a starting point

Small scaffold or full reference app.

Basic

A compact migration scaffold with path-based ordering, tests, and a readable deploy.sql.

Use the basic template