---
title: "About PgBeam"
description: "What PgBeam is, why it exists, who it is for, the principles behind wire-level enforcement, where it runs, and what it does not claim."
canonical: "https://pgbeam.com/about"
last-updated: "2026-09-14T06:01:35.626Z"
---

# About PgBeam

PgBeam is the safe Postgres gateway for AI agents. You hand an agent a scoped connection string or a hosted MCP endpoint instead of your superuser one, and PgBeam decides what that credential is allowed to do before the query reaches your database.

## What is PgBeam
A proxy that speaks the PostgreSQL wire protocol. It authenticates a PgBeam-issued credential, applies the policy attached to it, and only then connects upstream. The policy decides access mode, allowed statement types, which tables and columns the credential can touch, which rows come back, what is masked, and how many queries it can run. Every statement is recorded with its decision and reason. Enforcement is at the protocol, not inside the database, so it works with RDS, Aurora, self-hosted, or any managed Postgres, with no extension and no schema change.

## Why it exists
Teams wiring agents into production databases have two common options: a hand-rolled read-only role, or an MCP server pointed at a full-privilege connection string. Neither can mask a column, cap query volume, record what the agent ran, or be revoked without rotating a shared role.

## Who it is for
Platform and AI engineers putting an agent (Claude Code, Cursor, LangChain, or something in-house) in front of real data, and the engineering lead or security owner who has to approve that access. The same controls apply to a person at a psql prompt.

## Principles
- Fail closed. A statement that cannot be proven safe against the policy is refused for an agent credential.
- One policy engine, two front doors. The guarded connection string and the hosted MCP endpoint share one policy and one enforcement path.
- Enforce at the wire, not in the database. No extension, no schema change, no privileged migration.
- Everything is recorded. Allowed, masked, and blocked statements all land in a hash-chained audit log with their reason.
- Say what it does not do. The limits below are published rather than discovered.

## Where it runs
The gateway runs across 12 metros worldwide and routes a connection to the nearest one. The control plane runs in us-east-1. Cached results stay in the region that produced them, and residency routing is honored per organization.

## Pricing and data handling
Subscriptions on published prices, from $9/mo with a 14-day trial. Query contents are not sold or shared. Cached results are in-memory only and never written to disk; upstream database passwords are encrypted at rest and never logged.

## What it does not claim
No SOC 2 Type II certification. Relation-level allowlists do not see through views, so views must be allowlisted explicitly. `SET search_path` is blocked for agent credentials. Query budgets are per-region approximations, not a globally coordinated counter.

## Links
- Contact: https://pgbeam.com/contact
- Features: https://pgbeam.com/features
- Security: https://pgbeam.com/security
- Pricing: https://pgbeam.com/pricing
- Quickstart: https://pgbeam.com/docs