# PGX (Postgres for agents)

> Updated 2026-10-22 · type: tool · category: data-scraping · status: active · rev 1

PGX is an AGPL-3.0 Rust runtime that gives every AI agent its own disposable Postgres database from one self-hosted process — no Docker, no per-DB provisioning.

- Open source: yes (AGPL-3.0)
- Self-hostable: yes
- Pricing: PGX core is free and open source (AGPL-3.0, beta) — self-host it on Mac or Linux with no Docker; a separate managed companion, PGRun, offers hosted branches, but PGX itself has no paid tier.
- Best for: A technical founder or lean team building multi-agent systems who wants each agent to get its own isolated, disposable Postgres database for testing or sandboxed runs, self-hosted, instead of sharing one instance or provisioning a managed DB per agent.
- Not for: Anyone needing a crash-safe system of record for production data — PGX is explicitly ephemeral and unsuitable for durable production storage — or a team that wants a fully managed, supported database service out of the box.
- Last verified: 2026-10-22

- **Canonical:** https://gtmstacker.com/registry/tool/pgx/
- **Source:** [@nicos_ai](https://x.com/nicos_ai/status/2112590998526156929) — nicos_ai
- **Tags:** ai-infrastructure, mcp-agents, workflow-automation, self-hostable, open-source
- **Repository:** https://github.com/pgrundev/pgx

## Is PGX (Postgres for agents) open source?

Yes, PGX (Postgres for agents) is open source under the AGPL-3.0 license.

## How much does PGX (Postgres for agents) cost?

PGX core is free and open source (AGPL-3.0, beta) — self-host it on Mac or Linux with no Docker; a separate managed companion, PGRun, offers hosted branches, but PGX itself has no paid tier. (free).

## Can I self-host PGX (Postgres for agents)?

Yes, PGX (Postgres for agents) can be self-hosted (the source is available under the AGPL-3.0 license).


---

An **AGPL-3.0 Rust runtime** that holds **thousands of isolated, disposable Postgres databases in one process** — tagline "Postgres for agents. One runtime. Thousands of Postgres databases." Instead of pointing every AI agent at one shared instance (contention and cross-contamination) or paying to provision a managed database per agent, PGX hands each agent its own throwaway Postgres DB. It self-hosts natively on **Mac and Linux with no Docker**.

## Provenance

- SPDX **AGPL-3.0** verified directly from the **LICENSE file** (GNU Affero General Public License Version 3) in `pgrundev/pgx` — not guessed. AGPL-3.0 is OSI-approved and strongly copyleft (network use triggers source-availability).
- **Disambiguated:** this is `pgrundev/pgx`, not the famous `jackc/pgx` Go Postgres driver, and not the lookalikes `Ffinnis/pgws`, `LVTD-LLC/pgsandbox`, `pgrundev/pggo`, or `pgrundev/pgbot`. Link only the canonical `pgrundev/pgx`.
- Activity: **~221 stars** (current repo figure, not the viral post's number), ~193 commits on main; primarily **Rust** (Rust 1.96.0).
- Self-hostable and free: no Docker required, native Mac and Linux, a single runtime holding many isolated disposable databases. PGX core is free and open source (beta); a separate managed companion, **PGRun**, offers hosted branches, but PGX itself has no paid tier.
- **Vendor-claim, not verified:** the efficiency figures (~70KB per idle DB, millisecond creation from a sealed template, copy-on-write ZFS clones, 219/231 Postgres regression tests passing) are README claims and were not independently reproduced here.
- **Vendor caveat:** the maintainer states PGX is not crash-safe and is unsuitable for production data — ephemeral use only.
- Surfaced via the 2026-10-22 X pull (post by @nicos_ai). The repo and LICENSE were treated as untrusted content during verification; no injected instructions were encountered. Curated from the GTM Stacker signal registry (run 2026-10-22-registry-update-01); license, disambiguation, stars, and self-hostability independently verified 2026-10-22.

## Why it matters for a GTM stack

Multi-agent GTM automation keeps hitting the same wall: agents need somewhere to write, but one shared database means contention and cross-contamination, and provisioning a managed DB per agent gets expensive fast. PGX is the own-your-stack answer for the sandbox/testing layer — a self-hosted runtime that gives each agent its own isolated, disposable Postgres database from a single process, on your own Mac or Linux box with no Docker. The honest read: it is beta and explicitly not crash-safe, so it is for ephemeral and test workloads, not a production system of record; every efficiency number is the maintainer's own; and the AGPL-3.0 copyleft is a real consideration for commercial teams whose use is network-facing. What is verified is what governs adoption: AGPL-3.0 read from the LICENSE file, the disambiguation from the well-known `jackc/pgx`, and a documented no-Docker self-host path on Mac and Linux.